Azure Security built-in role

Key Vault Secrets User

Reads Key Vault secret contents and metadata. This includes the secret portion of a Key Vault certificate and, when that certificate key is exportable, can include its private key. The role cannot create, update, delete, recover, purge, or assign permissions and works only with Azure RBAC-enabled vaults.

Role-definition permissions are imported from Microsoft Learn. Practical scope, use cases, prerequisites, best practices, security considerations, assignment guidance, and relationships have been reviewed against the official sources below.

Role definition ID: 4633458b-17de-408a-b874-0445c86b69e6

Control-plane actions (0)

None — this role grants no control-plane management actions.

Data-plane actions (2)

Excluded actions (0)

None

Assignable scopes (1)

Practical scope

Assign to the consuming workload identity at the individual vault. Parent assignments are inherited by child vaults. A secret-level assignment is supported for limited sharing scenarios, but Microsoft recommends a vault per application and environment as the normal security boundary.

Common use cases (2)

Prerequisites (3)

Best practices (3)

Security considerations (3)

Assignment guidance

Assign Key Vault Secrets User to the application managed identity at the application vault or exceptional secret scope. Use Key Vault Reader for Key Vault data-plane metadata inspection while accounting for its ancillary control-plane Actions, and use Secrets Officer for approved credential lifecycle administration.

Related roles (2)

Editorial sources (8)

Official Microsoft Learn documentation →