> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](/platform/deploy/azure-cloudprem/deploy-workspace)). 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/catalogs/register-and-manage-catalogs).

## Next step

Continue to [Create a cluster](/platform/deploy/azure-cloudprem/create-cluster).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.