Announcedazure-infrastructureZero TrustSovereignty & regulationDay 2

Shrinking the trusted computing base for sensitive cloud workloads

Azure confidential computing previewed three capabilities planned for a future release, all built on next-generation Confidential Child Capable VMs. The child VMs are hardware-isolated with AMD SEV-SNP inside a customer-run parent VM. Confidential enclaves split a secret-handling component out of an Azure Linux VM without enclave SDKs. Confidential containers on AKS isolate an individual pod rather than the whole node.

Recap by Jussi Roine · Updated 18 Nov 2026
status
Announced
why it matters

The idea is to stop trusting the whole VM or node: only the signer, key broker or policy check sees the secret, and it gets the key only after attestation proves which code is running. Nothing here ships yet and details may change. You can still prepare now: separate secret-bearing code behind a narrow interface, decide who owns the key-release policy, and treat the channel to the parent as untrusted.

Zero TrustSovereignty & regulation

Official sources

Community deep dives

0 links · newest first
Written or recorded something about this?It goes to the moderators with this recap attached. No account needed, and you can get the credit.
Add a link to this recap