Customer-managed keys (CMK) are encryption keys that a customer creates and controls, typically in Azure Key Vault or Managed HSM, to protect the keys that encrypt their data in a cloud service, instead of relying on provider-managed keys.
Title graphic: Customer-managed keys (CMK) (Concept)
Customer-managed keys (CMK) are encryption keys that a customer creates and controls, typically in Azure Key Vault or Azure Key Vault Managed HSM, to protect the keys that encrypt their data in a cloud service. They are used instead of relying on provider-managed (platform-managed) keys, and they give the customer more control over how data is protected at rest.
Microsoft Learn documentation for Azure Storage shows how this works in practice. The customer's own key does not encrypt the data directly. It protects the account encryption key, which in turn encrypts the data in a storage account. The customer key must be held in Azure Key Vault or Azure Key Vault Managed HSM, which can be in a different tenant, region or subscription than the storage account. A managed identity is granted permission on the key. Azure Storage authenticates with Microsoft Entra ID, wraps the account encryption key with the customer key, and unwraps it when data is read or written.
The documentation also names several requirements and operational duties. The key vault needs soft delete and purge protection enabled. The key must be an RSA or RSA-HSM key of an allowed size. For Azure Storage, Blob Storage and Azure Files are always protected, whereas protection for queues and tables is optional and is chosen when the account is created. Rotation is the customer's responsibility, handled through a Key Vault policy; when no key version is pinned, Storage checks daily for new versions. Disabling the key causes covered operations to fail with a forbidden error for all users, which makes access to the key a control point over access to the data. Key Vault and Managed HSM also carry their own costs, which belong in any decision about adopting CMK.
Typical decisions around CMK involve weighing the extra control against the extra responsibility. Using CMK means the organization must manage key lifecycle, rotation, permissions and availability of the vault, since a disabled or unavailable key affects the data it protects. Organizations usually consider it when compliance, regulatory or sovereignty requirements call for more direct control over encryption than platform-managed keys provide.
The M365.FM episode "Azure Bicep Fundamentals for Production Projects" lists CMK among security practices for production deployments. Its recommendations include using Private Endpoints for services such as Storage Accounts and SQL Databases instead of public IPs, enabling diagnostic logging through Azure Monitor, enforcing compliance with Azure Policy, and enabling encryption at rest with Customer-Managed Keys for greater control rather than relying on platform-managed keys.
The episode "Microsoft 365 Data Sovereignty Beyond Technical Custody" places CMK in a data sovereignty checklist. Under data protection and controls, it recommends ensuring encryption at rest and in transit and evaluating customer-managed keys and HSM options within the required region. The same list covers DLP policies tailored to classification and residency, retention and records management rules, and sensitivity labels with Microsoft Purview and Azure Information Protection. In this context CMK is one control among several that support sovereignty requirements, alongside legal and contractual mapping of applicable laws and regulations.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
Type
Concept
Episodes about Customer-managed keys (CMK)
Episodes in which Customer-managed keys (CMK) is discussed:
Microsoft Fabric pipelines often feel “secure by default,” but silent data exposure usually comes from misconfigured permissions, hardcoded secrets, and overbroad workspace roles. This episode shows how to harden end-to-end pipelines with managed identities…
Articles about Customer-managed keys (CMK) (1)
Articles in which Customer-managed keys (CMK) is a topic:
When to Graduate from Power Automate to Azure Logic Apps · Mirko Peters Welcome back, podcasters and automation enthusiasts! Have you ever hit a wall while building an office automation workflow, wondering why your flow is suddenly fail…
Questions marked with AI were written with AI from the facts on this page.
What are customer-managed keys (CMK)? (AI)
CMK are encryption keys that a customer creates and controls, typically in Azure Key Vault or Managed HSM, to protect the keys that encrypt their data in a cloud service, instead of relying on provider-managed keys.
What must be in place to use CMK with Azure Storage? (AI)
According to Microsoft Learn, the key must be in Azure Key Vault or Managed HSM with soft delete and purge protection, and it must be an RSA or RSA-HSM key of an allowed size. A managed identity needs permission on the key.
What happens if a customer-managed key is disabled? (AI)
For Azure Storage, covered operations fail with a forbidden error for all users when the key is disabled.
What other safeguards protect sensitive data in Fabric?
Encrypt data at rest and in transit using Microsoft-managed or customer-managed keys, set up monitoring and auditing to spot unusual activity, and apply data masking, including dynamic masking for live data. · From the episode: Secure Microsoft Fabric Data Pipelines
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.