If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Hi
Zosimo Recio Jr
•,
Welcome to Microsoft Q&A forum.
As I understand, you could not connect to newly created Azure SQL Managed Instance.
Could you please let us know the configuration details of the SQL MI ?
Also, review your network settings and instance name.
If you're unable to connect to SQL Managed Instance from an Azure virtual machine within the same virtual network but a different subnet, check if you have a Network Security Group set up on VM subnet that might be blocking access. Additionally, open outbound connection on SQL port 1433 as well as ports in the range 11000-11999, since those are needed to connect via redirection inside the Azure boundary.
Ensure that propagation of gateway routes is disabled for the route table associated with the virtual network.
If using point-to-site VPN, check the configuration in the Azure portal to see if you see
Ingress/Egress
numbers. Nonzero numbers indicate that Azure is routing traffic to/from on-premises.
Check that the client machine (that is running the VPN client) has route entries for all the virtual networks that you need to access. The routes are stored in
%AppData%\Roaming\Microsoft\Network\Connections\Cm\<GUID>\routes.txt
.
As shown in this image, there are two entries for each virtual network involved and a third entry for the VPN endpoint that is configured in the portal.
Another way to check the routes is via the following command. The output shows the routes to the various subnets:
C:\ >route print -4
Interface List
14...54 ee 75 67 6b 39 ......Intel(R) Ethernet Connection (3) I218-LM
57...........................rndatavnet
18...94 65 9c 7d e5 ce ......Intel(R) Dual Band Wireless-AC 7265
1...........................Software Loopback Interface 1
Adapter===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.83.72.1 10.83.74.112 35
10.0.0.0 255.255.255.0 On-link 172.26.34.2 43
10.4.0.0 255.255.255.0 On-link 172.26.34.2 43
===========================================================================
Persistent Routes:
If you're using virtual network peering, ensure that you have followed the instructions for setting Allow Gateway Transit and Use Remote Gateways.
If you're using virtual network peering to connect an Azure App Service hosted application, and the SQL Managed Instance virtual network has a public IP address range, make sure that your hosted application settings allow your outbound traffic to be routed to public IP networks. Follow the instructions in Regional virtual network integration.
Let us know if this helps.
Thanks.
