Azure sql managed instance mirror to Fabric - Error

[jmalcober]

Hello Community,

I am facing an issue while attempting to mirror an Azure SQL Database to Fabric OneLake. During the process, I encountered the following error:

The database cannot be mirrored to Fabric due to below error: A database operation failed with the following error: 'Invalid object name 'sys.dm_server_managed_identities'.' Invalid object name 'sys.dm_server_managed_identities'., SqlErrorNumber=208,Class=16,State=1,

when i execute SELECT * FROM sys.dm_server_managed_identities; in ssms i get Msg 208, Level 16, State 1, Line 1
Invalid object name 'sys.dm_server_managed_identities'.

The data base is stored in a azure sql managed instance.

Any guidance or recommendations from the community would be greatly appreciated!

Thnks in advance

[AndyDDC · Accepted solution]

Hi @jmalcober currently only Azure SQL Database is supported with Fabric Mirroring, no support yet for Managed Instance

[tlanza89_RWL]

Hi @AndyDDC  I see that you said "yet". Is there any plan to support a Managed Instance in the future?

[MichaelCrocker]

Hi @jmalcober  

We're facing similar challenge with Fabric and SQL MI. Very frustrating. Hopefully Microsoft will resolve it soon. 

[barcoyolo]

It does support it now...Microsoft Fabric Mirrored Databases From Azure SQL Managed Instance (Preview) - Microsoft Fabric | M... but still have the same error occuring

[DataBard]

Hi @barcoyolo ,

Can you confirm if you have a public endpoint available to connect to your Managed Instance? The current preview does not support connecting to your Managed Instance via a private endpoint.

[gcarvalho]

Having the same issue here, we do have a public endpoint setup and I can connect to the server from Dataflow Gen2, Power Query, or Notebooks, but mirroring won't work.

[gcarvalho]

@barcoyolo I'm not sure if you were able to get it to work, but I was finally able to after trying everything under the sun. To be more specific we tried everything until we changed the policy to be Always up to date, that made it work like magic.

1. Enable System Assigned Managed Identity

2. Updated the Policy for source Azure SQL Managed Instance configured to "Always up to date"

https://learn.microsoft.com/en-us/fabric/database/mirrored-database/azure-sql-managed-instance-tutor...

https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/update-policy?view=azuresql&prese...