Azure DataCenter
  • All of Microsoft
  • My Role
    • All in My Role
    • Azure DataCenter
  • Focus
    • All in Focus
    • Microsoft Ignite 2026
    • Azure Weekly Update
    • Azure Master Class
    • What's Hot
    • M365 Release
Timespan
explore our new search
Azure sovereignty: control workloads from silicon to cloud
Compute

Azure sovereignty: control workloads from silicon to cloud

Azure’s sovereignty approach combines hardware security and deployment choices for organizations with strict control requirements.

Key insights

  • The Microsoft and Intel approach combines Intel TDX, Azure confidential VMs, Azure Local and Sovereign Cloud controls.
  • Intel TDX creates hardware-isolated trust domains to help protect data while it is being processed.
  • Azure Local supports customer-operated environments, including locations where connectivity is limited.
  • Microsoft's Sovereign Cloud strategy offers public cloud, private cloud and partner-operated deployment options.

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.

What's new

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.

Who it is for and what you need

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.

How it works

  1. Assess each workload’s requirements for data location, access, operations, continuity and security.
  2. Choose an environment that fits: public Azure, customer-operated Azure Local, or a local partner-operated option.
  3. For workloads using confidential computing, use Azure confidential VMs with Intel TDX to help isolate processing in hardware-backed trust domains.
  4. Use attestation to verify evidence about the workload’s execution environment.

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.

Limitations and alternatives

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.

Sources

Frequently asked questions

What is Azure sovereignty?

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.

How does Intel TDX relate to Azure confidential computing?

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.

Can Azure sovereignty workloads run outside public Azure?

Yes. The described choices include Azure Local in customer-operated environments and partner-operated environments, as well as Sovereign Public Cloud.