L12. Azure Key Vault
Course outlineLesson 12 of 18
Distinguish secrets, keys and certificates, apply data-plane authorization, and plan deletion recovery, certificate lifecycle and HSM-backed protection.
Course context: AZ-500 retired on August 31, 2026. Use these Azure security concepts for operational practice and continue with the current SC-500 course for certification preparation.
Secrets, Keys and Certificates
| Object | Purpose | Access pattern |
|---|---|---|
| Secret | Password, connection string or API key | Authorized application retrieves the value |
| Key | Cryptographic operations | Application requests signing, decrypting or key wrapping without retrieving private key material |
| Certificate | X.509 certificate lifecycle | Certificate object plus associated key and secret |
Data Plane vs Control Plane
The control plane manages the vault through Azure RBAC. The data plane manages secrets, keys and certificates through Azure RBAC or legacy access policies. Selecting RBAC for the data plane does not eliminate the separate control-plane permissions.
Prefer RBAC. Key Vault Secrets User reads secret values; Secrets Officer manages secrets. Key Vault Reader reads metadata, not secret values. Crypto User performs key operations; Crypto Officer manages keys. Administrator manages data-plane objects, not role assignments.
Per-object RBAC scopes are supported, but Microsoft recommends a vault per application per environment and vault-level assignments for most scenarios.
Deletion Recovery
Soft delete retains deleted vaults and objects for 7 to 90 days, with the retention interval selected at creation. Once enabled it cannot be disabled. Purge protection prevents early permanent deletion and cannot be disabled or bypassed once enabled. Services such as Azure Storage require soft delete and purge protection for customer-managed-key vaults.
Hardware Protection
Premium supports HSM-backed keys. Current Microsoft documentation identifies FIPS 140-3 Level 3 HSM protection. Do not confuse Premium vaults with the separate Managed HSM resource and its access-control model.
References
- Key Vault overview and current HSM protection
- Key Vault RBAC and role permissions
- Soft delete and purge protection
- Certificate lifecycle and exportability
- Storage CMK requirements
- AZ-500 retirement and legacy skills outline
Continue Learning
- ✓Secrets return their values; key operations protect private key material while public key material can be retrieved
- ✓Certificate exportability and issuer integration determine private-key retrieval and automatic renewal
- ✓Control-plane authorization always uses Azure RBAC; data-plane authorization selects RBAC or access policies
- ✓Key Vault Reader reads metadata, not secret values; Secrets User can read secret values
- ✓Soft delete retains objects for 7 to 90 days; enabled purge protection cannot be bypassed during retention
- ✓Premium supports HSM-backed keys; current documentation specifies FIPS 140-3 Level 3
1. What is the key difference between Key Vault 'secrets' and Key Vault 'keys'?
2. Azure Key Vault soft-delete is enabled. An administrator accidentally deletes a secret. What is the correct recovery procedure?
3. You need fine-grained per-secret access control in Key Vault. Which permission model should you use?