Monday's post said the interesting thing about the AWS European Sovereign Cloud drill scheduled for October 24 was its genre: a dated, timed disconnect that can be failed — a falsifiable sovereignty claim. On the same day, Microsoft published the next stage of its own sovereign cloud portfolio. The two documents describe the same customer anxiety — who can still reach the systems that matter when the network, the jurisdiction, or the vendor relationship changes — from opposite ends. AWS is scheduling a demonstration of state. Microsoft is shipping a menu of tiers. Both deserve reading, and one of them can be failed.

What is actually in the menu

Stripping the prose, the announcement has four load-bearing items:

Sovereign Control Panel (public preview at Ignite): a portal that surfaces "sovereignty posture," applies controls, identifies gaps — and, the part worth underlining, "supports business continuity readiness by helping customers understand workload dependencies and assess portability across operating environments."

Operator accountability in the EU/EFTA: Data Guardian adds European-resident oversight by a trusted EU partner for qualifying Microsoft engineer remote access to in-scope production systems, and the Production Touch Ledger creates "tamper-evident records" of that access and the actions performed.

Keys you physically hold: external key management with Azure Managed HSM is now generally available — the root encryption key stays in hardware the customer owns and operates, on-premises or through a trusted third party.

Sovereign Private Cloud, built on Azure Local: customer-operated environments running in connected and disconnected models, with workloads able to transition from connected to disconnected operations — entering public preview. Around it, SQL Server on Azure Local is GA for both modes; DocumentDB and Blob Storage on Azure Local enter public preview; GitHub Enterprise Local becomes a validated GitHub Enterprise Server appliance on Azure Local at Ignite; Foundry Local goes GA for connected and disconnected operations with a model catalog that includes open-weight and open-source entries; and Microsoft 365 Local extends SharePoint and Exchange into that environment in preview. Microsoft also published new "sovereign business continuity guidance and architecture patterns."

The National Partner Clouds — Delos in Germany, Bleu in France — appear as the third loop: "independently operated environments." Hold that phrase; it is the most important one in the document and Microsoft did not underline it.

The parts worth taking seriously

It is easy to dunk on sovereignty marketing and wrong to write this menu off, because three of its items are precisely the mechanisms this site asks for in sovereign-washing audits — including the AWS one from Monday. Tamper-evident logging of vendor operator access is a real control: it turns "Microsoft staff can't see your production" from a promise into an inspectable record. The Physical HSM root key is the strongest data-custody control a hyperscaler can offer without changing its legal structure — if you hold the root key, encryption ceases to be a policy commitment and becomes a physical fact. And publishing architecture patterns for business continuity, rather than selling a badge, means buyers can copy patterns and test them independently. These are the right mechanisms for the tier they serve: organizations that have decided to keep the vendor and want evidence-grade restraint on it. If your organization is in that tier, ask for all three, in writing, and demand exportability of the Touch Ledger — a tamper-evident log you cannot export and retain off-platform is accountability theater with the audit trail stored in the same filing cabinet as the behavior being audited.

The toggle problem

The headline capability — workloads transitioning from connected to disconnected operations, public preview — is sovereignty as a switch the vendor ships. Switches have shipped broken since the first switch. A preview toggle is a product plan, not a state, and nothing in the announcement demonstrates the disconnected mode doing real work under real load — no drill is scheduled, no failure mode is published, and the grading of the transition will be done by the same entity that graded it into being. This is exactly the gap Monday's post drew around the AWS ESC drill: drills are falsifiable, decks are not, and a preview is a deck with a changelog. The copyable demand is already written: when the Sovereign Private Cloud reaches your procurement table, the condition is a timed disconnect on a calendar — ideally one Microsoft doesn't choose alone — with the runbook and the results published, the way BSI-adjacent buyers are beginning to ask of the ESC.

The portability score in the Control Panel has the same shape in quieter form. A dependency map and a portability rating computed by the vendor are the vendor's assessment of the vendor's homework. If portability matters to your continuity plan — and it should, because the EU Data Act has made exit an architecture requirement — then the number that counts is the one your own export run produces: restore your data, your code, your configuration into an environment Microsoft doesn't operate, on a date chosen by you, and time it. Use the Control Panel's dependency map as a checklist of what to carry, not as the grade.

And the legal floor stays exactly where every hyperscaler sovereignty analysis on this site left it: Sovereign Private Cloud is Microsoft technology, under Microsoft's control plane, offered by a US parent group. Azure Local appliances are operated by the customer, which is more than most sovereign SKUs grant — but operating Microsoft's appliances is not the same thing as operating your own stack, and no preview toggle reaches a US court order. The menu sells operational autonomy over Microsoft's dependency surface. That is real and worth having when the choice is Microsoft either way. It is not legal sovereignty, and the announcement — to its credit, mostly — does not pretend otherwise. Mostly.

The honest part of the graph

The National Partner Clouds are the tell. Delos Cloud is SAP operating Microsoft software on German soil; Bleu Cloud is Orange and Capgemini operating it in France. Microsoft's own marketing calls them "independently operated," and that phrase is doing the work the rest of the portfolio can't: the reason Delos can sell to the German military is not a Microsoft feature tier, it is a different legal entity — a company whose jurisdiction is the customer's. This is the quiet concession in the announcement. What killed Azure Germany was not a missing certificate; it was missing capability — the sovereign tier didn't have the services customers wanted, so they left. Microsoft's answer this year is to make the capability follow the tier: appliance-local SQL, GitHub, models, SharePoint. Whether the sovereign tier that emerges from this is operable only by a Microsoft-controlled plane, or by a Bleu or a Delos with real feature parity, is the question that decides if the EU's sovereignty procurement lands somewhere with teeth or somewhere with plumbing.

What a community buyer should write down

If your city hall, fire district, or co-op is evaluating this portfolio — some will, it is aimed squarely at critical infrastructure with limited staff — five lines go in the requirements document:

  1. Timed disconnect drill, results published. The connected-to-disconnected transition enters acceptance testing when someone independent has pulled the wire. Copy the AWS format; date, runbook, evidence, failure modes.
  2. Portability is self-graded. Vendor dependency maps are checklists, not grades. Your export run, your restore, your timer.
  3. Custody named for every key. Who physically holds the root key HSM, and what happens to your data at 3 a.m. if your organization can't reach it.
  4. Operator access ledgers are exportable. Tamper-evident is table stakes; retained off-platform is the requirement.
  5. The legal layer is disclosed. Which entity operates which tier, under which jurisdiction, and where a foreign court order arrives.

And keep the fifth question honest with the fourth alternative: the strongest sovereignty available to a community remains the stack it can unplug and re-plug itself — Matrix, Nextcloud, Postgres, backups on hardware whose lease never expires. Whether the workload runs on your metal or a vendor's is the second question. The first is who can still reach it when the wire moves — and this month, for the first time, both the biggest vendors are treating the answer to that first question as a product requirement, because communities and public buyers made the demand loud enough that it reaches a release calendar. That is progress. It counts when it can be failed.