Skip to main content
Lexicon
Lexicon
Azure Key Vault

Azure Key Vault

Difficulty: Intermediate
6 min read
Updated 2026-08-13

In plain English

Plain definition

Azure Key Vault is a cloud-hosted service, part of Microsoft Azure, used to store and control access to secrets, encryption keys and digital certificates. Instead of embedding a database password, an API key or a certificate directly inside application code or configuration files, a team places that material inside a vault and lets authorised applications and people retrieve it on demand, under a permission model that can be reviewed and changed independently of the application itself.

What a vault holds and who can read it

Key Vault holds three kinds of protected material: secrets (arbitrary key-value data such as connection strings), cryptographic keys (used for signing and encryption, optionally backed by hardware security modules) and X.509 certificates. Access is governed either by Azure role-based access control (RBAC) or by a vault-level access policy model, and callers typically authenticate using a Microsoft Entra ID (Azure Active Directory) identity, including a managed identity assigned to an Azure compute resource. Exact deletion-recovery behaviour, permission-model interaction and API version details vary by configuration, so check them against current Microsoft documentation before relying on them in production.

Why teams keep secrets in a vault

Teams use Key Vault to centralise the lifecycle of sensitive material: rotation, revocation and audit happen in one place rather than being scattered across applications. This limits the damage a single leaked credential can do and removes the need for long-lived secrets inside deployment pipelines when combined with managed identities. A Key Vault integration is working when an application retrieves the correct secret value only through an authenticated identity call, no static credential appears in its configuration, and every retrieval is visible afterwards in the vault’s diagnostic logs.

The Azure services around a vault

Key Vault does not work alone. It relies on Microsoft Entra ID for authentication, on Azure Monitor and diagnostic logging for auditability, and is typically referenced by compute resources such as App Service, Azure Functions, virtual machines and AKS workloads through managed identity or workload identity federation. Network exposure can be constrained with private endpoints and firewall rules so that retrieval traffic does not need to cross the public internet. Vaults, and the access assignments attached to them, are usually deployed and versioned through Azure Resource Manager or infrastructure-as-code alongside the resources that consume them, so that access changes are traceable rather than made ad hoc.

Reading a secret with a managed identity

Here an application retrieves a secret at start-up using its assigned managed identity, rather than reading a value from an environment variable that someone had to place there manually:

using var client = new SecretClient(vaultUri, new DefaultAzureCredential());
KeyVaultSecret secret = await client.GetSecretAsync("example-secret-name");
// DefaultAzureCredential resolves the caller's managed identity at runtime;
// no static credential is stored in application configuration.

The snippet shows the shape of the call only. It is not a command to run against a live environment.

Key Vault is not a password manager

People sometimes treat Azure Key Vault as a general-purpose end-user password manager rather than an application- and infrastructure-facing service governed by identity and policy. Another mistake is to assume that removing a secret, key or vault is always immediately and irreversibly destructive; some deletion behaviour in Azure is recoverable for a period, but the exact retention, soft-delete and purge-protection behaviour that applies to a given vault should be confirmed against current Microsoft documentation rather than assumed, since it affects how a mistaken deletion can be recovered.

Terms used with Key Vault

  • Managed Identity
  • Microsoft Entra ID (Azure Active Directory)
  • Role-Based Access Control (RBAC)
  • Hardware Security Module (HSM)
  • Azure Resource Manager

Further Reading

When this entry was written, the only verified source available was the RFC Editor’s RFC Series, which establishes general Internet standards context but does not document Azure Key Vault specifically. Product-specific behaviour, current API versions, pricing tiers and regional availability were deliberately left general or flagged for review rather than asserted, and should be checked against Microsoft’s current official Azure Key Vault documentation before this entry is treated as fully verified for publication.

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.