> 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-in-vpc/register-catalog.md).

# Register catalog

Grant the In-VPC engine access to your data and register a catalog in your Azure-hosted e6data workspace.

With the workspace deployed, connect your data so you can query it. This has two parts: granting the engine access to your storage, and registering a catalog in the Compute Plane.

## Grant data access

The In-VPC engine reads your data through Azure Workload Identity. The workspace's engine service account is federated with a Managed Identity that holds **Storage Blob Data Contributor** on the metadata account (configured during [deployment](/query-engine/guides/deployment/azure-in-vpc/deploy-workspace-and-e6data.md)). To query a data lake, grant that same identity **Storage Blob Data Reader** on each storage account that holds data you want to read. For data in a **different Azure tenant**, use the cross-tenant pattern (Tenant ID, Client ID, Storage Account Name) when registering the catalog.

## Register the catalog

1. Open the workspace's Compute Plane and go to the **Catalogs** section.
2. Select **Create Catalog** and choose your **Catalog Type** - Hive Metastore, Databricks Unity, Microsoft Fabric, Apache Polaris, or Iceberg REST.
3. Provide the connection details. For cross-tenant data, enable **Cross-Account Connection** and supply the Tenant ID, Client ID, and Storage Account Name.
4. Select **Test Connection**, choose the schemas to include, and select **Create Catalog**.

For the full set of catalog types and their settings, see [Catalogs](/query-engine/guides/catalogs.md).

## Next step

Continue to [Create a cluster](/query-engine/guides/deployment/azure-in-vpc/create-cluster.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-in-vpc/register-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.