Limitations in Microsoft Fabric mirrored databases from Azure Databricks (Preview)

This article lists current limitations with mirrored Azure Databricks in Microsoft Fabric.

Network

  • Azure Databricks workspaces shouldn't be behind a private endpoint.
  • Storage accounts containing unity catalog data can't be behind a firewall.
  • 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.

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:

Asia Pacific:

  • Australia East
  • Australia Southeast
  • Central India
  • East Asia
  • Japan East
  • Japan West
  • Korea Central
  • Southeast Asia
  • South India

Europe

  • North Europe
  • West Europe
  • France Central
  • Germany North
  • Germany West Central
  • Norway East
  • Norway West
  • Sweden Central
  • Switzerland North
  • Switzerland West
  • Poland Central
  • Italy North
  • UK South
  • UK West

Americas:

  • Brazil South
  • Canada Central
  • Canada East
  • Central US
  • East US
  • East US2
  • North Central US
  • West US

Middle East and Africa:

  • South Africa North
  • South Africa West
  • UAE North