Course contentsShow
← Cloud and Infrastructure
Lesson 1283 of 2,98925. Kubernetes Configuration and SecretsFree lesson

Azure Key Vault Integration

Connecting to Azure Key Vault using managed identities, service principals, and configuring SecretStore resources.

Azure Key Vault Integration

What you'll learn: How to connect the External Secrets Operator to Azure Key Vault so Kubernetes can securely retrieve secrets from Azure's managed secrets service.

The Core Idea

Azure Key Vault is Microsoft's cloud service for storing secrets, keys, and certificates. Just like you've learned to pull secrets from AWS Secrets Manager and HashiCorp Vault, Azure Key Vault integration lets your Kubernetes cluster fetch secrets from Azure's ecosystem.

The connection requires authentication — you can't just ask Azure for secrets without proving who you are. Azure offers managed identities (Azure automatically handles credentials for resources) and service principals (manually created accounts with credentials) as authentication methods.

Connecting with Managed Identities

Managed identities work like a special pass Azure gives to your Kubernetes cluster. If your cluster runs in Azure (AKS), you enable managed identity for specific pods using Azure AD Pod Identity or Azure Workload Identity. The External Secrets Operator pod gets this identity, which Azure Key Vault recognizes and trusts.

Connecting with Service Principals

A service principal is like creating a service account — you generate a client ID and client secret, store those credentials as a Kubernetes Secret, then reference them in your SecretStore resource. Less automated than managed identities, but works anywhere.

Configuring the SecretStore

Your SecretStore resource points to Azure Key Vault by specifying the vault URL (like https://my-vault.vault.azure.net/), the authentication method (managed identity or service principal reference), and optionally which Azure tenant you're using. Once configured, your ExternalSecret resources can reference keys stored in that Azure vault.

Key Takeaway: Azure Key Vault integration requires authentication via managed identities (for Azure-native environments) or service principals (using stored credentials), configured through the SecretStore resource's Azure-specific provider settings.