Skip to content
Least Privilege Principle

Least privilege for Azure Key Vault means one vault per application and environment, with Secrets User or Crypto User

Key Vault has a management plane and a data plane that are authorized separately. Microsoft's documentation, read 16 Nov 2026, recommends one vault per application per environment with data plane roles assigned at the vault scope, and names Key Vault Secrets User for reading secrets.

Open the calculator ยท All services

Key Vault authorizes its management plane and data plane separately

Microsoft's documentation says both planes use Microsoft Entra ID for authentication. The control plane uses Azure RBAC for authorization. The data plane uses either a Key Vault access policy (the legacy model) or Azure RBAC for data plane operations.

The two planes work independently. A user can hold read access to vault properties and tags without any access to keys, secrets or certificates. Changing a vault from access policies to the Azure RBAC permission model needs unrestricted Microsoft.Authorization/roleAssignments/write, which is part of the Owner and User Access Administrator roles.

Microsoft recommends a vault per application per environment (development, pre-production, production), with roles assigned at the key vault scope.

The identities that call this service (people, services, workloads, third parties) are covered in the Azure service identities guide and the workload identities guide.

Roles and patterns to avoid, with the documented reason

Most over-grants in Key Vault come from the control plane reaching into the data plane.

  • Contributor on a vault that still uses access policies: Microsoft's documentation says a user with Contributor on the control plane can grant themselves data plane access by setting an access policy, and that Contributor access to key vaults should be tightly controlled.
  • Key Vault Administrator: Microsoft describes it as all data plane operations on a vault and all objects in it. Reserve it for few people.
  • Roles on individual keys, secrets or certificates: Microsoft says this is not recommended, except where individual secrets need individual user access or must be shared between applications.
  • Object-scope assignments as tenant isolation: Microsoft's FAQ says administrative operations such as network access control and monitoring need vault-level permissions, so object-level assignment does not isolate application teams.

A minimal binding for an application that reads secrets

An application that reads secret values at start-up needs Key Vault Secrets User on its own vault. Role names and IDs come from Microsoft's Key Vault RBAC guide.

TaskBuilt-in roleRole IDWhat Microsoft says it allows
Read secret valuesKey Vault Secrets User4633458b-17de-408a-b874-0445c86b69e6Read secret contents, including the secret portion of a certificate with private key
Use a key for cryptographic operationsKey Vault Crypto User12338af0-0e69-4776-bea7-57ae8d297424Perform cryptographic operations using keys
Wrap and unwrap for storage encryptionKey Vault Crypto Service Encryption Usere147488a-f6f5-4113-8e2d-b22465e65bf6Read metadata of keys and perform wrap and unwrap operations
Read metadata onlyKey Vault Reader21090545-7ca7-4776-b22c-e363652d74d2Cannot read secret values or key material

Vault scope and the permission model are the narrowing controls

Assign the role at the vault scope, using a command of the form az role assignment create --role "Key Vault Secrets User" --assignee --scope . Use a managed identity for the application so that no secret is needed to reach the vault.

Microsoft's guide notes that a custom role can be defined when no predefined role fits, and that the Key Vault Contributor role is for control plane operations only: it does not allow access to keys, secrets or certificates. Officer roles (Secrets Officer, Crypto Officer, Certificates Officer) manage objects but not permissions.

Checking what is used

Defender for Cloud permissions management, according to Microsoft, assesses managed identities, service principals and groups for excessive or unused permissions. Run it against the identities that hold vault roles, then remove Secrets Officer or Administrator assignments held by identities that only read.

For people with administrative roles, Microsoft Entra access reviews let owners confirm each assignment on a schedule. List role assignments at the vault scope with az role assignment list and compare them with the table above.

Sources

  1. Azure RBAC guide for Key Vault, read 16 Nov 2026
  2. Defender for Cloud permissions management, read 16 Nov 2026
  3. Microsoft Entra access reviews, read 16 Nov 2026

Last reviewed 16 Nov 2026.