oct-HSM.One caveat on sourcing: the Azure Updates page didn't show the item's body text when we looked at it. The technical details below come from Microsoft Learn documentation updated on the day of the announcement. Some other Microsoft pages still carry the old preview wording. Treat those as lagging documentation, not as a contradiction of the GA announcement.
What actually changed
Before this, Key Vault vaults offered RSA and EC keys. Premium also offered HSM-protected versions of those. Symmetric HSM keys were a Managed HSM feature, and in vaults they were only in preview.
Azure Key Vault Premium supports HSM-protected symmetric keys through the oct-HSM key type. Symmetric keys in vaults are HSM-backed only and require a Premium vault. That means no software-protected AES keys and no Standard-tier support.
This GA is for Key Vault vaults on Premium. Managed HSM is a separate product with its own endpoint, and Microsoft's key reference already listed oct-HSM there. The two use different data-plane URLs: <vault-name>.vault.azure.net for vaults and <hsm-name>.managedhsm.azure.net for Managed HSM.
What you can do with the keys
Per Microsoft's key reference:
- Key sizes: 128, 192 and 256 bits.
- Operations: encrypt, decrypt, wrapKey and unwrapKey.
- Encryption and wrapping algorithms: AES-KW, AES-GCM and AES-CBC.
- HMAC sign/verify: HS256, HS384 and HS512.
The sign and verify algorithm has to match the key type and size. If it doesn't, the service returns a key-size-incorrect error.
Wrapping is probably the most useful of these for many teams. A key held in the service can protect another key, typically a symmetric content encryption key. Microsoft's example for symmetric keys is AES-KW.
The limit that shapes your design
Key Vault is not a bulk encryption engine. Microsoft documents that input to an encrypt, decrypt, wrapKey or unwrapKey operation on a Premium oct-HSM key can't exceed 4,096 bytes before Base64 encoding. Algorithm-specific rules, such as padding, can lower that limit.
Microsoft also says that encrypt, wrap and verify operations perform better when run locally. So the usual pattern applies:
- Generate a data encryption key in your application.
- Encrypt the data locally with that key.
- Wrap the data key with the Key Vault key.
- Store the wrapped key next to the ciphertext.
Creating and using a key
Microsoft's documentation gives an Azure CLI example for creating a key:
az keyvault key create \
--vault-name <vault-name> \
--name sample-aes-key \
--kty oct-HSM \
--size 256 \
--ops encrypt decrypt wrapKey unwrapKey
The encrypt example uses az keyvault key encrypt with algorithm A256GCM and a Base64-encoded value.
With AES-GCM, save the iv, result and tag values from the encryption response. All three are needed to decrypt. Microsoft suggests the CLI --query option to capture them in one call. If you lose the tag or IV, the ciphertext can't be recovered.
Security behavior worth knowing
- No plaintext export. When you create a key, the service generates it and stores it without releasing it to the client. A
getdoesn't return symmetric key material. There is no export operation. - Protected backup and restore. Backups are in a protected form and can't be used outside the service.
- Per-key restrictions. The
key_opsproperty can limit which cryptographic operations a key allows. - Access control. Azure RBAC is the default and recommended model, and the legacy access-policy model still exists. The predefined key roles are Key Vault Crypto Officer, Key Vault Crypto User and Key Vault Service Encryption User. Scope each application identity to the operations it needs.
- Date controls. Keys outside their
nbfandexpwindow still allow decrypt, release, unwrap and verify. That lets you recover older data after a key expires.
The "quantum-resistant" claim
Microsoft states that 256-bit AES keys used with the AES algorithms in Key Vault Premium and Managed HSM are quantum-resistant. It cites the CNSA 2.0 FAQ. The claim covers 256-bit symmetric keys only.
It doesn't mean Key Vault has post-quantum asymmetric key types. One third-party analysis from this year notes that vaults have no ML-KEM or ML-DSA key types. That is an outside assessment, not a Microsoft statement. Your RSA and EC keys are unaffected by the symmetric announcement.
Before you adopt it
- Check your service integration. Microsoft's documentation does not say every Azure service's customer-managed-key feature accepts
oct-HSMkeys in vaults. Check the service you plan to use before building around it. - Check your tier. A Standard vault can't hold these keys. Premium is billed per transaction, so estimate operation volume. We have no pricing figures in our evidence, so check the pricing page for current numbers.
- Choose Managed HSM if you need single tenancy. Microsoft says Premium uses shared HSMs operated by Microsoft. It points customers who need key sovereignty, single tenancy or higher operations per second to Managed HSM.
- Update your tooling. You need a CLI and SDKs recent enough to know
oct-HSM. We haven't verified minimum versions.
Bottom line
Production teams on Key Vault Premium can now keep AES keys in HSM-backed storage, without moving to Managed HSM. They can use those keys for key wrapping, small-payload encryption and HMAC. The 4,096-byte ceiling, the AES-GCM bookkeeping and the service-integration question are the details to check first. Wrapping a locally generated data key is the usual way to work within those limits.
References
- (Launched) Generally Available: Symmetric keys on Azure Key Vault Premium Azure Updates · 2026-11-17T20:00:32Z
- Key types, algorithms, and operations - Azure Key Vault | Microsoft Learn learn.microsoft.com
- About keys - Azure Key Vault learn.microsoft.com