Introduction
In my latest article, I show how you can store Azure Databricks tables directly in Microsoft OneLake. I cover the required configuration steps in both Databricks and Microsoft Fabric and guide you through the entire setup process. You’ll also learn how to expose those tables through a Lakehouse, making them easy to access and reuse for analytics, reporting, and other data projects. I also show how data can be written from Microsoft Fabric to Azure Databricks and from Azure Databricks back to Microsoft Fabric.
Important this feature is still in preview (2026/09/04)!
What are the Requirements?
- Azure Databrick Workspace (You can use the Trial Premium – 14-Days Free DBUs pricing tier for a Demo
- Microsoft Fabric Workspace with F, P or TRIAL Capacity assgined
- Databricks Workspace must be enabled for Unity Catalog
- Fabric Administrator muss enable Users can create Azure Databricks Storage items in Tenant Settins
- Target Workspace must have Authenticate with OneLake user-delegated SAS tokens enabled in Workspace settings. You find this in Delegated settings and OneLake settings
- CREATE STORAGE CREDENTIAL privilige on the Unity Catalog metastore and CREATE EXTERNAL LOCATION privilige on both the metastore and the storage credential.
