Course contentsShow
← Cloud and Infrastructure
Lesson 2315 of 2,98949. KMS and EncryptionFree lesson

Azure Key Vault Access Policies and RBAC

Configuring vault access policies, Azure RBAC integration, and managed identities for Key Vault.

Azure Key Vault Access Policies and RBAC

You'll learn how Azure Key Vault controls who can access secrets, keys, and certificates using two distinct authorization models.

Two Authorization Models

Azure Key Vault offers two ways to grant access: the classic Access Policies model and the modern Azure RBAC (Role-Based Access Control) model. You choose one per vault—they don't mix.

Access Policies (Classic Model)

Access policies attach directly to the Key Vault resource. You specify:

  • Who: User, service principal, or managed identity
  • What permissions: Granular operations like Get, List, Set, Delete for secrets; Encrypt, Decrypt, Sign for keys

Think of access policies like handing out specific keys to specific rooms—you give Alice the key to read secrets, Bob the key to create them, and Charlie access to cryptographic operations.

# Example permissions in an access policy
- Get secrets
- List secrets
- Set secrets (create/update)

Azure RBAC Integration

The RBAC model uses Azure's unified role system. Instead of vault-specific policies, you assign built-in or custom roles at the vault, resource group, or subscription level. Common roles:

  • Key Vault Secrets User: Read secrets only
  • Key Vault Secrets Officer: Full secret management
  • Key Vault Crypto User: Perform cryptographic operations

RBAC follows Azure's inheritance model—permissions flow down from parent scopes, making multi-vault management cleaner.

Managed Identities for Key Vault

Both models support managed identities—Azure-managed service principals for your VMs, App Services, or Functions. Instead of storing credentials, your application authenticates automatically using its identity, then Key Vault checks permissions via your chosen model (access policy or RBAC).

Key Takeaway: Azure Key Vault supports access policies for fine-grained, vault-specific permissions or Azure RBAC for centralized, role-based authorization; managed identities eliminate credential storage by using Azure's identity system for authentication.