Azure Container Registry's Managed HSM integration expands existing customer-managed key support with a dedicated, single-tenant key-store option managed by Azure.
A dedicated HSM environment for your container registry's encryption key
What if your container registry's encryption key could live in an HSM environment reserved for your organization, while Azure handles the infrastructure?
Azure Key Vault Managed HSM provides a dedicated, single-tenant environment for storing and using cryptographic keys in hardware security modules (HSMs). Azure operates and maintains the HSM infrastructure.
Azure Container Registry (ACR) already supports customer-managed keys (CMK), giving you control over the key used for an additional layer of registry encryption, including its access and rotation. Managed HSM support extends your choice of where that key is stored.
Choose a dedicated environment for your key
Each Managed HSM instance is dedicated to one customer. A customer-specific security domain cryptographically isolates its HSM cluster from other customers' clusters.
Azure Key Vault Premium already supports HSM-backed keys in a multitenant service. The choice is not simply software versus hardware protection: Managed HSM adds a dedicated, single-tenant environment for customers who want that isolation.
You don't have to be an existing Managed HSM customer to benefit. If you're considering a dedicated HSM service, ACR can be part of that choice.
Bring your registry into the key-management service you already use
Already using Managed HSM for other workloads? Your container registry's customer-managed encryption key can live in that service too. You don't need to choose a different key store just for ACR.
That lets your security team bring the registry's key into its existing Managed HSM administration and key-lifecycle practices. You can extend the use of a service your team already knows, rather than introduce another key-management environment for your container artifacts.
Keep your applications focused on shipping software
Choosing a different home for your encryption key shouldn't mean teaching every application how to handle it.
With ACR's Managed HSM integration, application teams continue publishing and pulling images through their normal registry workflows. They don't need to receive the HSM key or add encryption-key handling to their applications. Your security team can manage the key environment while application teams stay focused on building and delivering software.
ACR uses a managed identity to access the key, with permissions that can be scoped to that key for wrapping and unwrapping encryption keys. This is part of ACR's existing CMK model, not a new image format or application-level encryption workflow.
More choice, not a requirement to change
ACR continues to encrypt stored images and artifacts by default. Customer-managed keys provide an additional customer-controlled encryption layer, and Azure Key Vault remains a supported key store.
If your current key-store choice meets your needs, there's no requirement to change it.
Get started
Ready to use Managed HSM with Azure Container Registry?
- Already using customer-managed keys? You can switch your existing registry to a key stored in Managed HSM.
- Setting up a new registry? Configure a customer-managed key when you create a new Premium registry.
See Enable a customer-managed key for Azure Container Registry for prerequisites, key permissions, and configuration steps. Before deploying, review Managed HSM retention and billing, key rotation and revocation, and troubleshooting guidance.