Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Microsoft Azure Foundations v6.0.0 · 2.1.12

Azure Databricks groups should be reviewed on a regular schedule

  • Level 1
  • Analytics Services

This check looks at the groups and their members in your Azure Databricks workspaces. The safe setting is a recurring review, so that people who changed role or left no longer hold access through an old group.

Why it matters

Databricks groups decide who can open notebooks, run clusters and read data. Memberships are easy to add and rarely cleaned up, so over time a group collects people who no longer need what it grants. A leaver or a person who moved teams then keeps access that nobody intended. A regular review keeps group membership in line with what people actually do.

Databricks documents groups as the recommended way to manage permissions, which also means the group list is the right place to look when you want to know who can reach what.

Source: Microsoft Learn, Manage groups for Azure Databricks.

How to check it yourself

In the Azure Databricks account console, open User management and then Groups. Open each group and read its member list. In a single workspace, the admin settings have an Identity and access section with the same information.

The Databricks CLI can list groups without changing anything. Run it against a test workspace first.

databricks account groups list
databricks account groups get <group-id>

Compare each member list against your current staff list and the purpose of the group. Note when the list was last reviewed and by whom, because the review itself is the safe setting.

How to fix it

Portal: for each group in User management, remove members who no longer need it, delete groups that nobody uses, and give each group an owner who is responsible for it. If you sync identities from Microsoft Entra ID, change membership there so the next sync does not undo your edit.

Script: removal can be done with the Databricks CLI or the SCIM API. ConfigCobra itself never changes your environment; it only reads and points to the fix.

databricks account groups delete <group-id>

Put a recurring task in your team calendar so the review actually happens, for example each quarter, and keep a short note of what was removed.

What changes when you fix it

People removed from a group lose the access that group gave them: workspace folders, cluster policies or data permissions. If someone was relying on a group by accident, their jobs or notebooks can start to fail with permission errors.

Before removing anyone, ask the group owner or the person's manager, and check whether scheduled jobs run as that person. Deleting a group that is referenced in permissions on other objects will remove those permissions too, so look at where a group is used before you delete it.

Included in

BenchmarkCIS IDProfile
CIS Microsoft Azure Foundations v6.0.02.1.12Level 1

Check this on your Microsoft Azure

ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial