This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Recently I have been working on some cases for stuck operations on Azure SQL managed instance. These operations can be such as an update backup storage redundancy or scale service tier, which gets stuck and never completes.
Looking at Azure SQL managed instance telemetries we were able to find that in such cases the cause can be related to using one of the reserved names for Microsoft for your Azure DNS private DNS zone(s):
- database.windows.net
Associating Azure DNS private zone with a reserved name with a virtual network containing Managed Instance renders SQL Managed Instance unavailable.
To resolve this, we will need to remove the virtual network link on the Private DNS Zone to the virtual network that contains Managed Instance. You can follow the steps below:
1. From Azure portal, search and access Private DNS zones.
2. Select the private DNS zone that is causing the issue.
3. Select Virtual network links blade.
4. Select the link that is associated with the virtual network containing SQL Managed Instance.
5. Delete the link.
6. If you have more than one private DNS zone listed above, repeat the same process for the remaining zone(s).
Using a name reserved for Microsoft services for your Azure DNS private zone with is currently not supported for SQL Managed Instance.
In addition, please find the below as shared in our public document (Connectivity architecture - Azure SQL Managed Instance | Microsoft Docs:(
Following is the list of reserved names: windows.net, database.windows.net, core.windows.net, blob.core.windows.net, table.core.windows.net, management.core.windows.net, monitoring.core.windows.net, queue.core.windows.net, graph.windows.net, login.microsoftonline.com, login.windows.net, servicebus.windows.net.
To configure private links correctly, see Azure Private Endpoint DNS configuration. We also recommend reviewing the existing networking constraints.
Thank you!