> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/2025.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/2025.1/configuration/integrations/databricks/databricks-unity-catalog/unity-catalog.md).

# Getting Started with Databricks Unity Catalog

The how-to guides linked on this page illustrate how to integrate Databricks Unity Catalog with Immuta. See the [reference guide](/2025.1/configuration/integrations/databricks/databricks-unity-catalog/unity-catalog-overview.md) for information about the Databricks Unity Catalog integration.

**Requirements**:

* Unity Catalog [metastore created](https://docs.databricks.com/data-governance/unity-catalog/create-metastore.html) and attached to a Databricks workspace. Immuta supports configuring a single metastore for each configured integration, and that metastore may be attached to multiple Databricks workspaces.
* Unity Catalog enabled on your Databricks cluster or SQL warehouse. All SQL warehouses have Unity Catalog enabled if your workspace is attached to a Unity Catalog metastore.

{% stepper %}
{% step %}
**Connect your technology**

These guides provide instructions on getting your data set up in Immuta.

1. [Register your Databricks Unity Catalog connection](/2025.1/configuration/integrations/databricks/databricks-unity-catalog/how-to-guides/register-a-databricks-unity-catalog-connection.md): Using a single setup process, connect Databricks Unity Catalog to Immuta. This will register your data objects into Immuta and allow you to start dictating access through global policies.
2. [Organize your data sources into domains and assign domain permissions to accountable teams](/2025.1/configuration/domains/configure-domains.md): Use domains to segment your data and assign responsibilities to the appropriate team members. These domains will then be used in policies, audit, and identification.

{% hint style="info" %}
Connections are generally available on all 2025.1+ tenants. If you do not have connections enabled on your tenant, [configure Databricks Unity Catalog](/2025.1/configuration/integrations/databricks/databricks-unity-catalog/how-to-guides/configure.md) and [register data sources](/2025.1/configuration/integrations/registering-metadata/data-sources/register-data-sources/databricks-tutorial.md) using the legacy workflow.
{% endhint %}
{% endstep %}

{% step %}
**Register your users**

These guides provide instructions on getting your users set up in Immuta.

1. [Connect an IAM](/2025.1/configuration/people/getting-started.md): Bring the IAM your organization already uses and allow Immuta to register your users for you.
2. [Map external user IDs from Databricks to Immuta](/2025.1/configuration/people/immuta-users/how-to-guides/external-user-mapping.md): Ensure the user IDs in Immuta, Databricks, and your IAM are aligned so that the right policies impact the right users.
   {% endstep %}

{% step %}
**Add data metadata**

These guides provide instructions on getting your data metadata set up in Immuta.

1. [Connect an external catalog](/2025.1/configuration/manage-data-metadata/catalogs/configure.md): Bring the external catalog your organization already uses and allow Immuta to continually sync your tags with your data sources for you.
2. [Run identification](/2025.1/developer-guides/the-immuta-cli/manage-sensitive-data-discovery/sdd.md): Identification allows you to automate data tagging using identifiers that detect certain data patterns.
   {% endstep %}

{% step %}
**Start using the Governance app**

These guides provide instructions on using the Governance app for the first time.

1. [Author a global subscription policy](/2025.1/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents/how-to-guides/subscription-policy-tutorial.md): Once you add your data metadata to Immuta, you can immediately create policies that utilize your tags and apply to your tables. Subscription policies can be created to dictate access to data sources.
2. [Author a global data policy](/2025.1/governance/author-policies-for-data-access-control/authoring-policies-in-secure/data-policies/how-to-guides/data-policy-tutorial.md): Data metadata can also be used to create data policies that apply to data sources as they are registered in Immuta. Data policies dictate what data a user can see once they are granted access to a data source. Using catalog and identification applied tags you can create proactive policies, knowing that they will apply to data sources as they are added to Immuta with the automated tagging.
3. [Configure audit](/2025.1/governance/detect-your-activity/audit/reference-guides/universal-audit-model-uam.md): Once you have your data sources and users, and policies granting them access, you can set up audit export. This will export the audit logs from user queries, policy changes, and tagging updates.
   {% endstep %}
   {% endstepper %}


---

# 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://documentation.immuta.com/2025.1/configuration/integrations/databricks/databricks-unity-catalog/unity-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.