I don't see any German text provided in your message to translate. You've only included the English word "draft". Could you please provide the German text you'd like me to translate?

Digital Sovereignty of Switzerland: Strategic Rhetoric Meets Microsoft Reality

Blog (EN) pending

Editorial Mode: CLARUS_ANALYSIS Index Recommendation: INDEX Language/Role: FULL_ANALYSIS Fact-Check Date: 2026-03-26

Analysis: Digital Sovereignty and Sovereign AI Infrastructure of Switzerland

Executive Summary

The Council of States adopted Motion Juillard 24.3209 "For a sovereign digital infrastructure" on March 20, 2026, with 31:11 votes against the Federal Council's recommendation. The Federal Council had recommended rejection, referring to existing instruments such as EMBAG and the report on Postulate Z'graggen 22.4411. Simultaneously, the federal administration completed the full rollout of Microsoft 365 at the end of 2025 – including VBS and FEDPIC. Parliament debates sovereign infrastructure while the executive creates facts in the opposite direction.

Key Persons

  • Charles Juillard (Center/JU, Council of States, First signatory Motion 24.3209)
  • Isabelle Chappuis (Center/VD, National Councillor, Parallel motion 24.3363)
  • Jacqueline Badran (SP/ZH, National Councillor, Motion 25.3506 – rejected by Federal Council)

Topics

  • Digital Sovereignty
  • Open Source Software in Federal Administration
  • Swiss Government Cloud
  • Microsoft 365 and Vendor Lock-in
  • EMBAG Art. 9 (Public Money – Public Code)
  • Hybrid Multi-Cloud Strategy

Clarus Lead

The real contradiction in the "digital sovereignty" dossier lies not between parties, but between parliamentary rhetoric and executive action. While the Council of States demands a legislative revision for sovereign infrastructure with a clear majority, the Federal Council has systematically slowed down every binding initiative – while simultaneously deepening dependence on US hyperscalers. The central question is not whether Switzerland wants digital sovereignty, but whether it is ready to draw the consequence: Open Source not as an emergency plan, but as standard architecture.

Detailed Summary

Contradiction 1: Microsoft 365 Completed, Open Source as "Proof of Concept"

In December 2025, the Federal Chancellery reported the completion of the M365 rollout across the entire central federal administration. Simultaneously, the "PoC BOSS" (Office Automation with Open Source Software) has been running since early 2025 – a feasibility study that will only deliver initial results in mid-2026. The temporal sequence is revealing: The federal administration has contractually and operationally committed itself fully to Microsoft before the alternative has even been evaluated. The PoC BOSS explicitly tests open source as an emergency replacement in case of M365 failure and for processing sensitive documents – not as a primary working environment. This means: Open source is conceived as backup insurance, not as an exit strategy.

Contradiction 2: "Sovereign Cloud" with American Hyperscalers

The Swiss Government Cloud (SGC), for which Parliament approved a commitment credit of 246.9 million CHF in December 2024, is explicitly designed as a Hybrid Multi-Cloud. The National Council's Finance Committee explicitly stated that this is not a "sovereign cloud" in the sense of a purely state infrastructure. The public cloud services procured in 2022 from five major providers – including US hyperscalers – remain an integral part of the SGC architecture. The wording in the federal decree that procurements should "when possible" prefer open standards, open source software and Swiss companies is legally non-binding.

Contradiction 3: Federal Council Systematically Slows Binding Initiatives

The pattern is consistent: The Federal Council accepts soft instruments (postulates, reports, interdepartmental working groups) but rejects binding mandates:

  • Postulate Z'graggen 22.4411: Acceptance recommended → Report adopted (November 2025)
  • Motion Badran 25.3506: Rejection requested, with reference to existing resources
  • Motion Juillard 24.3209: Rejection requested, overruled by Council of States (31:11)
  • Motion Chappuis 24.3363 (parallel initiative in National Council): Treatment pending

In its statement on Motion Juillard, the Federal Council referred to Art. 11 EMBAG as an already existing legal basis. This argument overlooks that EMBAG regulates the publication of software, not the active development of sovereign infrastructure.

Contradiction 4: EMBAG Without Enforcement

EMBAG Art. 9 obliges federal authorities to publish their source code as open source. In practice, however, there is no central enforcement authority: Each authority is responsible for itself. The Digital Switzerland Advisory Board suggested in December 2025 the creation of a central open source specialist unit – an admission that decentralized implementation is not working. The demand "Public Money – Public Code" is in the law but remains largely a dead letter without institutional anchoring.

Contradiction 5: Discussing Sovereignty, Expanding Surveillance

Parallel to the sovereignty debate, the Federal Council planned a tightening of VÜPF (Ordinance on the Surveillance of Postal and Telecommunications Services), which would have prompted companies like Proton and Threema to consider relocating from Switzerland. When the state propagates digital sovereignty on one hand but endangers the technological basis of its own flagship companies for encryption and data protection on the other, a credibility problem emerges.

Key Statements

  • Parliament drives the topic of digital sovereignty with growing urgency, the Federal Council systematically brakes on binding measures.
  • Open source plays a surprisingly small explicit role in parliamentary initiatives – most motions speak of "infrastructure" without defining the technological foundation.
  • Factual dependence on Microsoft and US hyperscalers was deepened, not reduced, in 2025.
  • The Federal Audit Office has determined that the economic benefit of the Swiss Government Cloud for the Confederation has not yet been proven.

Critical Questions

(a) Evidence / Data Quality / Source Validity

  1. On what empirical basis does the Federal Council claim in its report on Postulate 22.4411 that the federal administration has "a good overview" of its digital dependencies – is there a public register of proprietary systems used and their substitution costs?
  2. Why was PoC BOSS only started in early 2025, although EMBAG has been in force since January 2024 and the strategic anchoring of open source in the "Digital Federal Administration Strategy" had already taken place?

(b) Conflicts of Interest / Incentives / Independence

  1. What influence did existing contracts with Microsoft and public cloud providers have on the Federal Council's recommendation to reject Motion Juillard? Is there disclosure of contractual lock-in clauses?
  2. Who sits on the interdepartmental working group that the Federal Council established in November 2025, and which representatives of the open source community or Swiss technology companies are involved?

(c) Causality / Alternatives / Counter-hypotheses

  1. Is the "Hybrid Multi-Cloud" strategy actually a sovereignty gain – or does it legitimize the continuation of hyperscaler dependence under a new label? What concrete exit scenarios exist in case a US provider restricts its services due to geopolitical changes (e.g., CLOUD Act conflicts)?
  2. Why is there no explicit open source obligation in most parliamentary initiatives on digital sovereignty? Is there a risk that "sovereign infrastructure" ultimately means proprietary Swiss providers that reproduce the same vendor lock-in problem?

(d) Feasibility / Risks / Side Effects

  1. How realistic is the SGC timeline (first functionalities 2026, migration from 2027), when the Federal Audit Office has already criticized that the economic benefit has not yet been calculated?
  2. How does the Federal Council resolve the contradiction between VÜPF surveillance expansion and the goal of positioning Switzerland as a trustworthy location for digital sovereignty?

Bibliography

Primary Source: Clarus News Analysis – "Digital Sovereignty and Sovereign AI Infrastructure of Switzerland" (26.03.2026) – clarus.news

Supplementary Sources:

  1. Federal Council, Report in fulfillment of Postulate 22.4411 Z'graggen (26.11.2025) – news.admin.ch
  2. Netzwoche, "Council of States says yes to sovereign AI infrastructure" (23.03.2026) – netzwoche.ch
  3. Federal Chancellery, Feasibility Study PoC BOSS – bk.admin.ch
  4. Federal Chancellery, Press Release Completion of M365 Rollout (18.12.2025) – news.admin.ch
  5. Federal Office of Information Technology, Systems and Telecommunication, Swiss Government Cloud – bit.admin.ch
  6. Federal Audit Office, Key Project Swiss Government Cloud (03.12.2025) – efk.admin.ch
  7. Digital Switzerland Advisory Board, Open Source should be promoted more strongly (01.12.2025) – bk.admin.ch
  8. Inside IT, "Sovereign digital infrastructure comes back on Parliament's agenda" (21.03.2024) – inside-it.ch
  9. Swiss IGF 2025, Session 5: Digital Sovereignty – igf.swiss
  10. NZZ, "Technology instead of protectionism" (12.12.2025) – nzz.ch

Verification Status: ✓ 2026-03-26

This text was created with the support of an AI model. Editorial responsibility: clarus.news | Fact-checking: 2026-03-26

Zurück zur Übersicht