Microsoft's sovereign cloud update: AI on servers you run, and oversight of who reaches your systems

Microsoft published its update on 20 October 2026, written by Douglas Phillips, President and Chief Technology Officer of Microsoft Specialized Clouds. Microsoft introduced Microsoft Sovereign Cloud last year, and the post describes it as a range of control in three parts. Those parts are Sovereign Public Cloud, Sovereign Private Cloud and the Sovereign Partner Ecosystem. Customers choose the control for each workload and can combine the three.

Microsoft says a public-facing digital service may suit the public cloud. A system that supports essential operations may need to keep running locally if the connection fails. An AI workload that handles highly sensitive data may need its models, data and processing to stay in an environment the customer controls.

Data Guardian is being rolled out for customers in the European Union (EU) and the European Free Trade Association (EFTA). A trusted EU partner, based in Europe, oversees qualifying remote access by Microsoft engineers to in-scope production systems.

Production Touch Ledger has launched with a phased rollout in the same regions. It keeps a tamper-evident record of that access and of what was done. A tamper-evident record shows if anyone has altered it. Just-in-time Access and Customer Lockbox, which already exist, give customers more control over access to their environments.

External key management with Azure Managed HSM is now generally available, Microsoft's term for a full release. An HSM, or hardware security module, is a dedicated device that stores encryption keys.

With this option the customer keeps the root encryption key in hardware it owns and runs. That hardware can sit on the customer's own premises or with a trusted third party. Azure Key Vault Managed HSM already gave dedicated, single-tenant key protection inside Microsoft's infrastructure.

The Sovereign Control Panel enters public preview at Microsoft Ignite. It brings sovereignty settings into one view in the Azure portal. There a team can see where its sovereignty settings stand, apply and manage controls, and find gaps and risks. It also shows how workloads depend on each other and how easily they could move to another environment.

Azure Confidential Clean Rooms is in limited preview. It applies confidential computing to approved work between several organisations on shared sensitive data. Confidential computing protects data in hardware while it is being processed. Microsoft is also publishing new business continuity guidance and architecture patterns.

A risk committee at a regulated buyer can ask who at the cloud provider is able to reach its production systems. Where Data Guardian and Production Touch Ledger apply, they give the committee a control and a record to point to.

The post names EU and EFTA customers for both. It does not mention the UK. A UK buyer who wants this oversight should ask Microsoft whether and when it applies to their tenancy, and get the answer in writing.

Holding the root key is a decision for procurement and for the security architects. The key then sits in hardware the customer controls, and that hardware and the people who run it join the customer's own estate. A buyer that already runs HSMs for other systems likely has less to set up.

Sovereign Private Cloud is built on Azure Local, which the customer operates and can run with or without a link to Microsoft's cloud. Microsoft says Foundry Local will become generally available at Ignite for connected and disconnected operation on Azure Local. It comes with a larger model catalogue of Microsoft, partner, open-weight and open-source models. An open-weight model is one whose maker publishes the trained model for others to download and run.

Microsoft also says people will be able to ask questions of local company data in plain language and get answers drawn from that data. It calls this local inference and agentic retrieval, and the post gives no date for it. Microsoft 365 Local is in preview for approved customers. Microsoft says its integration brings those answers to SharePoint and Exchange servers the customer runs, and gives no date for that either.

GitHub Enterprise Local will become generally available at Ignite. It is a GitHub Enterprise Server appliance validated for Azure Local, so repositories, code and development artifacts stay under local control. Developers can also use GitHub Copilot with locally hosted models.

Confidential virtual machines on Azure Local are generally available. They encrypt memory in hardware, isolate workloads in hardware and check a workload before sensitive data or keys are released to it.

SQL Server on Azure Local is already generally available for connected and disconnected use, and DocumentDB and Blob Storage on Azure Local enter public preview. The ability to move workloads from connected to disconnected operation also enters public preview.

Microsoft says Azure Local will support multitenancy, with no date given. Several tenants would share the same hardware, each with its own resources, governance and management. Microsoft presents this as a way for local operators and service providers to offer sovereign cloud services on Azure Local.

Microsoft's private cloud gets a model catalogue and a coding assistant on local models, both due at Ignite. Answers from local SharePoint and Exchange are announced with no date. A workload whose data rules out the public cloud can then have an AI option on the customer's own servers.

Choosing a model to run locally comes with three conditions. The model has to be in the catalogue, the hardware you run has to carry the load, and the results need their own evaluation. Check which models are in Foundry Local's catalogue before committing a use case to it.

The AI items are in preview, due at Ignite or undated, and none has a price yet. Plan pilots now, and commit to production once general availability and pricing are published.

The post does not name the Gulf. For Gulf buyers, the item to look at first is disconnected operation on Azure Local. Ask who the local partner would be and how support works. Once Microsoft gives a date, multitenancy could let a local service provider run Azure Local for buyers who would rather not run the hardware.