An Azure service that provides fine-grained access management for Azure resources, enabling you to grant users only the rights they need to perform their jobs.
For a small team, the supported path is to have an existing workspace admin or account admin assign the Databricks workspace admin role to the person who will handle cleanup.
Key points:
- Who can grant access
- Only account admins or workspace admins can manage users.
- Workspace admins have admin privileges within a single workspace and can manage workspace-level identities and settings.
- The workspace admin role can be assigned only to individual users or service principals, not to a group.
- How to assign workspace admin access
- In the Azure Databricks workspace, a current workspace admin can go to: Username in top bar → Settings → Identity and access → Users → Manage
- Select the user.
- Under Entitlements, turn on Admin access.
- Alternative account-level path
- An account admin can also manage access from the account console and assign users to workspaces.
- Account admins can delegate both account admin and workspace admin roles.
- If no account admin is known
- A Microsoft Entra ID Global Administrator can establish the first Databricks account admin by signing in to the account console at
https://accounts.azuredatabricks.net. - After that, the new account admin can assign the needed admin roles.
- A Microsoft Entra ID Global Administrator can establish the first Databricks account admin by signing in to the account console at
- For cleanup and orphaned assets
- Workspace admin is the appropriate day-to-day role for tasks such as adding and removing users, managing workspace access, and handling workspace administration.
- Databricks recommends limiting the number of workspace admins and using groups for ongoing access management where possible.
- If the goal is access to data or assets owned by inactive users
- Many organizations manage permissions through synced groups.
- If teammates already have the needed access, a workspace admin can add the cleanup user to the correct group.
References: