Every production system has a node you cannot afford to lose — the one where, if it goes dark, everything downstream goes with it. Switzerland just put a franc figure on prying loose one of its own. The Federal Chancellery is spending 9 million Swiss francs (about $11 million) to move 3,000 federal workstations off Microsoft 365 and onto openDesk, the open-source office suite built by Germany’s Centre for Digital Sovereignty (ZenDiS), as TechSpot reported.

The pilot that unlocked the budget was small and legible: PoC BOSS, 172 federal employees running openDesk in place of Outlook, Teams and the rest for real work. Document processing and mail held up; “large-scale” video conferencing was where the seams showed. The Federal Council read that as a pass and set a hard date — 3,000 machines Microsoft-free by the end of 2027. That is 7% of the federal workforce. The full fleet is 54,000 computers, and the military’s Cyber Command is moving faster still, targeting October 2026.

Read this as topology, not politics. Microsoft 365 is not one product; it is a single operator sitting on top of your identity, your mail, your files and your meetings at once. Bern University’s Matthias Stürmer names the failure mode plainly: a foreign jurisdiction can compel the vendor to surrender data the vendor holds on your behalf, and the annual licence increase is a cost you do not set. Both are properties of one design decision — you concentrated identity, storage and enforcement behind a single operator who answers to someone else’s law. Switzerland’s 2024 EMBAG law is the policy that finally lets agencies refuse that concentration.

PAZ’s own reference frame for this is Zero-Trust identity: keep the decision plane — who is allowed — physically separate from the enforcement plane — what actually opens. A single vendor that owns both is a master key waiting to be handed over. openDesk does not erase that risk; it re-splits the operators so none of them can reconstruct the whole. The trade is explicit, and worth stating flat: you gain sovereignty and inherit the integration work Microsoft used to do for you — the video-conferencing gap is that bill, itemised.

←TODAY: Bern pays $11M to remove one vendor from 3,000 desks by end-2027.
→3012: Sovereignty is measured in dependency edges cut, not features bought.
Fulcrum: A dependency you can price is a dependency you can finally choose to keep or cut.

Your office runs the same topology one industry over. The BIM stack concentrates model storage, licensing and identity behind a handful of US vendors whose cloud terms and price curves you do not control. PAZ has covered the individual-scale version of the same instinct before — Steve Hanov running $10K-MRR companies on a $20/month stack precisely to refuse the ~$300 cloud baseline he never chose. Switzerland’s move is not a call to rip anything out; they are migrating 7% and watching the failure modes, not torching 54,000 machines. It is a call to know your graph before someone else’s outage or price hike draws it for you.

Atelier: For a Büro adopting AI and cloud BIM at the same time, the sovereignty question is no longer abstract — every AI feature you switch on adds another operator holding your project data. Munich’s Linux experiment (started 2004, reversed by 2017) is the honest warning: migrations fail on retraining and integration, not on the software. Your one Monday move: pick a single workflow — say, model handoff — and write down every external service it touches and who is legally allowed to read what passes through. That one honest list beats a strategy deck.

Hack: Rank your stack by how many things die when one vendor goes dark. List each service against what it leans on, then count how many services fall with each node — the high-count nodes are your single points of failure.

from collections import Counter
deps = {"BIM": ["store","SSO"], "Mail": ["M365","SSO"], "Meet": ["M365"], "SSO": ["M365"]}
load = Counter(d for reqs in deps.values() for d in reqs)
for node, n in load.most_common(): print(f"{node:6} {n} systems fall with it")
# M365 -> 3: your master key

Run it against your real services, not the tidy architecture diagram. The value is the third dependency on one vendor that you forgot you had.

Draw the dependency graph for one workflow before the end of the day — not the architecture diagram, the graph of who can read your data and whose outage takes you down. Switzerland found its master key was worth 9 million francs to remove. Find yours while it is still a line item and not an incident.

Source: techspot.com