Secure networking with Azure and Azure SQL Managed Instance
summary
Azure SQL Managed Instance requires a dedicated subnet that can’t host other resources, and DNS changes in the VNet must be notified to the instance. Connectivity options are vNet-local (dynamic IP), a public endpoint uses port 3342 mapping to 1433 (proxy-only), and private endpoints (announced in public preview) where a private endpoint consumes one static IP and supports only 1433/proxy. Redirect connections need TDS 7.4+ drivers. Use NSGs, service endpoint policies, peering/VPN/ExpressRoute, Bastion, Defender/Sentinel, Azure Policy and private DNS for secure setups.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:46Agenda
- 1:51Azure SQL - a family of SQL products
- 4:17Virtual network (VNets)
- 6:04Virtual networks: subnets
- 7:57How Azure SQL Managed Instance integrates into your virtual network
- 9:05Connecting to Azure SQL Managed Instance
- 9:57VNet-local endpoint
- 11:27Public endpoint
- 12:09Private endpoints
- 16:02Scenario 1 Open to the Internet
- 19:25Secure operator access
- 23:03Scenario 2
- 23:47Secure connectivity inside your company's Azure presence Virtual network peering
- 26:36Scenario 3 | Secure connectivity between your company's Azure resources
- 31:43Secure connectivity across Azure
- 34:14Scenario 5
- 36:39Azure SQL Managed Instance works with...
related talks
44mSQL Managed Instance: Fully managed SQL Server in Azure
52mAzure Sql DB Managed instance, a different sql server?
50mManaged Instance Link - Seamless migration to Azure
39mModernize your applications on Azure SQL Managed Instance Q&A
50mDiscover what's new in Azure SQL Managed Instance through an exciting Demo Party!
44mThe Ultimate Freedom of Movement with SQL Server 2022 and Azure SQL Managed Instance- 44mThe Ultimate Freedom of Movement with SQL Server 2022 and Azure SQL Managed Instance
- 50mManaged Instance Link - Seamless migration to Azure