> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/organizational-setup/connector-onboarding-guide/databricks.md).

# Databricks

This guide sets up the Databricks connector using an **account-level service principal** with OAuth machine-to-machine (M2M) authentication. It works for Databricks on AWS, Azure, and Google Cloud. Datalogz reads metadata from your workspaces and Unity Catalog; it never accesses the data inside your tables.

### Step 1: Create a service principal in Databricks

1. In the Databricks **account console**, create a new service principal.
2. Grant it the **account admin** role. This is required for Datalogz to enumerate workspaces and read Unity Catalog metadata.
3. Generate an **OAuth secret** for the service principal and note the **Client ID** and **Secret**.

### Step 2: Create the connector in Control Tower

1. Sign in to Datalogz Control Tower and go to **Settings > BI Connectors**.
2. Click **New Connector** and select **Databricks**.
3. Enter your Databricks **account ID** and the service principal's **Client ID** and **Secret**, then click **Connect**.
4. Select the **workspaces** you want to monitor.
5. Select a **SQL warehouse** for metadata queries. Serverless warehouses are preferred and selected automatically when available.
6. Enter a **Connector Name** and select the snapshot frequency (for example Daily or Weekly).
7. Click **Next**, then **Confirm and Finish**.

{% hint style="info" %}
Control Tower ingests workspaces, Unity Catalog tables and columns, volumes, functions, Genie (AI/BI) Spaces, and SQL warehouses. Large Unity Catalog estates can take a while on the first sync.
{% endhint %}

For questions or help with this setup, contact <support@datalogz.io>.


---

# 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.datalogz.io/guides/organizational-setup/connector-onboarding-guide/databricks.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.