Forum Discussion
Mirrored Azure Databricks Catalog bug?
Hi All,
Thankyou for your suggestions!
With help from Microsoft support, I have now identified the root cause.
The issue is a limitation in using guest accounts with Mirrored Azure Databricks Catalogs.
To summarize, I have two Entra Id tenants A and B in my setup, applied as follows:
- Entra Id tenant A hosts my Fabric and Databricks workspaces.
- Entra Id tenant B contains the organisational account I was using to create the Mirrored Azure Databricks Catalog. That is, the account is a guest in Entra Id tenant A.
It turns out that this configuration is not supported by the current version of Mirrored Azure Databricks Catalog.
The fix is to use either a service principal or an organisational member account from tenant A to setup the connection.
Personally, I would appreciate a more general support for multi-tenant setups, as multi-tenancy is a fact of life in my organisation. Therefore, I have often run into limitations of this kind. One day I might even learn to check for this as a matter of course :).
Best Regards,
Søren
Hi All,
Thankyou for your suggestions!
With help from Microsoft support, I have now identified the root cause.
The issue is a limitation in using guest accounts with Mirrored Azure Databricks Catalogs.
To summarize, I have two Entra Id tenants A and B in my setup, applied as follows:
- Entra Id tenant A hosts my Fabric and Databricks workspaces.
- Entra Id tenant B contains the organisational account I was using to create the Mirrored Azure Databricks Catalog. That is, the account is a guest in Entra Id tenant A.
It turns out that this configuration is not supported by the current version of Mirrored Azure Databricks Catalog.
The fix is to use either a service principal or an organisational member account from tenant A to setup the connection.
Personally, I would appreciate a more general support for multi-tenant setups, as multi-tenancy is a fact of life in my organisation. Therefore, I have often run into limitations of this kind. One day I might even learn to check for this as a matter of course :).
Best Regards,
Søren
Hi SørenBrandt,
Thank you so much for back and sharing the details of your findings with the community. This is valuable, since others who might run into the same limitation with guest accounts and Mirrored Azure Databricks Catalogs will now have a clear reference point.
You have summarized the tenant setup and the resolution (using a service principal or an organizational member account from the hosting tenant) clearly. I agree with you, multi-tenant scenarios are common, and your feedback about broader support for these setups is valid.
Refer this link: https://learn.microsoft.com/en-us/fabric/database/mirrored-database/azure-databricks-limitations
Hope this helps. If you have any doubts regarding this, please feel free to ask here. We will be happy to help.
Thank you for using the Microsoft Community Forum.