Azure SQL DB Mirror Error

[caomayan]

I am using the SQL gateway connection in Azure SQL Database Managed Instance, and the System Assigned Managed Identity (SAMI) of the Azure SQL Managed Instance has been enabled as primary identity on Azue...Can you please help on the issue? Thank you!

[v-hjannapu]

Hi @caomayan,

I would also take a moment to thank @deborshi_nag  , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Regards,
Community Support Team.

[v-hjannapu]

Hi @caomayan,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.


Regards,
Community Support Team.

[deborshi_nag]

Hello @caomayan

You can start by checking a couple of things:

1. The Managed Instance build doesn’t have the required managed‑identity objects

When Fabric sets up mirroring, it queries internal system objects on the Managed Instance to discover the managed identity. If those objects don’t exist, SQL returns an “Invalid object name” error, which Fabric surfaces as “Unable to retrieve SQL Server managed identities”. This almost always means the Managed Instance is not on a recent enough platform build.

 

You can quickly confirm this by running the following on the MI (typically in master):

SELECT @@VERSION;

SELECT name, type_desc

FROM sys.all_objects

WHERE name LIKE '%managed%identit%';

If no managed‑identity related system objects are returned, update the Managed Instance to the latest servicing level and try the mirroring setup again.

 

2. The gateway connection doesn’t have server‑level visibility

Fabric also needs to read server‑scoped metadata/DMVs during mirroring setup. If the login used by the SQL gateway connection can’t see server‑level state, Fabric fails during the identity discovery step.

The fix to grant server visibility to the gateway identity.

GRANT VIEW SERVER STATE TO [gateway_login_or_principal];

Once the Managed Instance is on a compatible build and the gateway identity has VIEW SERVER STATE, Fabric can successfully retrieve the managed identity and the mirroring setup completes without errors.

[caomayan]

Thanks so much @deborshi_nag for the quick reply, I have forwarded your comments to the users, will see if it works then accept as a solution! 🙂