Forum Discussion
Mirrored Azure Databricks catalog not available
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 ,
400 error typically indicates that the API call from Fabric to Databricks failed due to:
Incorrect or missing authentication headers /misconfigured cluster or workspace settings/unsupported request payloads.
You can perform these checks-
1.Check User Permissions-Ensure your account has access to Unity Catalog and validate that the account is active.
2.Review Logs- Look for specific error codes or patterns in Fabric diagnostic logs.
3.Confirm that no firewall or security group is blocking access between Fabric and Databricks.
4. Double-check the Unity Catalog setup and any recent changes.
Refer- Microsoft Fabric Mirrored Databases From Azure Databricks Security - Microsoft Fabric | Microsoft Learn
Also, check-out the limitations here
Limitations in Microsoft Fabric Mirrored Databases From Azure Databricks - Microsoft Fabric | Microsoft Learn
Even if get the same error consider raising a Support ticket with detailed logs and session IDs.
Microsoft Fabric service status
Hope this helps!
Hi v-sdhruv,
Thank you for your suggestions!
Unfortunately, I have been unable to identify any issues in my configuration so far.
However, it turns out that my issue connecting from Fabric to Databricks applies to more than just mirrored catalogs: As a short-term workaround to my problem with setting up a mirrored catalog, I tried to copy data from Databricks to Fabric using a pipeline. This also does not work, and the information available to me is somewhat puzzling because it suggest that the request from Fabric is received and processed by Databricks, but the response is not received or understood by Fabric:
1. On the Databricks side, the log suggests that the Warehouse received the catalog query from Fabric, and returned a set of results.
2. On the Fabric side, the error message indicates that the SQL Warehouse in Databricks does not exist. However, the SQL Warehouse that Fabric claims to not exist is the very one that receives and processes the request from Fabric.
Here's a couple of screenshots to document my observations.
Fabric says:
Databricks says:
Any help would be greatly appreciated!
BR,
Søren