Demo: Network Security for Azure SQL Database | Azure SQL for beginners (Ep. 23)

In this video, watch a demo of how to configure and examine the various Azure SQL networking options, including Private Link. For the full Azure SQL Fundamentals learning path on Microsoft Learn, visit: aka.ms/azuresqlfundamentalsyt
Watch the entire series: aka.ms/azuresql4beginners
View code on Github: aka.ms/asqlworkshop, select Workshop: Azure SQL
Learn live: aka.ms/azuresqlbootcamp
👉 Follow Azure SQL on Twitter: aka.ms/msftazuresqltw
🔔 Subscribe to our channels for even more tips:
Microsoft Developer: aka.ms/msftdeveloperyt
Microsoft Azure SQL: aka.ms/msftazuresqlyt
✔️ Additional Resources:
Azure SQL documentation: aka.ms/azuresqldocumentation
Get expert advice on Azure SQL Database with detailed guidance on migration and how to modernize your applications: aka.ms/AzureSQLDBAdmin
Learn the benefits of transforming your on-premises databases to the cloud database technologies available with Azure SQL: aka.ms/DBAHandbook
#AzureSQL #AzureSQLforbeginners #LearnAzureSQL #DataExposed #Azure #SQL

[@SQLTalk]

Excellent video. Very clearly explained how to set up Privatelink for Azure SQL. Thank you.

[@pdaniaful]

Excellent video, thanks for sharing but if I'm not mistaken, Private Link for securing azure sql database has moved on a bit since? Is there an updated video?

[@prafulrane9037]

is this helpful for dp 300?

[@daye1997]

Thanks for the video, How to integrate AzureAD authentication with Azure SQL Database? How can On-Prem users connect to the Azure logical DB? using the DNS name after setting up the allowed client public IP address or using the endpoint private virtual network?

[@amthomas46]

Hi Da Ye, I am including a reference below that should help with your AAD auth query. For your second two questions, either way, a user will connect to the logical server name, e.g. aw-server0602.database.windows.net. If public endpoint is configured, they will still need network access from where they are connecting. If Private Link is used, they will need access to the virtual network. The second link below contains some more info. Hope that helps. docs.microsoft.com/azure/azure-sql/database/authentication-aad-overview docs.microsoft.com/azure/azure-sql/database/security-overview#network-security

[@pavelsh3638]

Thanks for a good video! I did it like a video. I have a sql server, added a virtual network to the rule, created an endpoint, everything is like in video. But my virtual server with which I want to connect in a different subnet and a different data center. I have configured network peering. Everything is fine, I see through the netcat or telnet program the open port 1433 of the sql server. But when I try to connect, I have problem "Error message: Cannot open server "my_server_ip or url" requested by the login. The login failed". What could be the matter, please tell me.

[@MicrosoftDeveloper]

Hi Pavel, it's hard to troubleshoot over comments. I would try some basic testing to confirm you are able to connect to the logical SQL Server from anywhere (e.g. the same virtual network, using the Azure portal query editor). If that works, then there's something up with the connectivity between where the logical server is, and the 'different subnet and different data center'. If you can't narrow that down, you might find this guide helpful docs.microsoft.com/azure/azure-sql/database/troubleshoot-common-errors-issues . Alternatively, I would open a support case. Thanks!