The ongoing debate surrounding digital sovereignty, open-source adoption, and reliance on proprietary tech giants has taken a complicated turn in Denmark. Following earlier media reports that suggested the Danish government was dramatically casting aside Microsoft in favor of open-source office software, a clearer and much more nuanced picture has emerged. Collabora, one of the central firms involved in the initiative, has published its own detailed account of the events, shedding light on a small-scale government pilot that faced technical hurdles, political transitions, and an abrupt end before a formal evaluation could ever take place.
The initiative first caught international attention in June 2025, when reports surfaced that the Danish Digitalization Ministry was preparing to transition away from Microsoft Office 365 toward open-source solutions like LibreOffice and Collabora. Subsequent clarifications from the ministry, however, painted a much more modest picture. Rather than a sweeping, government-wide migration, the initiative was actually a localized, voluntary test project launched within a single department of the ministry.
A Volunteer Test, Not a Comprehensive Switch
The pilot officially began in June 2025, when a cohort of volunteer employees within the Danish Digitalization Ministry’s own department began drafting and editing documents using Collabora instead of traditional Microsoft editors such as Word, Excel, and PowerPoint. To facilitate this shift, the ministry partnered with cBrain, the Danish technology company responsible for developing the ministry’s F2 case and document management system. cBrain was tasked with the crucial job of integrating Collabora directly into the existing F2 workflow.
From the very beginning, the ministry took pains to characterize the initiative as a strictly controlled test rather than an aggressive decoupling from Microsoft. Officials emphasized that any wider rollout across the department would hinge entirely on the results of the trial. Just days after the pilot’s launch, the ministry clarified to the Danish tech publication Version2 that no official decision had been made to phase out Microsoft products, and explicitly stated that there were no plans to replace the underlying Windows operating system with Linux.
Despite the limited scope of the pilot, friction was inevitable as employees tested the alternative software in real-world administrative scenarios. In December, the Danish engineering publication Ingeniøren published an investigative report detailing complaints gathered from testers during the months leading up to an evaluation workshop held in October. According to correspondence and documents obtained through freedom of information requests, participating civil servants encountered several frustrating bugs and compatibility issues.
Among the chief grievances were documents received from external government agencies that occasionally opened as completely blank files, tracked changes that proved difficult to accept or review properly, and line spacing that appeared distorted when crossing between platforms. These teething pains are common when introducing new software into legacy bureaucratic environments, but they created tangible frustration among the staff tasked with using the alternative suite.
Despite these hurdles, the project initially pushed forward. Later reporting from Ingeniøren highlighted comments from Frejdie Søndergaard-Gudmandsen, cBrain’s head of product management, who defended the technical glitches as normal, expected growing pains for any software pilot of this scale. At the time, indications suggested that the ministry intended to continue the testing phase into 2026 to thoroughly vet the platform.
Two Versions of Why the Project Stopped
The trajectory of the pilot shifted abruptly in October, though accounts regarding why the project ultimately folded differ significantly depending on the source.
According to statements provided by a ministry press officer to Ingeniøren in October, the project was quietly scrapped. The press officer pointed to the calling of a national election as a major disruption that derailed the timeline, preventing the planned evaluation from taking place. As a result, staff members stopped using Collabora entirely, and the ministry confirmed there were no ongoing plans to revive the software suite within the department.
Collabora, however, presented a markedly different narrative regarding the project’s demise. In its published account, the open-source software provider argued that a major administrative reorganization in June fundamentally altered the landscape. That reorganization effectively dissolved the Digitalization Ministry as a standalone entity, leaving the pilot project effectively orphaned before a proper, comprehensive evaluation could be conducted. Collabora maintained that this structural upheaval should not be interpreted as a failure of the office suite itself.
Furthermore, Collabora noted that political shifts compounded the administrative changes. A national election was called in February, and the new government that took office in June merged the digitalization portfolio into the broader Ministry of Research and Education.
Addressing the technical complaints raised by testers earlier in the project, Collabora asserted that the initial phase of the technical integration was fundamentally successful. The company stated that its engineering team actively worked to resolve the support tickets generated by the ministry’s testers—often absorbing the costs of that developmental and troubleshooting work itself. Collabora also emphasized that the knowledge and experience gained during the Danish ministry pilot are actively being carried forward into ongoing work with other public authorities in Denmark in partnership with cBrain, even if the formal assessment within the digitalization department was never officially finalized.
The political leadership has also acknowledged the unusual conclusion of the pilot. On October 27, Minister for Research, Education, and Digitalization Christina Egelund addressed the topic during an appearance on the Danish broadcasting corporation DR’s P1 Morning radio program. Egelund admitted that she had limited insight into the precise reasons why the project concluded without a formal evaluation, noting pointedly that the initial decisions and subsequent handling of the pilot occurred under the watch of the previous administration.
Reassessing the Early Media Narrative
The divergence between early media reports and the actual scope of the project has provided a case study in how complex administrative trials can be amplified in the public sphere.
Initial coverage, including a prominent June 2025 report by the newspaper Politiken, suggested that the Danish government was actively transitioning from Microsoft Office 365 to LibreOffice, with full departmental adoption anticipated as early as autumn. Those early reports catalyzed widespread international discussions regarding European digital sovereignty and the feasibility of public institutions moving away from dominant American tech conglomerates.
As subsequent official clarifications emerged, media outlets began to recalibrate. The ministry’s insistence that no definitive decision had been made to phase out Microsoft, combined with revelations that the project was merely a voluntary test involving a single department, brought a dose of reality to the headlines. Politiken subsequently adjusted its reporting to reflect the more modest parameters of the pilot, and other outlets worked to correct early misconceptions regarding broader operating system changes.
Ultimately, the Danish digitalization pilot leaves behind a complicated legacy. While it did not result in a permanent, government-wide migration away from Microsoft, it provided valuable lessons regarding software compatibility, inter-agency document exchange, and the logistical challenges of integrating open-source tools into entrenched bureaucratic workflows. As public sector entities across Europe continue to grapple with questions of digital independence, the experiences of the Danish ministry and the insights published by Collabora will likely inform future attempts to diversify government technology stacks.
