Azure Key Vault Fundamentals
What you'll learn: How Azure Key Vault provides centralized, secure storage for secrets, cryptographic keys, and TLS/SSL certificates in Azure.
What is Azure Key Vault?
Azure Key Vault is Microsoft Azure's managed service for safeguarding cryptographic secrets, keys, and certificates. Think of it as a secure, centralized vault where your applications can retrieve credentials, API keys, connection strings, and encryption keys without hardcoding them into your code.
Unlike AWS Secrets Manager which focuses primarily on secrets, Key Vault offers three distinct object types in one service:
- Secrets: Strings like passwords, connection strings, and API tokens
- Keys: Cryptographic keys for encryption/decryption operations
- Certificates: TLS/SSL certificates with automated renewal support
Core Components
A vault is your isolated container with its own access policies and audit logs. Each vault has a unique DNS name (e.g., https://myvault.vault.azure.net/) and exists within a specific Azure region.
Access policies control who (users, service principals, managed identities) can perform which operations (get, list, set, delete) on which object types. This granular control means you can let an application read a database password without letting it change or delete it.
Basic Vault Operations
Common operations include:
- Create a vault in your subscription
- Set a secret, key, or certificate
- Get the current value when your application needs it
- List available objects (respecting permissions)
- Version secrets automatically with each update
Key Vault integrates natively with Azure Active Directory for authentication and supports both standard and premium tiers (premium adds hardware security module backing for keys).
Key Takeaway: Azure Key Vault centralizes secrets, keys, and certificates in a managed service with fine-grained access control, automatic versioning, and audit logging—removing the need to store sensitive data in application code or configuration files.