Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article lists current limitations with mirrored Azure Databricks in Microsoft Fabric.
Network
- Azure Databricks workspaces shouldn't be behind a private endpoint.
- Azure Databricks IP Access lists aren't supported.
Supported Spark Versions
Fabric Runtime Version needs to be at least Spark 3.4 Delta 2.4. Verify in Workspace Settings, Data Engineering/Science, Spark Settings, Environment Tab.
Limitations
- Mirrored Azure Databricks item doesn't support renaming schema, table, or both when added to the inclusion or exclusion list.
- Azure Databricks workspaces shouldn't be behind a private endpoint.
- Azure Data Lake Storage Gen 2 account that is utilized by your Azure Databricks workspace must also be accessible to Fabric.
- Azure Mirrored Databricks Catalog does not support Manage Catalog functionality if OneLake security is enabled on that item. This functionality is coming in November, 2025.
The following table types are not supported:
- Tables with RLS/CLM policies
- Lakehouse federated tables
- Delta sharing tables
- Streaming tables
- Views, Materialized views
Supported regions
Here's a list of regions that support mirroring for Azure Databricks Catalog:
Americas:
- Brazil South
- Canada Central
- Canada East
- Mexico Central
- Central US
- East US
- East US2
- North Central US
- West US
- West US 2
- West US 3
Asia Pacific:
- East Asia
- Southeast Asia
- Australia East
- Australia Southeast
- Central India
- South India
- Japan East
- Japan West
- Korea Central
Europe, Middle East, and Africa:
- North Europe
- West Europe
- France Central
- Germany North
- Germany West Central
- Israel Central
- Italy North
- Norway East
- Norway West
- Poland Central
- Spain Central
- Sweden Central
- Switzerland North
- Switzerland West
- South Africa North
- South Africa West
- UAE North
- UK South
- UK West