Study guide

12.2 Key Vault Backup, Recovery & Automated Key Rotation

Microsoft Azure Security Technologies AZ-500

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Azure Security Architecture Foundation

1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles

2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM

2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)

3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity

3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration

4 Chapter 4: Microsoft Entra Application Access & Consent Governance

4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials

5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection

5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door

6 Chapter 6: Secure Azure Networking - Private Access & Monitoring

6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring

7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity

7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance

8 Chapter 8: Public and Edge Access Protection

8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management

9 Chapter 9: Compute, Container & Registry Security

9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control

10 Chapter 10: Storage Security, Access Methods & Data Protection

10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup

11 Chapter 11: Data Platform & Database Security

11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration

12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection

12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc

13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection

13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud

14 Chapter 14: External Attack Surface & Vulnerability Management

14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab

15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation

15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation

12.2 Key Vault Backup, Recovery & Automated Key Rotation

Key Takeaways Explain This Topic AI

A Key Vault object backup can only be restored into a vault in the same Azure subscription and the same Azure geography.

Backing up a key, secret, or certificate captures every version of that object as a single encrypted, opaque blob.

Soft delete is mandatory on Key Vault with a retention window of 7 to 90 days; purge protection makes purging impossible until that window elapses and cannot be turned off.

Key rotation policies rotate keys automatically based on time after creation or time before expiry, and emit Event Grid notifications.

Managed HSM protects its own restore path with a security domain that requires a quorum of key holders.

Last updated: August 2026

Why Key Recoverability Is a Security Control

If a customer-managed key protecting a storage account, a disk encryption set, or a SQL database with transparent data encryption is deleted, the data becomes permanently unreadable. Deleting a key is therefore a destructive action equivalent to destroying the data , which is why Azure makes deletion recoverable by design and why the AZ-500 objective explicitly names "perform backup and recovery of certificates, secrets, and keys".

Object Backup and the Geography Restriction

Azure Key Vault (standard and premium) provides per-object backup : az keyvault key backup --vault-name kv-prod --name cmk-storage --file cmk-storage.backup

  • az keyvault secret backup --vault-name kv-prod --name sql-conn --file sql-conn.backup
  • az keyvault certificate backup --vault-name kv-prod --name tls-cert --file tls-cert.backup

Properties that get tested:

The backup blob is encrypted and opaque . You cannot read it, parse it, or extract the key material — it is only meaningful to the Key Vault service.

A backup captures all versions of the object, not just the current one.

Restore is limited to a vault in the same Azure subscription and the same Azure geography (for example, a backup from a vault in North Europe can be restored into West Europe, but not into a US or Asian geography). This is a deliberate data-residency and security boundary, and it means a Key Vault backup is not a cross-region disaster recovery mechanism on its own.

There is no supported "back up the whole vault in one call" for standard Key Vault — you enumerate objects and back each one up. Managed HSM , by contrast, supports full backup and restore of the entire HSM.

Performing a backup requires the backup data-plane permission (access policy model) or a role that includes it, such as Key Vault Contributor combined with the relevant data role, in the RBAC model.

Because of the geography limit, treat object backup as protection against accidental deletion and vault corruption, and treat multi-region key management (separate vaults per region, with keys created independently and referenced by regional resources) as the real availability design.

Soft Delete and Purge Protection

Feature Status Behaviour

Soft delete Always on; cannot be disabled Deleted vaults and objects are retained for the configured retention period of 7–90 days (90 is the default) and can be recovered

Purge protection Optional, irreversible once enabled Blocks permanent purge of a deleted vault or object until the retention period expires — even for a Global Administrator

  • Recovery commands: az keyvault recover --name kv-prod # recover a deleted vault
  • az keyvault key recover --vault-name kv-prod --name cmk-storage

Purge protection is a prerequisite for several services that rely on customer-managed keys, including Azure Storage CMK configurations and disk encryption sets, precisely because those services cannot tolerate an unrecoverable key deletion. Recovering a deleted object requires the recover permission; purging requires purge , which should be granted to almost nobody.

Note the interaction with role separation: the ability to purge is the ability to destroy data irrecoverably, so it belongs in a PIM-eligible role, not in a standing assignment.

Automated Key Rotation

Keys support a rotation policy so the vault generates a new key version on schedule with no orchestration code:

  • Policy element Meaning
  • Expiry time The lifetime assigned to each newly created key version
  • Rotate: time after create Rotate N days after the current version was created
  • Rotate: time before expiry Rotate N days before the current version expires
  • Notify: time before expiry Emit an Event Grid KeyNearExpiry event N days before expiry

Configuring the policy requires Key Vault Crypto Officer (or the rotate and setrotationpolicy permissions). Azure services that reference a key without pinning a version — such as storage account CMK configured for automatic key version rotation, or a disk encryption set with auto-rotation — pick up the new version automatically. Services pinned to a specific key version keep using the old one, which is the usual reason "rotation happened but nothing changed".

Secrets do not rotate themselves. The pattern is Event Grid SecretNearExpiry → Azure Function or Automation runbook that changes the credential at the source system and writes the new value as a new secret version.

Certificates managed by Key Vault with an integrated certificate authority (DigiCert or GlobalSign) auto-renew via a lifetime action configured either as a percentage of lifetime elapsed or a number of days before expiry. Non-integrated certificates emit the same notification events for a manual or automated process to act on.

Managed HSM Considerations

Managed HSM raises both the assurance level and the recovery complexity:

FIPS 140-2 Level 3 validated , single-tenant HSM pools.

Security domain : during activation you upload 3–10 RSA public keys and set a quorum . The security domain blob returned is encrypted to those keys, and without a quorum of the corresponding private keys the HSM cannot be recovered or restored — Microsoft cannot recover it for you. Losing the security domain means losing every key in the pool.

Supports full backup and restore of the entire HSM, plus selective key restore.

Uses a local RBAC model (Managed HSM Administrator, Crypto Officer, Crypto User) that is separate from Azure RBAC, so subscription Owner does not imply HSM data access — a deliberate separation of duties that appears in exam scenarios about limiting cloud administrators.