An Azure relational database service.
Thank you for reaching out with your question regarding the auto-upgrade process for your Azure SQL Managed Instance (SQL MI) in a non-compliant subnet and using a custom DNS zone. We understand the importance of minimizing downtime during the upgrade and would like to guide you through the steps you can take to prepare and mitigate potential issues.
As the SQL MI undergoes an auto-upgrade, it’s important to ensure that the networking and DNS configuration are set up correctly to avoid any interruptions, particularly given the potential downtime of up to 6 hours during the upgrade.
Verify that your subnet complies with the network intent policy requirements, including correct route table and network security group (NSG) configurations.
Please go through this link for Additional Information: https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/subnet-service-aided-configuration-enable?view=azuresql#overview
Ensure your custom DNS zone is correctly configured and resolves all necessary domain names.
If changing DNS server settings, update the virtual network's DNS settings and ensure SQL Managed Instances are notified.
Ensure there are no DNS caching issues, and that your DNS settings are propagated across the network before the upgrade.
Hope this helps. Do let us know if you any further queries. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.