Skip to content

docs(databricks): require Databricks SQL Access and Workspace Access entitlements #39209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
charlesmyu wants to merge 3 commits into
base: master
Choose a base branch
from
Open

docs(databricks): require Databricks SQL Access and Workspace Access entitlements #39209

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bb38a85
docs(databricks): require Databricks SQL Access and Workspace Access …
charlesmyu Aug 14, 2026
bdbbd4f
docs(databricks): restructure Permissions section into logical subsec…
charlesmyu Aug 14, 2026
fa59b43
docs(databricks): merge Workspace Admin and Granular permissions as a…
charlesmyu Aug 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 19 additions & 9 deletions hugo/content/en/data_observability/jobs_monitoring/databricks/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -460,17 +460,27 @@ DD_LOGS_CONFIG_PROCESSING_RULES=[{\"type\": \"exclude_at_match\",\"name\": \"dro
```

### Permissions
Grant {{< ui >}}Workspace Admin{{< /ui >}} privileges to the user or service principal that connects to your Databricks workspace. This allows Datadog to manage init script installations and updates automatically, reducing the risk of misconfiguration.
The user or service principal that connects to your Databricks workspace must have the following workspace entitlements enabled, in addition to the permissions described below:

If you need more granular control, grant these minimal permissions to the following [workspace level objects][19] to still be able to monitor all jobs, clusters, and queries within a workspace:
- {{< ui >}}Databricks SQL access{{< /ui >}}
- {{< ui >}}Workspace access{{< /ui >}}
Comment on lines +465 to +466

@janine-c janine-c Aug 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- {{< ui >}}Databricks SQL access{{< /ui >}}
- {{< ui >}}Workspace access{{< /ui >}}
- {{< ui >}}Workspace access{{< /ui >}}
- {{< ui >}}Databricks SQL access{{< /ui >}}

Super nitpicky, but I can see that these are in the opposite order elsewhere in the file, and parallelism is just so satisfying (and can make docs easier to act on for users!)


| Object | Permission |
|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Job | [CAN VIEW][20]
| Compute | [CAN ATTACH TO][21]
| Lakeflow Declarative Pipelines | [CAN VIEW][22]
| Query | [CAN VIEW][23]
| SQL warehouse | [CAN MONITOR][24]
#### Workspace permissions

Choose one of the following approaches for the user or service principal:

- **Workspace Admin privileges** (recommended): Grant {{< ui >}}Workspace Admin{{< /ui >}} privileges. This allows Datadog to manage init script installations and updates automatically, reducing the risk of misconfiguration.
- **Granular permissions**: If you need more granular control, grant these minimal permissions to the following [workspace level objects][19] to still be able to monitor all jobs, clusters, and queries within a workspace:

| Object | Permission |

@janine-c janine-c Aug 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the links in this table be moved to the Object column rather than the Permission column? It looks like they all go to pages about the objects rather than the permissions. If there's more nuance here, then disregard!

|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Job | [CAN VIEW][20]
| Compute | [CAN ATTACH TO][21]
| Lakeflow Declarative Pipelines | [CAN VIEW][22]
| Query | [CAN VIEW][23]
| SQL warehouse | [CAN MONITOR][24]

#### Cost data permissions

Additionally, for Datadog to access your Databricks cost data in Data Observability: Jobs Monitoring or [Cloud Cost Management][26], the user or service principal used to query [system tables][27] must have the following permissions:
- `CAN USE` permission on the SQL Warehouse.
Expand Down
Loading