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