Azure Key Vault Key Management
You'll learn how to create, rotate, and version cryptographic keys in Azure Key Vault using both software and HSM protection.
Software-Protected vs. HSM-Protected Keys
Azure Key Vault offers two protection levels for cryptographic keys:
Software-protected keys are encrypted and processed using Azure's software-based cryptographic operations. They're cost-effective and sufficient for most workloads. Think of these as keys stored in a highly secure software vault — protected, but processed in memory.
HSM-protected keys (Premium tier) are generated, stored, and processed entirely within FIPS 140-2 Level 2 validated Hardware Security Modules. The private key material never leaves the HSM boundary. This is like having a physical safe where the lock mechanism itself performs all operations — the key never exits the vault.
Key Rotation
Key rotation in Azure Key Vault follows a versioned approach. When you rotate a key:
- A new version of the key is created with the same name
- The previous version remains accessible (unless explicitly disabled)
- Applications can reference the key by name (always getting the latest) or by specific version
You can rotate keys manually or configure automatic rotation policies (Preview feature). Each rotation maintains the key hierarchy — your Key Encryption Keys (KEKs) get new versions while encrypted Data Encryption Keys (DEKs) remain valid.
Key Versioning
Every key operation in Azure creates or references a version identifier. This enables:
- Graceful rollover: New encryptions use the latest version while old data remains decryptable with previous versions
- Audit trails: Track which version was used for specific operations
- Rollback capability: Revert to previous versions if needed
Version identifiers are immutable GUIDs appended to the key URI.
Key Takeaway: Azure Key Vault manages keys through software or HSM protection levels, with built-in versioning that enables safe rotation without breaking existing encrypted data.