Microsoft expands sovereign cloud with external keys and EU oversight

By Amara Osei

Microsoft expanded its sovereign cloud portfolio on Tuesday, adding external encryption key management, confidential computing, disconnected operations and an EU-specific oversight model — a package aimed squarely at customers who want to know where data sits, who can touch it and what happens when regulators or geopolitics shift.

The additions cover security, governance and AI capabilities across Azure. The underlying design principle, according to the company, is letting organizations apply different levels of control to different workloads instead of forcing one rigid model on everything.

“Organizations are considering more than where data resides. They also seek to understand who can access and operate their systems, how sensitive digital assets remain protected, which technology dependencies matter most and whether critical services can continue as regulatory, geopolitical, security or network conditions change,” said Douglas Phillips, president and CTO at Microsoft Specialized Clouds.

Put plainly: this release is Microsoft's answer to customers — European governments in particular — who no longer treat data location as sufficient.

Why is Microsoft doing this now?

Three forces are converging. Stricter data regulations, rising geopolitical tensions and accelerating AI adoption have pushed governments and enterprises to demand more control over storage, access and continuity.

“Governments and enterprises want greater control over where their data is stored, who can access it, and whether critical systems can operate during disruptions. For instance, governments and big enterprises in Europe are worried about keeping their important data on an American company's computers,” said Pareekh Jain, CEO at EIIRTrend & Pareekh Consulting. “Europe has proposed a new law that would limit the use of US cloud companies for sensitive government data in many areas. Microsoft is responding to these concerns while competing with local sovereign cloud providers.”

That competitive pressure is real. US hyperscalers — Amazon, Google and Microsoft — still control roughly 70% of the European cloud market, while European providers' share has shrunk over the past decade.

The takeaway: this is as much a defensive market move as a technical one.

What is actually shipping?

The announcement spans several products and preview stages:

• Sovereign Control Panel — a unified Azure portal experience for assessing sovereignty posture, identifying risks and gaps, applying controls and evaluating workload portability. Public preview is scheduled for Microsoft Ignite.
• External key management with Azure Managed HSM — generally available now. Organizations can hold root encryption keys in hardware they own and operate on-premises or through a trusted third party, extending control beyond Microsoft's own infrastructure.
• Azure Confidential Clean Rooms — limited preview. Confidential computing lets participants analyze shared sensitive data while limiting exposure of the underlying information.
• Azure Local expansions — transitioning workloads between connected and disconnected states enters public preview; DocumentDB and Blob Storage enter public preview on Azure Local; SQL Server on Azure Local is already generally available for connected and disconnected deployments.
• Foundry Local — scheduled for general availability at Ignite, supporting local inference and agentic retrieval in natural language on Azure Local, with an expanded model catalog from Microsoft, partners and open source.
• Confidential Virtual Machines on Azure Local — generally available now, using hardware-encrypted memory, isolation and workload attestation before sensitive keys or data are released.

In short: Microsoft is extending sovereign guarantees from storage down into compute, AI and even fully disconnected environments.

What changes for European customers?

For EU and EFTA customers, Microsoft is rolling out Data Guardian. A trusted regional partner will independently oversee remote access requests by Microsoft engineers. In parallel, a Production Touch Ledger will create tamper-evident logs of every technical action performed.

Microsoft is also widening its Sovereign Partner Ecosystem, naming regional operators Bleu Cloud in France and Delos Cloud in Germany, plus independent software vendors specializing in security, identity, observability and backup.

The effect is that European customers gain an auditable chain around who touched what, and when.

Does sovereignty now mean full independence?

Not according to the analysts. Ashish Banerjee, senior principal analyst at Gartner, draws a sharp line between different deployment models.

“Depending upon the deployment model, in the public cloud, enterprises get better visibility, stronger access controls, and more control over encryption keys. In the Sovereign Private Cloud, they can operate infrastructure locally and even disconnect selected workloads from Azure. But I would not call this complete control. Enterprises still need to check whether Microsoft remains involved in identity, software updates, management, or technical support for the services they use,” Banerjee said.

Jain points to the legal ceiling. “Local infrastructure, independent encryption keys, and disconnected operations make it harder for external parties to access data or disrupt services. However, Microsoft remains subject to applicable US laws, sanctions, and export restrictions. Enterprises gain greater operational independence but not complete legal or technological independence.”

What should CIOs do with this?

Sovereignty carries a price tag. Local or disconnected environments may not receive every Azure service at the same time, and organizations may need dedicated infrastructure, specialist skills and separate continuity arrangements — while giving up some elasticity and economies of scale.

Banerjee advises a workload-by-workload assessment rather than a blanket label. “I would not recommend maximum sovereignty for every workload. Reserve it for workloads where the legal, operational or geopolitical risk genuinely justifies the additional complexity.”

The calculus for buyers: match the level of sovereignty to the actual risk, because full independence is not on the menu.