The milestone, in the company's own framing

Christian Wölbert's report for heise/c't relays Delos's opening: in October, the company took over "the operative operation of the sovereign cloud platform completely into its own hands," and "the technology supplier Microsoft now has no more access to the platform." The Delos Cloud GmbH has been building the public-administration cloud since its 2022 founding: Microsoft supplies the software and the updates, the data centers belong to Delos, and Arvato Systems operates as partner. Launch: early 2027. The structure's entire sales pitch is jurisdictional — the data and the operations live in contracts enforceable under German law, not under US process.

The certification ladder around that claim is real and partially done: ISO/IEC 27001 is achieved for the ISMS and for operating the Delos Cloud Direct Connection; C5 type 1 and type 2 attestations and ISO 27001 on a BSI IT-Grundschutz basis are what the next months are for; the BSI Cloud Platform Requirements review is running. Onboarding gates follow the ladder: Länder and municipalities can adopt once C5 type 1 plus the ISO 27001 certificate exist, while federal agencies face the two-stage path — C5 type 2 and IT-Grundschutz first, then a usage recommendation from the federal digital ministry inside the joint audit project.

What the claim is for

This site read Microsoft's sovereign portfolio in October and said the National Partner Clouds were the tell: Delos is SAP operating Microsoft software on German soil, the "independently operated" tier, a different legal entity with the customer's jurisdiction — the reason the German armed forces can run on it at all. The October handover claim is that tier's founding promise arriving on schedule: someone other than Microsoft's own operating company holds the production keys.

Read the same claim the way this site graded AWS's disconnect drill: the announcement is a property claim — "Microsoft no longer has access" — and property claims need properties-grade evidence. Who holds which credentials now, what the change pipeline looks like from Microsoft's build output to Delos's production, what evidence would falsify the access statement: none of that ships with the announcement. ISO 27001 certifies the management system, not the access graph. The drill format — the one this site keeps asking for — would be: publish the operational boundary, then have someone outside the company say what they see. That remains undone.

The two streams, and the one that didn't move

The sentence to keep from the whole story is the Gesellschaft für Informatik's. Its digital sovereignty working group warns that the core of the platform is Microsoft technology: "Anyone who operates such a cloud is dependent on Microsoft delivering software updates and makes themselves erpressbar" — subject to pressure.

Split what Delos bought and what it did not:

  • The running system — operations, root access, the physical floor — moved to Delos in October, on Delos's account. That is the part jurisdictions care about when they talk about a government's data being subject to foreign process, and it is the part a C5 certificate chain can see.
  • The stream of changes — every future version, feature, and security fix — still flows from Microsoft by contract. That stream never transfers in this model. If the supply stops or changes shape, the German state keeps running what it has, frozen, at Microsoft's discretion. The GI's "erpressbar" is the operational name for that residual.

Two years ago Delos answered the sovereignty-washing charge in a long c't interview, and this site's broader argument has not changed since: the label matters less than the exit path. Compare the two German answers now running in parallel. KoDaS, the six-state school cloud tender, requires an OSI-approved license — exit backed by code; any qualified operator, not the incumbent, can take over the workload. Delos is exit backed by contract and audits — a real but different kind of exit, one that leaves the software's future in the hands of a single vendor. Neither is wrong. They are different bets on the same sentence: when the relationship with the technology supplier fails, what do you still own? The code answer is unfalsifiable by a licensing decision; the contract answer expires with the relationship.

The honest column

  • The handover claim is the company's own. No independent party has described the operational boundary, no artifacts are published, and "no more access" is ambiguous on its face — it plausibly means no production-operations access, not no role in the software supply, which Delos's own model (Microsoft as technology supplier delivering software and updates) confirms. Read the strong version neither into nor out of the announcement.
  • C5 type 2 and IT-Grundschutz are pending, so federal agencies are not cleared to adopt — the early-2027 target is a future claim, and the deadline pressure that creates for the certification chain should be watched, not assumed away.
  • Delos is not claiming update independence and never has; the GI quote charges the structure, and Delos's 2023 interview is a rebuttal to the label, not to the dependency. This site's grading: the operational milestone is plausible and important, the remaining dependency is named by the critics rather than hidden by the vendor, and what is still missing is exactly the artifact layer that would convert the claim from company statement to inspectable fact.
  • For the "independently operated" pair: Bleu in France has made no equivalent public claim in this window. Delos claiming it first is a data point about the German procurement culture — EUR 1.9 billion in standing Microsoft licenses still buys a lot of patience with the vendor who will not leave.

For your deployment

  • Name the two streams in every managed-sovereignty contract you sign — for a shared admin cloud, a community Nextcloud, a managed backup service, a K8s control plane. Stream one: who holds operational root and under which authority? Stream two: who decides what the software becomes next month? A provider with clean answers on one and silence on the other is a Delos-shaped contract at your scale.
  • Demand the artifact layer before the certificate impresses you: the credentials matrix, the change pipeline, and a test that shows the boundary — the community-drill outputs that this site keeps holding up as ahead of the market leaders.
  • Ask the update question out loud, even though it is embarrassing: what happens to our running system if your software supplier changes licensing, cadence, or interest? The answer for Delos is "it keeps running, frozen, under our jurisdiction" — a defensible answer, and one most managed providers cannot even give. The community-scale equivalent is knowing which of your dependencies can go quiet and who maintains what, per stream.

Sources: heise online / c't, Christian Wölbert: Umstrittene Cloud für den Staat — Delos will Anfang 2027 starten (November 10, 2026), English version; c't interview 2023: Wie unabhängig ist die Delos Cloud?; this site's Microsoft sovereignty-menu read, KoDaS procurement analysis, and AWS drill grading.