Microsoft's sovereign cloud: more control, no word on exit or jurisdiction.

What Microsoft announced, and what it had announced before

On 20 October 2026 Douglas Phillips, President and Chief Technology Officer of Microsoft Specialized Clouds, published Advancing digital sovereignty with greater control and choice on the Official Microsoft Blog. He calls it "the next stage" of Microsoft Sovereign Cloud, which the post dates only as "Last year". The introduction post, by Judson Althoff, is dated 16 June 2025. The offer is now framed as a "continuum of control" in three parts: Sovereign Public Cloud on Azure, Sovereign Private Cloud on Azure Local in environments the customer operates, and a Sovereign Partner Ecosystem.

New on 20 October, and mostly not yet in effect.

• A Sovereign Control Panel in the Azure portal, meant to show a customer's "sovereignty posture", gaps and risks. It enters public preview at Microsoft Ignite. The post does not give the Ignite date.
• Data Guardian, "rolling out" for customers in the EU and EFTA. It adds "European-resident oversight by a trusted EU partner" for qualifying remote access by Microsoft engineers to in-scope production systems. Production Touch Ledger, which keeps tamper-evident records of that access, is in phased rollout in the EU and EFTA.
• External key management with Azure Managed HSM is "now generally available". The root encryption key can sit in hardware the customer owns, on-premises or with a trusted third party.
• On Azure Local: moving workloads from connected to disconnected operation enters public preview, as do DocumentDB and Blob Storage. GitHub Enterprise Local and Foundry Local become generally available at Ignite. Confidential virtual machines are generally available. Foundry Local's integration with Microsoft 365 Local is in preview for approved customers. Azure Local "will support multitenancy", with no date given.
• Azure Confidential Clean Rooms in limited preview, and new sovereign business continuity guidance.

Already there before 20 October. The June 2025 post announced Data Guardian, external key management, Microsoft 365 Local and the Sovereign Private Cloud. It also named the National Partner Clouds: Bleu in France, a joint venture of Orange and Capgemini, and Delos Cloud in Germany, an SAP subsidiary. It described the EU Data Boundary as already in place; the October post does not mention the EU Data Boundary at all. On 24 February 2026 Microsoft wrote that Azure Local disconnected operations and Microsoft 365 Local disconnected were "now available worldwide", and that large models on Foundry Local were available to qualified customers. SQL Server on Azure Local is, in the October post's own words, "already generally available".

So the announcement date and the effective dates differ. Of the new items, external key management and confidential virtual machines on Azure Local are generally available. Data Guardian and the Touch Ledger are rolling out, without an end date. The rest are previews, or promises tied to Ignite or to no date.

What the post leaves out

The 20 October post never mentions the CLOUD Act, government orders, or who can compel Microsoft to hand over data or to act. The words jurisdiction and law do not appear in it. "Legal" appears once, as one of the requirements an organisation's own strategy may have, which the controls "can support". We searched the full text for each of these terms before writing this.

The June 2025 post went further. It said Sovereign Public Cloud ensures that customer data stays in Europe "under European Law". The October post does not repeat that sentence. The description of Data Guardian has also changed. In June 2025 it would ensure that "only Microsoft personnel residing in Europe control remote access". In October it adds oversight "by a trusted EU partner" for "qualifying" access to "in-scope" systems. That comparison is ours, made from the two texts. Microsoft does not explain the change in the post, and it may be a refinement rather than a step back.

Exit is missing too. The post comes near it only once, with the Control Panel helping customers "assess portability across operating environments when required". Assessing portability comes before an exit. It is not an exit, and it is not a test of one.

On 19 October, the day before, The Register's Dan Robinson reported a study by the European Centre for International Political Economy (ECIPE) of 8,725 cloud-related procurement contracts in nine EU member states. One of its recommendations, as The Register puts it, is to define sovereignty "as a demonstrated outcome, not an ownership status". ECIPE's director Fredrik Erixon is quoted to the effect that a public buyer should be able to show its data is secure and that it can switch provider. The same article describes the CLOUD Act as the US law under which Washington can compel American tech companies to hand over data they hold, including data stored overseas. That is The Register's description; we did not read the statute for this piece.

Control is not exit, and neither is jurisdiction

On 1 October we wrote that AWS's sovereign-cloud test covers the operations layer and cannot reach jurisdiction (AWS will disconnect its sovereign cloud for a few hours. Sovereignty has layers.). Microsoft's post works on the same layer, with more tools: who may touch the system, who holds the keys, whether it keeps running when the connection is cut, and a panel that shows all of it. These are real controls, and a buyer should use them.

In September we argued that private AI means bringing the model to the data (Private AI: bring the model to the data). Foundry Local on Azure Local, with open-weight models in its catalogue, is Microsoft doing exactly that. It confirms the direction more than it threatens it.

Two questions survive any list of controls.

Who can compel the operator. Microsoft is a United States company. For Sovereign Public Cloud the answer depends on law, and a portal cannot change it. In a disconnected Azure Local installation the reach is narrower, because nobody can touch what is not connected. Microsoft still holds the licences and the updates, and in its February post on large models in Foundry Local it says it will provide "comprehensive support for deployments, updates and operational health".

Whether the customer can leave. With its data, its models and a working system, and whether anyone has tried. A panel that assesses portability "when required" is a view. An exit is a rehearsal.

Our own answer is smaller, in both senses. ATAILA Enterprise runs single-tenant on the customer's hardware; ATAILA Cloud is managed and multi-tenant on our hardware in the EU. The models are open-weight, so the weights a customer runs do not depend on a licence we can withdraw. ATAILA is a Hungarian company, and Hungarian and EU law apply to us, including orders from Hungarian authorities. Sovereignty does not mean that nobody can compel the operator. It means the customer knows who can, and under which law. The silicon in our systems is NVIDIA's and not ours, as we said on 1 October.

Where our argument is weak

On features Microsoft is ahead, and not narrowly. Microsoft 365 Local, GitHub Enterprise Local, Foundry Local, disconnected operation, confidential computing on customer hardware, external HSM keys and a large partner network are things we do not offer, or offer only in part. A buyer whose organisation already runs on Microsoft gets most of this from one vendor and one contract.

Jurisdiction has an answer inside Microsoft's own offer, at least in two countries. Bleu in France and Delos Cloud in Germany are independently operated national partner clouds, for customers that need a different ownership and operating model. The post names no such partner for Hungary, but the model exists, and it answers the jurisdiction question better than a list of controls does.

ECIPE's study cuts against us as well. Its warning is that sovereignty labels steer public contracts to domestic providers and fragment the European market. A small Hungarian operator using the word sovereign is part of the pattern it describes.

And the evidence we asked of AWS we have not yet published ourselves. On 1 October we said we owe a plain document on how an ATAILA island behaves when its uplinks are cut. It is still owed.