The Format Default Is the Strategy
Euro-Office launched with a pitch tailor-made for the current moment: a European office suite for a continent increasingly anxious about its dependency on American software platforms. The Document Foundation isn't buying it.
The foundation, which oversees LibreOffice, has publicly accused Euro-Office of being a 'de facto ally' of Microsoft's lock-in strategy. The reason is straightforward: Euro-Office defaults to OOXML — Office Open XML, Microsoft's document format — rather than ODF, the Open Document Format that is both an ISO standard and the format LibreOffice defaults to.
This is not a minor configuration quibble. Format defaults are one of the most consequential decisions a productivity software maker can make, and they almost always reflect whose interests the product is actually serving.
Why Defaults Are the Whole Game
Most users never change default settings. That's not a behavioral quirk — it's a documented pattern that platform strategists have exploited for decades. When a product defaults to OOXML, documents created in it are natively compatible with Microsoft Office and subtly incompatible with everything else. Recipients without Microsoft software encounter friction. Over time, that friction becomes a switching cost, and switching costs are how lock-in compounds.
ODF exists precisely to break this dynamic. It's an open standard, maintained by OASIS, and adopted by the EU's own interoperability frameworks as the preferred format for government documents. A product that claims to advance European digital sovereignty — the ability of European institutions to operate independently of specific vendors — while defaulting to a Microsoft-controlled format is, at minimum, sending a contradictory signal.
The Document Foundation's framing is harsher than that: it's not a contradiction, it's a strategy.
Who Wins From This?
The incentive structure here isn't hard to read. Euro-Office benefits from positioning as an alternative to Microsoft while remaining frictionlessly compatible with Microsoft's format ecosystem. That compatibility makes adoption easier — IT departments don't have to retrain staff or convert document libraries. It also means Euro-Office never actually threatens Microsoft's format dominance.
Microsoft, meanwhile, gets a competitor that competes on price and branding while reinforcing OOXML as the universal default. That's a reasonable outcome for Redmond even if Euro-Office takes some market share.
The loser in this scenario is ODF adoption — and by extension, the broader project of format-level interoperability that genuine digital sovereignty requires.
The Open-Source Wrapper Problem
This episode illustrates a pattern worth naming: open-source code does not guarantee open-source outcomes. A product can be built on LibreOffice's codebase, carry open-source licensing, and still make configuration choices that serve proprietary ecosystem interests. The code is open; the defaults are not neutral.
The Document Foundation's accusation is pointed because it's structural, not personal. Euro-Office may have no formal relationship with Microsoft. It doesn't need one. If its defaults route users into OOXML dependency, the effect is the same.
For European policymakers and procurement officers who've been told that switching to a 'European' office suite satisfies digital sovereignty requirements, this is the detail worth scrutinizing. Sovereignty isn't in the logo. It's in the format dropdown.