Data Sources
Databricks
Databricks API token boundaries, workspace evidence, and troubleshooting.
Databricks
Noru connects to Databricks with a customer-provided API token. The token should belong to a principal with read-only workspace access.
Permission reference
Prop
Type
Setup
Create or select a Databricks service principal or user with read-only access.
Create an API token for that principal.
Enter the workspace URL and token in Noru.
Run the first sync and review workspace, user, cluster, job, and configuration evidence.
What Noru collects
- workspace inventory and configuration metadata
- users, groups, permissions, clusters, jobs, and related governance metadata where supported
- provider IDs and timestamps for evidence tracking
What Noru does not collect
- write access unless the token owner has it
- notebook source, query results, or table data unless the token and collector implementation explicitly allow it
- secrets stored in Databricks secret scopes
Evidence produced
Databricks evidence supports data platform inventory, access review, job governance, workspace configuration, and security controls.
Troubleshooting
Disconnect behavior
Disconnecting stops future syncs. Revoke the token in Databricks to remove provider-side authorization.
Scope minimization
Use a dedicated service principal, avoid personal admin tokens, and review workspace entitlements before connecting.