Azure sovereignty combines hardware-based security with deployment choices that give organizations more control over where workloads run and how they are operated. It is relevant to public-sector bodies and regulated industries, including healthcare, finance and critical infrastructure. Microsoft Azure’s short overview focuses on its collaboration with Intel to connect security from silicon through cloud infrastructure.
The collaboration brings Intel Xeon processors and Intel Trust Domain Extensions (TDX) together with Azure confidential virtual machines, Azure Local and Microsoft Sovereign Cloud controls. The aim is to support workloads across public cloud, customer-operated infrastructure, edge locations and disconnected environments.
Intel TDX creates hardware-isolated trust domains for virtual machines. Confidential computing is designed to protect data in use—while it is being processed—rather than only when stored or transmitted. Hardware-backed attestation can provide evidence that a workload is running in an approved, properly configured environment.
Microsoft’s broader approach treats sovereignty as a property of the technology stack, including hardware, infrastructure, cloud services, data and AI. That makes deployment location only one part of the decision: organizations can also consider who operates systems and who can access them.
This approach is aimed at organizations with strict sovereignty, security or regulatory requirements. Examples include government, critical infrastructure, healthcare and financial services.
The deployment choices described include Sovereign Public Cloud, Sovereign Private Cloud built on Azure Local, and environments operated by local partners. The model lets organizations select an environment for each workload rather than putting every application in the same place.
Azure Local provides Azure infrastructure and services in customer- or partner-operated environments. The approach can keep workloads closer to operations and support deployments where network connectivity is limited.
These options do not make every workload suitable for every environment. Organizations need to match deployment and controls to each workload’s requirements. The approach is a choice among public, private, partner-operated and local environments, not a requirement to move all systems into one model.
Confidential computing addresses protection while data is being processed; it sits alongside controls for data storage, transmission, access and operations. A deployment decision should account for those broader sovereignty requirements too.
It is an approach to controlling where workloads run and how data, infrastructure, access and operations are managed. The approach spans hardware, infrastructure and cloud services.
Intel TDX creates hardware-isolated trust domains. Used with Azure confidential VMs, it is designed to help protect workloads and data while they are being processed.
Yes. The described choices include Azure Local in customer-operated environments and partner-operated environments, as well as Sovereign Public Cloud.