OneLake Catalog
Description
Microsoft OneLake is the unified data lake for Microsoft Fabric. Onehouse integrates with OneLake to sync table metadata, enabling your Onehouse-managed tables to be queried and governed through Microsoft Fabric workspaces.
OneLake catalogs sync data using ADLS Shortcuts, which create references to your Onehouse table storage locations within a Fabric workspace.
Onehouse also supports connecting to OneLake for Access Control Sync, allowing you to import, manage, and sync data privileges between OneLake and your other catalogs.
Cloud Provider Support
- Azure (BYOK): ✅ Supported
- AWS: ❌ Not supported
- GCP: ❌ Not supported
OneLake catalogs are available for projects deployed via the Quanton Operator on Azure or similar BYOK environments.
Prerequisites
Before creating an OneLake catalog in Onehouse, ensure the following:
- A Microsoft Fabric workspace with a Lakehouse or Mirrored Azure Databricks UC item.
- A Microsoft Entra ID (Azure AD) application registered as a service principal with access to the Fabric workspace.
- The service principal's Tenant ID, Client ID, and Client Secret.
- The Workspace ID and Item ID from your Fabric workspace.
- OneLake Security must be enabled on your Lakehouse if using Access Control Sync. Refer to the Microsoft docs for details.
- Your Lakehouse must be schema-enabled (standard three-part hierarchy:
lakehouse.schema.table). Schema-disabled Lakehouses are not supported.
Only Lakehouses are supported. Warehouses are not supported for Access Control Sync, as OneLake Security is not available for Warehouses.
Setup Guide
- Navigate to Connections > Catalogs and click Add New Catalog.
- Select OneLake Catalog as the catalog type.
- Enter a Name to identify the catalog in Onehouse.
- Complete the following configuration fields:
| Field | Description |
|---|---|
| Workspace ID | The Microsoft Fabric workspace ID where tables will be synced. |
| Item Type | The type of Fabric item to sync to. Options: Lakehouse or Mirrored Azure Databricks UC. |
| Item ID | The ID of the target Lakehouse or Mirrored catalog item within the workspace. |
| Tenant ID | The Microsoft Entra ID (Azure AD) tenant ID for authentication. |
| Client ID | The application (service principal) client ID. |
| Client Secret | The application (service principal) client secret. |
| Sync Method | The method used to sync data. Currently supports ADLS Shortcut, which creates Azure Data Lake Storage shortcuts pointing to your Onehouse table locations. |
| ADLS Connection ID | (Optional) The ADLS connection ID to use when creating shortcuts. Required when the sync method is set to ADLS Shortcut. |
- Click Create to register the catalog.
Syncing Tables
After creating the OneLake catalog, attach it to your Flows or configure a Metadata Sync table service to sync table metadata to OneLake.
Tables synced to OneLake are accessible through Microsoft Fabric for querying, governance, and integration with other Fabric services such as Power BI, Synapse, and Data Factory.
Permissions
Creating an OneLake catalog requires the Project Admin role or equivalent permissions.