Skip to main content
Question

Azure SQL MIs being placed under Object Storage instead of Database

  • Nov 13, 2026 1:03 AM UTC
  • 1 reply
  • 19 views

Forum|alt.badge.img+3

When setting up backups for Azure SQL MI the discovery instance is being placed under Object Storage instead of Database.  I am using an Active Directory account that has the access needed to the dabase and a custom role with the correct permissions were applied to the SQL MI instance but, it will not discover any of the MIs.  There are no errors that I’ve found.   Has anyone seen this issue before and what did you do to resolve it.  Also, I am using the hosted optoin (Commvault’s access nodes) and going directly to Airgap storage.  

1 reply

Arvind
Vaulter
Forum|alt.badge.img+7
  • Vaulter
  • Nov 18, 2026 9:30 AM UTC

Good Day ​@JamesACS,
 

This typically points to the Azure cloud account/discovery configuration rather than Airgap storage.
 

A few things to validate:

  • Confirm the Azure account is associated with the subscription containing the SQL Managed Instances and configured for the Database workload, not Object Storage.
  • Verify the custom role includes the required Microsoft.Sql/managedInstances/* read permissions.
  • Since you’re using Commvault-hosted access nodes, verify the SQL MI is reachable through the required public connectivity. If the MI is private-only, a customer-managed access node within the Azure network may be required.
  • Ensure the Region is also selected properly as the Region of the SQL Managed Instance.

Cheers