> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/connect-adls-and-catalog.md).

# 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](/query-engine/guides/deployment/azure-serverless/configure-azure-access.md) you registered. This page covers connecting a catalog on Azure Serverless. For the full catalog reference and all types, see [Catalogs](/query-engine/guides/catalogs.md).

## Before you start

Make sure you've [configured Azure access](/query-engine/guides/deployment/azure-serverless/configure-azure-access.md): a Managed Identity with **Storage Blob Data Reader**, registered as a **Storage Credential** that shows **Connected**.

## Connect a catalog

1. In the Compute Plane, open **Catalogs → Create Catalog**.
2. Enter a unique **Catalog Name** (lowercase letters, numbers, and hyphens).
3. Select the **Catalog Type**:

   | Catalog type     | Key fields                                                 |
   | ---------------- | ---------------------------------------------------------- |
   | Hive 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 |
4. For storage access, choose **Use shared Storage Credential** (recommended) or enable **Cross-Account Access** for a different identity or tenant.
5. (Optional) Enable **Governance** (Ranger, OPA, Unity, or Lake Formation).
6. 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](/query-engine/guides/catalogs.md).

## See also

* [Create a cluster](/query-engine/guides/deployment/azure-serverless/create-cluster.md)
* [Catalogs](/query-engine/guides/catalogs.md)
* [Configure Azure access](/query-engine/guides/deployment/azure-serverless/configure-azure-access.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/connect-adls-and-catalog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.