Sovereign Storage Scales, but Office Habits Prove Stubborn in France's Digital Independence Drive

A Fire, a Pandemic, and the Decision to Own the Stack

In 2021 a blaze at an OVH data center wiped out swaths of Ministry of Education data, crystallizing a risk France had debated for years: critical public infrastructure sat on platforms whose continuity Paris could not guarantee. The incident, paired with the operational scramble of 2020 when COVID-19 pushed millions of students and teachers online, accelerated a shift the Ministry had sketched since 2018. By 2024 contracts were signed to deploy Nextcloud - an open-source storage and collaboration suite - across the Ministry's user base. The goal was clear: federated storage and account management that no external actor could shut down or surveil.

At DailyTechWire we have followed similar sovereign-infrastructure projects across the European Union, and the French deployment stands out for its scale and candor about the obstacles. Benoît Piédallu, the Ministry's National Project Manager of Shared Digital Services, told an audience in Munich last week that the platform now hosts slightly more than 400,000 accounts, with an ambition to reach 1.2 million. Each account can claim up to 100 gigabytes, a ceiling that would sum to 120 petabytes if fully utilized; in practice average consumption hovers near three gigabytes, and about 80,000 sync clients maintain persistent connections. The numbers confirm that sovereign file storage can work at the scale of a national ministry.

The Desktop Dilemma: Policy Meets Muscle Memory

Piédallu's presentation also surfaced the constraint that policy declarations often gloss over. Right now the Ministry does not mandate which desktop applications users run. Teachers and administrators are free to use Microsoft Office on their local machines, and many do. When files created in that ecosystem fail to behave as expected on the Ministry's open-source back end, support tickets land with a familiar refrain: "It is not working." The Ministry's reply is equally blunt - switch software.

That exchange encapsulates the tension at the heart of digital sovereignty in practice. Users have spent years building fluency in Microsoft's interface conventions, keyboard shortcuts, and file formats. Office performs best when paired with OneDrive, SharePoint, and the rest of Microsoft's cloud services - precisely the dependencies France's policy aims to sever. Storage and synchronization can migrate to European, open-source rails without enormous friction, but the visible layer where people draft budgets, grade essays, and prepare slide decks has proven stickier.

The dynamic is not unique to France. Across ministries in Berlin, Rome, and Brussels, procurement teams have discovered that lifting a workload out of a hyperscaler's orbit requires more than new contracts; it requires retraining thousands of civil servants and accepting a period of reduced productivity while habits rewire. The French Ministry's candor about allowing Microsoft on the desktop, even as it builds sovereign storage beneath, illustrates a pragmatic middle path - one that buys time but defers the harder migration.

What Sovereignty Means When the Layers Do Not Align

Digital sovereignty carries different definitions depending on who is drafting the white paper. For some it means data residency within national or EU borders. For others it means control over the source code, the ability to audit and modify without permission from a vendor in Redmond or Palo Alto. For Piédallu and his team the priority is operational autonomy: no external party should possess the ability to switch off the Ministry's services or access its data without French consent.

That framing has immediate geopolitical context. United States export-control regimes, the Cloud Act's extraterritorial reach, and periodic diplomatic friction over data-transfer agreements have all fed European anxiety about reliance on American technology companies. The European Technological Sovereignty Package, announced by Brussels, seeks to increase digital autonomy across the bloc, though analysts caution that overlapping compliance requirements may complicate procurement rather than simplify it.

France has been among the more vocal member states. Recent government pledges emphasize reducing dependence on non-European platforms, and the Education Ministry's Nextcloud deployment serves as a flagship proof point. Yet sovereignty at the infrastructure layer does not automatically extend upward. If the productivity suite, the identity provider, the endpoint-management tools, and the collaboration apps all remain tethered to a single vendor's cloud, the sovereign storage tier becomes an island rather than a foundation.

Euro-Office and the Long Road to Desktop Autonomy

Nextcloud released Hub 26 last week, bundling a productivity suite branded Euro-Office. The timing is deliberate. By offering word processing, spreadsheets, and presentation tools within the same open-source envelope as storage and sync, the project aims to close the gap that currently lets Microsoft Office persist on Ministry desktops. Whether teachers and administrators will migrate to Euro-Office in meaningful numbers remains an open question.

Adoption hinges on feature parity, interoperability with legacy file formats, and the less quantifiable variable of user experience. A spreadsheet that lacks a familiar pivot-table workflow or a presentation tool that renders animations differently can generate friction sufficient to stall a rollout. The Ministry's current posture - allowing users to choose their desktop software - buys goodwill and maintains productivity in the short term, but it also means the sovereignty vision remains incomplete.

Other European governments are watching. Estonia's public sector has piloted open-source office suites in selected agencies; Germany's Federal Office for Information Security has funded interoperability work to ease transitions away from proprietary formats. Each experiment contributes data points about where the pain concentrates: usually not in storage or compute, but in the everyday tools that shape how work gets done.

The Hyperscaler Gravity Well

Microsoft and its hyperscaler peers have spent two decades embedding themselves into enterprise and public-sector workflows. Free tiers for education, aggressive volume licensing, and integrations that reward staying within a single vendor's stack have created switching costs that go beyond contract penalties. Users develop fluency in one environment; IT teams build automation and security policies tuned to that environment; compliance audits and training materials assume it. Escaping that gravity well requires not only technical substitutes but also institutional commitment to absorb transition costs and user frustration.

The French Ministry's experience suggests that the first phase - standing up sovereign infrastructure for storage and identity - is achievable at scale within a few years. The second phase - migrating the visible productivity layer and retraining users - will take longer and encounter more resistance. It is also the phase that determines whether digital sovereignty becomes a lived reality or remains a back-end curiosity that users route around whenever a deadline looms.

Implications for the Broader European Push

France's deployment offers both encouragement and caution for the rest of Europe. On the encouraging side, 400,000 accounts and 80,000 persistent sync clients demonstrate that open-source collaboration platforms can handle the load, survive procurement cycles, and integrate with existing identity systems. The Ministry has shown that a mid-sized nation can build and operate storage infrastructure that does not depend on a hyperscaler's goodwill or a foreign government's export policy.

The caution lies in the desktop layer. As long as users default to Microsoft Office because it is familiar, the sovereignty stack remains half-built. Files created in proprietary formats, macros that depend on vendor-specific APIs, and collaboration workflows tuned to SharePoint all create dependencies that a sovereign storage tier cannot eliminate on its own. The arrival of Euro-Office in Hub 26 is a step toward closing that gap, but adoption will require the Ministry to shift from permissive guidance - use whatever you want - to active migration campaigns, training programs, and acceptance that productivity may dip before it recovers.

Other European ministries and agencies considering similar moves should note the timeline. France began exploratory work in 2018, accelerated after the OVH fire in 2021, signed contracts in 2024, and is only now approaching half a million users. The full vision of 1.2 million accounts, each with desktop tools that match the sovereignty of the storage layer, likely lies several more years ahead. Digital sovereignty is not a single procurement decision; it is a multi-year organizational transformation that touches procurement, training, support, and culture.

The Sovereignty Scorecard So Far

By the metrics that matter for operational autonomy, the French Ministry of Education has made measurable progress. Storage and synchronization now run on infrastructure that French administrators control, auditable code that can be modified without vendor permission, and servers that sit within jurisdictions Paris trusts. No external party can unilaterally shut down access or demand data under a foreign legal regime. Those are real gains.

The incomplete part of the scorecard is user behavior. When a teacher opens a laptop and launches Microsoft Office by habit, the sovereignty of the back-end storage becomes less relevant. The file may sync to a Nextcloud instance, but the creation, editing, and collaboration all happen inside a Microsoft-controlled environment. Telemetry flows to Redmond, feature updates arrive on Microsoft's schedule, and format lock-in persists.

Piédallu's willingness to acknowledge this gap in a public forum is itself notable. Many sovereign-cloud projects prefer to declare victory at the infrastructure layer and avoid discussing the desktop. The French Ministry's transparency about the challenge suggests a recognition that sovereignty is not binary - it is a gradient, and moving further along that gradient will require confronting user habits, not just server locations.

What Comes Next

The Ministry's roadmap includes expanding the account base toward 1.2 million and, implicitly, encouraging or requiring migration to Euro-Office and other open-source desktop tools. Success will depend on three variables: whether Euro-Office reaches feature parity quickly enough to satisfy power users, whether the Ministry invests in training and change management at the scale the transition demands, and whether political commitment to digital sovereignty remains strong enough to absorb the inevitable complaints and productivity dips.

Across the English Channel, the United Kingdom's public sector has oscillated between open-source mandates and returns to Microsoft. Germany's federal and state governments have run parallel experiments, some successful and some quietly shelved. The pattern suggests that technical capability is rarely the bottleneck; political will and user-experience design are.

France's deployment is now large enough to generate lessons that smaller pilots could not. If the Ministry succeeds in moving the majority of its 1.2 million target users onto a fully open-source stack - storage, identity, and desktop productivity - it will provide a template for other EU member states and a proof point that digital sovereignty can extend beyond infrastructure into daily work. If the desktop layer remains dominated by Microsoft, the project will still represent progress but will also underscore the limits of sovereignty achieved only at the back end.

For now the French Ministry has demonstrated that sovereign storage scales. The harder test - whether sovereign productivity tools can displace two decades of Microsoft muscle memory - is still ahead.