Azure Security built-in role

Key Vault Certificate User

Reads a Key Vault certificate and its complete certificate content, including the addressable secret and key portions exposed by the role. For an exportable certificate, the secret can contain the private key in PFX or PEM form; a non-exportable certificate does not return its private key. The role works only with the Azure RBAC permission model.

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: db79e9a7-68ee-4b58-9aeb-b90e7c24fcba

Control-plane actions (0)

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

Data-plane actions (4)

Excluded actions (0)

None

Assignable scopes (1)

Practical scope

Assign at the individual vault for an application that consumes certificates from that vault. Parent-scope assignments are inherited by child vaults. A certificate-level assignment is possible for a documented exception, but Microsoft recommends vault-per-application boundaries rather than routine object-level isolation.

Common use cases (2)

Prerequisites (3)

Best practices (3)

Security considerations (3)

Assignment guidance

Assign Key Vault Certificate User to the consuming workload identity at the vault scope only after confirming that complete certificate content is required. Use Key Vault Reader for Key Vault data-plane metadata inspection while accounting for its ancillary control-plane Actions, and use Key Vault Certificates Officer for lifecycle administration.

Related roles (2)

Editorial sources (7)

Official Microsoft Learn documentation →