Azure Key Vault
Centralized secrets, keys, and certificate management.
When to Use
- Storing application secrets
- Managing certificates
- Storing encryption keys
- Centralizing secret management
- Enabling secret rotation
Required Supporting Resources
| Resource | Purpose |
|---|---|
| None required | Key Vault is self-contained |
| Private Endpoint | Secure access (optional) |
SKU Selection
| SKU | Features |
|---|---|
| Standard | Software-protected keys |
| Premium | HSM-protected keys |
RBAC Roles
| Role | Permissions |
|---|---|
| Key Vault Administrator | Full access |
| Key Vault Secrets Officer | Manage secrets |
| Key Vault Secrets User | Read secrets |
| Key Vault Certificates Officer | Manage certificates |
| Key Vault Crypto Officer | Manage keys |
Environment Variables
| Variable | Value |
|---|---|
KEY_VAULT_URL | https://{vault-name}.vault.azure.net/ |
KEY_VAULT_NAME | Vault name |
Best Practices
- Always use RBAC over access policies
- Enable soft delete and purge protection for production
- Use managed identities instead of storing keys in apps
- Set expiration dates on secrets
- Use separate vaults for different environments