Connect ADLS and catalog
Create a catalog over your ADLS Gen2 data in a Serverless e6data workspace on Azure, using a shared Storage Credential.
A catalog connects e6data to a metastore that describes your databases, tables, and columns; your ADLS Gen2 data is reached through the Storage Credential you registered. This page covers connecting a catalog on Azure Serverless. For the full catalog reference and all types, see Catalogs.
Before you start
Make sure you've configured Azure access: a Managed Identity with Storage Blob Data Reader, registered as a Storage Credential that shows Connected.
Connect a catalog
In the Compute Plane, open Catalogs → Create Catalog.
Enter a unique Catalog Name (lowercase letters, numbers, and hyphens).
Select the Catalog Type:
Catalog typeKey fieldsHive Metastore
Metastore Host / Port
Databricks Unity
Workspace Host, Access Token
Apache Polaris
Polaris Host, Client ID, Client Secret
Iceberg REST
Catalog URI, Warehouse, Prefix, Authentication
Microsoft Fabric
Workspace ID, OneLake account / client / secret / endpoint
For storage access, choose Use shared Storage Credential (recommended) or enable Cross-Account Access for a different identity or tenant.
(Optional) Enable Governance (Ranger, OPA, Unity, or Lake Formation).
Select Test Connection, choose the schemas to include, and select Create Catalog.
The catalog is now available to attach to clusters. For per-catalog detail, see the guides under Catalogs.
See also
Last updated
Was this helpful?

