Microsoft Fabric

Connect e6data to Microsoft Fabric to query data stored in OneLake. e6data reads metadata from your Fabric workspace and accesses the underlying data directly from OneLake using your Azure credentials.

Before you start

A Microsoft Fabric workspace with the data you want to query.
An Azure AD app registration with permissions on the Fabric workspace.
The Workspace ID, OneLake account name, and OAuth credentials for the app registration.
The ADLS Gen2 storage account holding the underlying OneLake data.
For Serverless, your e6data workspace must already have storage access granted.

Connect to Microsoft Fabric

Navigate to the Catalogs section from the sidebar and click Create Catalog.
Enter a Catalog Name. The name must be unique within the workspace. Lowercase letters, numbers, and hyphens are recommended.
Select Catalog Type as Microsoft Fabric.
(Optional) Enable Governance. Apply fine-grained access control using Ranger, OPA, Unity, or Lake Formation.
Provide the Microsoft Fabric and OneLake connection details:
Field
Description
Workspace ID
Your Microsoft Fabric workspace identifier
OneLake Account Name
The OneLake account hosting your data (for example, onelake.dfs.fabric.microsoft.com)
OneLake Client ID
Client ID of the Azure AD app registration with access to OneLake
OneLake Client Secret
Client Secret for the same app registration
OneLake Client Endpoint
The OAuth2 token endpoint, typically https://login.microsoftonline.com/{tenant-id}/oauth2/token
Azure Tenant ID
The Azure AD tenant ID
Azure Client ID
Client ID used to access the underlying ADLS Gen2 storage
Azure Storage Account Name
The storage account where OneLake data resides
Click Test Connection to verify connectivity. The form validates that the catalog name, Workspace ID, Client ID, and Tenant ID are provided.
After a successful test, select the schemas you want this catalog to expose. You can change this later.
Click Create Catalog. The catalog appears in the catalogs list.
(Optional) Click Reset at any time to clear all entered fields.

Cross-tenant Fabric access

If your Microsoft Fabric workspace is in a different Azure tenant than where e6data has been granted access:

In the catalog form, enable Cross-Account Connection.
Provide the Tenant ID (where Fabric lives), the Client ID of the Managed Identity or service principal with access to that tenant's OneLake, and the Storage Account Name in that tenant.

This is the same pattern used for cross-tenant Hive, Unity, and Polaris catalogs.

Edit a Microsoft Fabric catalog

Edit a Fabric catalog to update which schemas it exposes, rotate credentials, or change governance settings.

Open the Catalogs page in the Compute Plane.
Find the Fabric catalog, click the row actions (⋮), and click Edit.
Update what you need - selected schemas, OneLake Client Secret (to rotate the credential), Cross-Account Connection, or Governance settings.
Click Test Connection if you changed credentials or cross-account settings.
Click Update Catalog.

A successful Test Connection is required before saving if you changed the OneLake Client ID/Secret/Endpoint, Tenant ID, Workspace ID, Storage Account, or the Cross-Account Connection toggle. Schema-selection and display-name changes don't require a re-test. Schema changes apply immediately; credential rotation is seamless; a cross-account toggle change may interrupt the next query while routing updates (typically a single retry resolves it).

Delete a Microsoft Fabric catalog

Open the Catalogs page, find the Fabric catalog, click the row actions (⋮), and click Delete. Confirm.

Deletion removes the catalog from this workspace; attached clusters lose access. The underlying Fabric workspace, OneLake data, and Azure AD app registration are not modified.