What changed
The Azure Updates entry is titled "Public Preview: Encryption at rest with customer-managed keys in Azure HorizonDB." It carries a November 17, 2026 timestamp. The page fetched for this story rendered only a generic updates interface with no announcement text. The details below therefore come from Microsoft's current documentation.
The HorizonDB security overview was last updated on November 17, 2026. It says that service-managed keys are the default, and it now lists customer-managed keys as a preview option. One of the search results is an older cached version of the same page. It describes only service-managed keys and does not mention CMK. Treat that older text as superseded.
The same day, Microsoft announced general availability of Azure HorizonDB in its Ignite blog. That blog lists customer-managed keys among the service's security capabilities. General availability of the service does not make CMK generally available. Microsoft's security documentation still labels CMK as preview.
What is protected
HorizonDB always encrypts managed data at rest. According to Microsoft Learn, this covers system and user databases, cluster logs, write-ahead log segments and backups. CMK does not turn encryption on, because encryption was already on. It changes who controls the key.
The two modes work as follows:
- Service-managed keys (default): Azure manages the keys and their rotation, and you configure nothing.
- Customer-managed keys (preview): You store the key in Azure Key Vault or Azure Key Vault Managed HSM. Microsoft says you are responsible for key permissions, network access, auditing and rotation.
Microsoft's general Azure guidance describes CMK the same way. Organizations can use customer-managed keys when they need extra control over encryption keys and key management policies. The cost is more management responsibility and complexity.
Planning constraints
Decide at creation time. You choose the encryption mode when you create the cluster, and Microsoft says you can't change it later. Don't assume you can convert an existing service-managed-key cluster in place. If you might need CMK, decide before you provision.
Geo-redundant backup trade-off. Microsoft Learn's HorizonDB overview lists a limitation: CMK is not available together with geo-redundant backup. A cluster can use one or the other. Check this against your recovery requirements before you choose CMK.
The key vault becomes a dependency. Microsoft's general Azure encryption guidance explains how CMK scenarios work. Disabling a key encryption key makes dependent services inaccessible. The guidance also says you stop using a customer-managed key by disabling the key or revoking access. The HorizonDB pages I reviewed do not describe HorizonDB's specific behavior if a key becomes unavailable. They also give no recovery promises, so plan and test for that case rather than assuming an outcome.
What this does not do
- Encryption at rest protects stored data, for example from someone obtaining physical media. It doesn't replace access control, TLS or application design.
- Microsoft's HorizonDB guidance still recommends application-level encryption for values that need application-controlled secrecy. It also recommends TLS for client connections, and HorizonDB supports TLS 1.2 and 1.3.
- Using CMK does not by itself make you compliant with any regulation. Whether it satisfies a requirement depends on your whole configuration and obligations.
Pre-adoption checklist
- Confirm the cluster really needs customer key control, since the default is already encrypted.
- Decide on Key Vault or Managed HSM, and define who can use and administer the key.
- Plan network access to the key store, plus auditing and rotation procedures.
- Weigh the loss of geo-redundant backup against your disaster recovery targets.
- Test in non-production first. Preview features are for non-production use and testing.
What isn't documented yet
The sources I reviewed don't include a full configuration walkthrough for HorizonDB CMK. They also don't cover regional availability of the CMK preview, pricing impact or a production-readiness commitment. Microsoft says HorizonDB is generally available in 13 Azure regions, but that figure applies to the service and not necessarily to CMK. Verify those details in the current documentation before you commit a design to CMK.
References
- (In preview) Public Preview: Encryption at rest with customer-managed keys in Azure HorizonDB Azure Updates · 2026-11-17T20:00:32Z
- Azure data encryption at rest - Azure Security learn.microsoft.com
- Secure Your Azure HorizonDB - Azure HorizonDB learn.microsoft.com