Azure Databricks tables can now sit in OneLake for Fabric to read
Reviewed by Helen Jones
Azure Databricks now lets Unity Catalog managed tables use OneLake as an external location while in beta. A separate preview lets users publish mirrored catalogs from Databricks into Fabric. Fabric can query the same Delta tables through SQL, notebooks, and Power BI. Tables stay read-only inside Fabric and metadata syncs on a schedule or manual refresh. The setup removes the need to copy data between platforms, but security rules and governance still need separate configuration in each tool.
Until now, teams that wanted both Databricks and Fabric kept two copies of the data and built pipelines to keep them in sync. Any change in one system arrived late or inconsistently in the other. The new arrangement removes the copy step for teams already committed to both platforms. For reporting owners who still pull most numbers from Excel files, SharePoint lists, or simple exports, the change does not touch their current refresh problems or KPI definitions.
Analysis
Ignore the integration story until you can name the exact source system behind each KPI in your monthly pack. Spend the next week listing every file or query that actually feeds your reports and mark which ones would ever justify moving into Databricks.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Azure Databricks tables can now sit in OneLake for Fabric to read", Collab365 Spaces. 2 sources referenced.