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

Each Azure subscription should have two or three owners

  • Level 1
  • Identity Services

This check counts the identities that hold the Owner role on each Azure subscription. The safe setting is to have two or three owners, which keeps a backup if one person is unavailable without spreading full control too widely.

Why it matters

The Owner role can do everything on a subscription, including granting access to other people. That makes it the most powerful role there is at that scope, and every extra owner is one more identity whose compromise would give an attacker complete control of the subscription.

Having too few owners is a problem of its own. If a subscription has a single owner and that person leaves, loses access or is locked out, nobody can manage access to it without a lengthy recovery process. Microsoft's guidance on Azure role-based access control recommends limiting the number of subscription owners to a small number, with a maximum of three, and giving people the least privilege they need (Best practices for Azure RBAC). Two or three owners balances resilience and exposure.

How to check it yourself

In the Azure portal, open Subscriptions, select the subscription, then Access control (IAM) > Role assignments, and filter the Role column by Owner. Note whether each entry is a user, a group or a service principal, and whether it is assigned at this scope or inherited from above.

With the Azure CLI, this read-only command lists owner assignments, including inherited ones:

az login
az role assignment list --role Owner --scope "/subscriptions/<SUBSCRIPTION_ID>" --include-inherited --query "[].{principal:principalName, type:principalType, scope:scope}" --output table

Count the rows. If an owner is a group, expand the group's membership, because the people in it are owners too.

How to fix it

If there are more than three owners, go to Access control (IAM) > Role assignments, select the assignments that are not needed and choose Remove. Replace broad access with a narrower role, such as Contributor or a specific service role, where people only need to work with resources and not manage access.

If there is only one owner, add a second named person or a small group. With the Azure CLI, an administrator can run the following after reviewing it:

az role assignment create --assignee "<USER_OR_GROUP_OBJECT_ID>" --role Owner --scope "/subscriptions/<SUBSCRIPTION_ID>"
az role assignment delete --assignee "<OBJECT_ID_TO_REMOVE>" --role Owner --scope "/subscriptions/<SUBSCRIPTION_ID>"

ConfigCobra itself never writes to your Azure; it only reads role assignments and shows you the steps above.

What changes when you fix it

People whose Owner assignment is removed lose the ability to grant or remove access and to change anything that needs owner rights on that subscription. If they still need to deploy and manage resources, give them Contributor first, so that their daily work does not stop.

Automation needs a check too. Pipelines, deployment tools and service principals are sometimes given Owner because it was the easy option, and removing it can make a deployment fail on the next run, particularly if the deployment creates role assignments. Find out which identities deploy to the subscription before you remove anything, and give those a narrower role that still covers what they do. Adding a second owner changes nothing for existing users, but that person gains full control, so choose someone accountable and make sure their account is protected with multifactor authentication.

Included in

BenchmarkCIS IDProfile
CIS Microsoft Azure Foundations v6.0.05.7Level 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