Azure Key Vault Access Policies and RBAC
You'll learn how to control who and what can access secrets, keys, and certificates in Azure Key Vault using two distinct permission models.
Two Permission Models
Azure Key Vault offers two ways to grant access: Access Policies (the legacy model) and Azure RBAC (the modern, recommended approach). Think of it like choosing between giving someone a physical key to a specific drawer (access policy) versus assigning them a role with defined responsibilities across the entire office (RBAC).
Access Policies (Legacy)
Access policies grant permissions directly at the Key Vault level. You specify which identity (user, service principal, managed identity) gets which permissions (Get, List, Set, Delete) on which object type (secrets, keys, certificates). This model is vault-specific and doesn't integrate with broader Azure governance.
Azure RBAC (Recommended)
Azure RBAC uses built-in roles like Key Vault Secrets User or Key Vault Secrets Officer that integrate with Azure's unified permission system. This approach leverages managed identities seamlessly—your VM or App Service can authenticate without storing credentials, and you assign roles at the subscription, resource group, or vault level. RBAC supports inheritance, audit trails, and conditional access policies.
Why This Matters
When using managed identities (covered in earlier Azure fundamentals), RBAC is the natural fit. Your application's managed identity gets assigned the minimum required role (like Key Vault Secrets User to read secrets), and Azure handles authentication automatically. No credentials in code, no rotation headaches.
You can enable RBAC on new vaults or migrate existing vaults from access policies—but not both simultaneously on the same vault.
Key Takeaway: Use Azure RBAC with managed identities for modern, scalable secrets access control; access policies remain available for legacy scenarios but lack integration with Azure's broader identity and governance features.