How proprietary formats have become Microsoft’s main tool for lock-in

In the previous article, we explored the importance of standards: how the unspoken agreements governing electrical sockets, paper sizes and file formats form the foundations of a world in which choices remain open and power is not concentrated in the hands of a single player. We concluded with a question: if open standards are so beneficial, why aren’t they universally adopted?

The answer, in the case of document formats, lies in a single page produced by Microsoft Office. Getting rid of it is harder than it seems.

A file is never just a file

When you save a document on your computer, you are choosing a format — that is, the language in which your document is written in a way that the computer can understand: the set of rules that determines how words, tables, images and formatting instructions are stored and, consequently, how they can be retrieved, shared and read in the future.

For decades, the dominant format for office documents has been that produced by Microsoft Office. Initially as binary files with extensions such as DOC and XLS, then as XML-based formats introduced with Office 2007: DOCX, XLSX and PPTX. These formats are used by hundreds of millions of people. They are the lingua franca of offices, schools, public administrations and courts around the world.

Furthermore, in significant and decisive ways, they are proprietary — meaning they belong to Microsoft, are controlled by Microsoft and serve Microsoft’s interests in ways that may not align with the interests of users.

Understanding how all this works — and why it matters far beyond mere matters of software preference — is the aim of this article.

The architecture of dependency

Proprietary formats create dependency through a mechanism that is simple in principle and extraordinarily effective in practice: they make the data contained in a document inseparable from the software used to create it.

This is not a law of physics, but a design choice.

An open format — a format whose specifications are published, freely available and implementable by any software without restrictions — stores information in such a way that any compliant application can read, write and reproduce it faithfully.

A proprietary format, by contrast, may contain undocumented features, private extensions or behaviours that only the original software implements correctly. The document may be opened by other applications, but it cannot always be reproduced faithfully.

The practical consequence is familiar to anyone who has tried to open a Microsoft Office document in another application: the formatting becomes distorted, bullet points shift, tables lose their proportions, and headings appear different.

A presentation that looked polished in PowerPoint seems slapdash in a different viewer: the content is all there, whilst the document, strictly speaking, is not.

This is “lock-in”: it is not a padlock, it is not a technical ban, it is not a contractual restriction, but a silent and persistent friction that makes any work outside the Microsoft ecosystem seem slightly off, slightly unreliable, slightly unprofessional — and ensures that the easiest route is to return to the tools that produce documents with the expected appearance.

The standard that isn’t a standard

Microsoft formats have been submitted to international standardisation bodies and approved. This has been used, time and again, to argue that concerns about “lock-in” are exaggerated — that OOXML, the Office Open XML format, is as open a standard as any other, and that the playing field is level.

The reality is considerably more complicated.

The standardisation of OOXML was one of the most contested processes in the history of ISO: national standardisation bodies reported procedural irregularities, and the votes were contested. The process has left an indelible mark on the credibility of international standards, and has resulted in a specification of extraordinary length and complexity — running to thousands of pages — which did not describe a format designed for interoperability, but rather the existing behaviour of Microsoft Office, including legacy behaviours, undocumented features and implementation details specific to Microsoft’s source code.

No other software could fully implement the format, yet it was required to do so out of respect for its users, who needed to exchange documents with Microsoft users.

The version of OOXML that was standardised — OOXML Transitional — initially co-existed with a stricter variant, OOXML Strict, which eliminated most of the problematic legacy elements, but not all. Moreover, Microsoft Office has always used OOXML Transitional as the default format, and has relegated OOXML Strict to the bottom of the options (to prevent it from being used).

The practical effect is that the format used daily by hundreds of millions of people is the one that only Microsoft’s own software implements correctly, whilst the cleaner variant — which other software could actually support — is not used, and has now even disappeared from some versions.

A standard that only one implementation fully supports is, from a functional point of view, a proprietary format with a standardisation certificate.

Lock-in, from the individual to the institution

Dependence on document formats is the main mechanism of lock-in, but it is not the only one. We discussed the layering of dependencies at length in a previous article, so we will not revisit the subject here. Levels of dependence vary depending on the importance of the documents involved and the size of the organisation producing them.

For an individual user, a document with altered layout is simply an inconvenience. For a law firm, it may mean that a contract submitted to court does not match the version in the client’s file. For a hospital, it may mean that a clinical form is printed incorrectly. For a government department, it may mean that a document appears differently depending on the software used: a silent and unintended form of unequal access to public information.

At the level of public administration, this dependency takes on a dimension that goes beyond operational efficiency. A government that archives official documents in a format controlled by a private company has, strictly speaking, delegated the custody of its institutional memory to that company. Today, documents are readable because Microsoft continues to support the format, but whether they can be read in twenty years’ time will depend on the company’s decisions, for reasons that have nothing to do with the public interest.

This is not a hypothetical risk: formats are phased out, software versions change, and features present in one version of Office may behave differently — or not work at all — in another.

The history of digital documents is littered with files that cannot be opened because the software with which they were created no longer exists or no longer works on modern systems. Proprietary formats accelerate this risk by concentrating the knowledge needed to interpret them within an organisation whose commercial interests may, at any time, diverge from the interests of those who depend on access to their own documents.

What true sovereignty requires

A truly independent document — one that displays identically on any system, in any country, for any user, regardless of the software used — requires informed choices at every stage of its creation.

At the format level, it requires an open standard such as the Open Document Format (ODF), whose specifications are published, freely implementable and managed by a body independent of any single vendor. ODF is an international ISO standard that has undergone a legitimate standardisation process and whose specifications can be fully implemented by any software that chooses to do so. LibreOffice, the leading open-source office suite, uses ODF natively. The same should apply to any other self-respecting open-source office application.

In terms of fonts, it requires open fonts, the designs of which are published under licences that allow any software to implement them and any user to install them without cost or restrictions. Open font repositories offer a wide range of high-quality options that have no proprietary dependencies.

In terms of templates and workflows, it requires institutional policies that specify open formats and open fonts as the default for all official documents — not as an aesthetic preference, but as a governance requirement, in the same way that a public administration might specify accessibility standards or data protection requirements.

At the archiving level, this requires a commitment to formats specifically designed for long-term preservation — such as PDF/A for documents intended for permanent archiving — whose specifications are public and whose readability does not depend on the commercial decisions of a single supplier.

None of this is technically complex, but it requires a conscious decision by someone with the authority to do so.

A document is never innocent

A document is an argument made visible. It is also, always, a set of dependencies made invisible.

When an institution sends a letter formatted with a proprietary font, embedded in a proprietary format, produced by proprietary software, it is not communicating information but perpetuating a dependency — in workflows, in the expectations of correspondents, in staff memory and in the implicit message to recipients — that this is precisely how documents work, that there are no alternatives, that the infrastructure of written communication belongs to someone else, and that it has always been this way.

Digital sovereignty begins with the recognition that this is a choice: the file format is a choice, the font on the page is a choice, and the software is a choice. And choices, unlike facts, can vary.

That document, which continues to be regarded as a “seemingly” innocent piece of paper, is in reality no longer a piece of paper — and hasn’t been for some time — but an executable file that is interpreted by software, and as such is no longer innocent but, in many cases, the insidious tool of lock-in.

Microsoft Office Icons: Ms Office Icon Vectors by Vecteezy
Protest against OOXML: Techrights
Innocent piece of paper: The Mazloom Law Firm, LLC

Financials and Budget – TDF Annual Report 2025

TDF Annual Report 2025 banner

This is part of the Annual Report 2025 from The Document Foundation, the non-profit that coordinates the LibreOffice project and community.

TDF exists because of a large, dynamic global community — volunteers, ecosystem companies and committed end users who support our work with donations of both time and money. The 2025 accounts tell a clear story: a foundation that grew significantly, while keeping its finances transparent and its spending tied to its mission.

A year of strong growth in income

Total income for 2025 reached € 2,175,997, a substantial increase on the € 1,387,589 recorded in 2024. The growth came from three distinct sources, and it is worth being precise about each.

The largest share, € 1,976,825, came from donations — overwhelmingly from individual users and small businesses, mostly in Europe. This was the fifth consecutive year in which donations exceeded one million euro, and the highest figure to date. Part of this increase was organic, reflecting the continued strength of LibreOffice downloads. A further part can be attributed to a concrete change: in mid-2025 we introduced a new in-product update notification on Windows, which periodically — after every major release and selected minor ones — informs users that an update is available, presents the new features, and invites them to support the project with a donation. The effect was immediately visible as a step-up in donations from the moment it was deployed, and it is keeping donations at a higher level into 2026. We mention this openly, because transparency about *why* the numbers move is as important as the numbers themselves.

The second source was income from the sale of LibreOffice through online stores, sponsoring and related commercial activity, which together generated € 168,975. The Apple App Store (€ 118,942) and the Microsoft Store (€ 35,393) accounted for most of this. The third source was € 30,197 in income from securities held under the foundation’s asset management.

How the money was spent

Total expenditure for 2025 was € 1,457,343. The breakdown by category shows where donor money goes.

  • Staff and operations remained by far the largest commitment, at € 1,091,032. This covers salaries (€ 406,736), statutory social security contributions (€ 93,244) and freelancers (€ 591,052) — the people who keep infrastructure, communication, administration and project coordination running, in order to share knowledge, support the community in its activities, and enable contributors to do their work.
  • Tenders. As in 2024, no development tenders were funded in 2025. Tenders related to LibreOffice development remain on hold, and will be resumed based on the development strategy currently under discussion according to the new Procurement Policy.
  • Events and community support amounted to roughly € 87,000, including the LibreOffice Conference (developer conference, € 51,184), community projects (€ 15,014) and student scholarships (€ 17,368), together with marketing initiatives. These funds support the events and local activities that hold the global community together, and help us to share knowledge around the world.
  • Infrastructure and hosting came to € 51,420, covering the hosting, virtual machines, services and domains that underpin the project’s technical independence — a foundational asset we continue to prioritise.
  • Legal and administrative expenses totalled roughly € 92,000, including accounting and the preparation of financial statements (€ 34,164), legal advice and counselling (€ 36,597 across project and general legal work), and insurances (€ 4,626).
  • Cost of fundraising. Receiving donations is not free. In 2025, payment-processing and banking fees came to roughly € 98,000 — Stripe fees of € 46,446 and bank transfer and money-transfer fees of € 51,190. These are simply the cost of doing business: they scale with the volume of donations we receive. It is worth adding that these figures do not capture the full picture, because PayPal’s currency-conversion costs are embedded in the transactions and not separately visible — though they are comparable in scale to the Stripe fees. We report this plainly so that no reader underestimates what it costs to collect the donations that fund our work.

Results and transparency

After expenses, the charitable entity closed the year with a result of € 554,476, asset management contributed € 21,263, and the commercial business operations returned a profit of € 142,916.

Transparency remains one of TDF’s defining characteristics — towards our donors, contributors, community and users. Our accounting is handled by a professional accountant, and our complete ledgers, listing all income and spending broken down by project, are published on our public wiki at https://wiki.documentfoundation.org/TDF/Ledgers, with only a few items obfuscated for privacy. As in previous years, and given the scale the foundation has reached, our books have been audited, and the Board continues to work with the authorities in Berlin to implement the improvements the audit recommended.

To everyone who contributed time, skills, resources and money in 2025: thank you. The foundation’s strength is your achievement.

Note: The expense categories above are indicative groupings drawn from the foundation’s accounts. They exclude VAT flows and certain material costs that the ledger handles separately, so the categories are not intended to reconcile arithmetically with the per-sphere annual results. The authoritative, fully itemised figures are published in the ledgers.

Like what we do? Support the LibreOffice project and The Document Foundation – make a donation, or get involved and help our volunteers. Thank you!

What We Owe Each Other, in Millimetres and Volts

You arrive in a city you have never visited before. You are tired. You find your room, open your suitcase, pull out a charger, and plug it into the wall. The small green light comes on. You think nothing of it, because nothing happened. You moved between two countries, two electrical grids, two regulatory regimes, and the machine in your hand simply continued to work.

Behind that uneventful moment sits more than a century of meetings, arguments, technical drawings, and compromises between people who will never meet you. The plug fits because somebody, somewhere, decided that it should – and decided further that the decision should be written down, made public, and not owned by anyone. We almost never notice this kind of work. We only notice it when it fails: the adapter that does not fit, the document that does not open, the part that cannot be replaced. Standards are the infrastructure we live inside, and like most infrastructure, they are invisible until they are not.

The public agreement

A standard is a public agreement about how things should fit together. Two words in that sentence carry the weight: public and agreement. Public, because the rules are written down and anyone can read them. Agreement, because nobody imposes them alone; they are negotiated between parties who accept that the shared space is more valuable than any individual advantage within it.

This distinguishes a standard from two things it is often confused with. It is not a law, because no state enforces it directly. And it is not a product, because no company owns it. A standard sits in a peculiar middle ground – it is something that belongs to everyone and to no one, maintained by institutions whose only task is to keep it coherent and accessible. The metric system is a standard. So is the size of a sheet of A4 paper, the shape of a stop sign, the gauge of a railway track, the dimensions of a shipping container. None of these things were inevitable. Each of them was once contested, and each of them was resolved not by conquest but by convention.

A civic act, not a technical one

It is tempting to treat standards as a matter for engineers. They are not. Or rather, they are only incidentally so. The engineering is the easy part. The hard part is the decision that the rules of a shared space should not belong to any single actor – that the measurement of length, the width of a road, the voltage in a socket should be held in common rather than owned.

The history of standards is, almost without exception, a history of fragmentation followed by painful consolidation. In the nineteenth century, European railways had dozens of incompatible track gauges, because each company built its own. Goods had to be unloaded and reloaded at every border, and sometimes at every regional boundary. The loss was enormous, and it was eventually resolved not because engineers invented a better track but because societies decided that the common good of interoperability was worth more than the private advantage of incompatibility. The same story repeats with screw threads, with time zones, with paper sizes, with electrical systems. Each consolidation was a political act dressed in technical clothing.

When we say a standard is public, then, we are saying something quite radical. We are saying that a certain category of rules – the ones that govern how we connect to each other – must be held outside the market, because if the market owns them, the market can charge rent on the simple act of cooperation.

What standards give us

From the point of view of the person who uses them – which is to say, all of us, every day – open standards provide three things that are easy to take for granted until they are gone.

The first is interchangeability. Because the rules are public, anyone can build to them. If the lamp you bought five years ago breaks, you can replace the bulb with one from any manufacturer. If your supplier raises prices unreasonably, you can switch to another. If a company goes out of business, its customers are not stranded. You are not captured by the choices you made in the past, because the choices were made against a common framework rather than inside a private one.

The second is continuity. What works today will still work tomorrow, and what was made yesterday still works today. This is a quieter gift, but it may be the most important one. A standard that is public and stable means that your past remains legible to you. The documents you wrote twenty years ago, the tools your grandfather used, the measurements recorded in an old building plan – all of these remain available, because the rules that governed them are still available. Continuity is how a society talks to itself across time. It is how we remain connected to what we have done and what has been done for us.

The third is shared ground. Standards let people who have made different choices still cooperate. You and I do not need to use the same brand, the same supplier, the same tool. We only need to agree on the interface between us. A standard is, in this sense, a kind of peace treaty – a recognition that a common format for exchange matters more than uniformity of preference. It is the opposite of a monoculture. It is the condition that makes plurality possible without chaos.

When the rules become private property

Now consider what happens when the rules of a shared space are privately owned.

Imagine that the thread on every screw in your country belonged to a single company, and that using a screw at all required permission from that company. Imagine that the gauge of the railway tracks was the property of one firm, and that every other operator had to pay to run trains on lines they did not own. Imagine that the voltage of the electrical grid was licensed, and that plugs from any other manufacturer simply did not fit.

The three goods we just described begin to erode. Interchangeability disappears, because you cannot replace one part with another without the owner’s permission. Continuity depends on the corporate survival of a single actor: if the company changes its terms, raises its prices, or goes bankrupt, you lose access not just to a product but to the entire category of things that depended on it. Shared ground shrinks until it includes only the people who have paid the same licence as you have. Cooperation becomes a privilege extended by a third party, rather than a right held between equals.

This sounds absurd when we imagine it happening to physical infrastructure. We would never accept it for screws or rails or electricity. And yet the history of standards is also the history of attempts to do exactly this, resisted successfully in some domains and less successfully in others. The reason we have open standards for physical infrastructure is not that anyone thought them obviously good. It is that societies fought, sometimes for decades, to keep them out of private hands.

The ancestor question

There is a useful way to think about all of this, which is to ask what kind of ancestor we want to be.

Every time we accept an open standard, we are making a small bet on behalf of people who do not yet exist. We are saying that the thing we are building – the document, the product, the system – should remain accessible to them, even though we will not be here to help them open it. We are choosing to be hospitable to a future we cannot see. And every time we accept a closed one, we are making the opposite bet. We are saying that our successors will have to rely on the continued goodwill of a private actor to reach back to what we have made. We are outsourcing their access to our own lives.

This is not a technical question. It is a civic one, and it is also a moral one. Standards are how a society decides whether its own infrastructure should be owned or shared, whether its past should be accessible or licensed, whether its future should be open or gated. They look like engineering. They are really a quiet, continuous answer to the question of what we owe each other, and what we owe to those who come after us.

So the next time you plug something into a wall and it simply works – the next time a door handle fits, a page prints cleanly, a part slots into place without thought – consider for a moment what had to be true for that to happen. Consider who refused to own it. And ask yourself what kind of ancestor a closed standard lets you be.

Policy and Digital Sovereignty – TDF Annual Report 2025

TDF Annual Report 2025 banner

This is part of the Annual Report 2025 from The Document Foundation, the non-profit that coordinates the LibreOffice project and community.

Across the reporting period, the public conversation about office software and document formats shifted decisively. The justification for moving away from proprietary suites is no longer framed primarily as cost saving. It is framed as the preservation of independence — the ability of a government to act without asking permission from a foreign supplier. Several of the year’s migrations were announced with that argument stated explicitly and the cost argument set aside; the Austrian Armed Forces went so far as to say the move was not about money at all.

This reframing matters for The Document Foundation, because it moves the debate onto ground where the Foundation has argued for two decades. Digital sovereignty is the ability of nations, organisations and individuals to control their own digital destiny: to control access to their own information without depending on third parties, to make technological choices based on their own needs rather than a vendor’s commercial strategy, and to preserve that self-determination as the market consolidates. When public bodies store their documents in proprietary formats controlled by a single company, they surrender part of that sovereignty.

A standard in name only

The year also clarified a distinction the foundation has long insisted on: sovereignty is not delivered by any single layer of the technology stack. It requires an open standard format at the base, an open source application above it, open source infrastructure for data location, and a legislative framework that defines the requirements. A law favouring open source, an open cloud, and an open suite together still leave sovereignty incomplete if the document format itself remains under one vendor’s control. The format is the foundation of the stack, and it is the layer most often overlooked.

The year’s central policy development was Germany’s formal commitment to ODF, a decision whose full weight became apparent only as it moved from principle toward binding implementation.

Germany’s IT Planning Council commits to ODF (April 2025)

In April 2025, Germany’s IT Planning Council — a seventeen-member body representing the federal government and the state governments — committed to moving public administration to the Open Document Format, with the stated aim of making ODF the standard for document exchange by 2027. The Council framed open formats and open interfaces as a necessary building block of public-sector transformation toward digital sovereignty, and commissioned its Standardization Board to implement the decision. The commitment set a clear trajectory: a federal-level decision, binding on the implementing board, with a 2027 target for ODF as the standard for document exchange. Its translation into concrete, enforceable infrastructure standards was expected to follow — and the early signs as the year closed pointed toward exactly that outcome.

ODF v1.4 approved as an OASIS Standard (December 2025)

ODF logo

On 3 December 2025, OASIS Open approved ODF v1.4 as an OASIS Standard — the organisation’s highest level of ratification — coinciding with the twentieth anniversary of ODF’s original adoption as an OASIS Standard. The new version maintains full backward compatibility while improving accessibility support (assistive technologies, decorative-object marking), professional formatting and visual design, and features for data analysis and technical documentation. It remains an XML-based, vendor-neutral, royalty-free format. Earlier ODF versions are published as ISO/IEC 26300; the four-part v1.4 specification is available in the OASIS library.

Twentieth anniversary of ODF standardisation

The year carried the twentieth-anniversary thread throughout: ODF’s adoption as an OASIS Standard in 2005, and its ISO/IEC standardisation on 3 May 2006. The ODF v1.4 ratification in December 2025 was deliberately timed to the OASIS anniversary. The anniversary is not merely commemorative: it underpins the argument that ODF is the only open standard for office documents with a twenty-year record governments can rely on for long-term archival access.

Open Document Format Campaign and Document Freedom Day

The Foundation ran a sustained ODF communications campaign through the year, built around a regular series of articles on the TDF blog. Rather than isolated announcements, the series formed a coherent body of work that moved from the fundamentals — what ODF is and why it matters — through technical and practical material on file types, compliance and interoperability, the differences between ODF and proprietary formats, migration guidance, and the new features of recent ODF versions, and on to the wider argument connecting open document standards to digital sovereignty. Taken together, the series gave the Foundation a standing reference resource and a consistent public voice on the format throughout the year.

Document Freedom Day was marked as a purely advocacy-driven occasion: blog posts, social media activity across the Foundation’s channels, and small local events organised by community members around the world. The emphasis was on awareness and outreach rather than on any single flagship event.

Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

Public Administrations Migrating to LibreOffice/ODF During the Year

The following migrations were publicly reported and verifiably advanced during 2025. Status reflects what the cited primary or most reliable source actually supports. Long-standing legacy deployments are deliberately excluded; this list is reserved for movement during the year, and only entries with solid sourcing are included. Figures and completion claims should be confirmed against TDF records before publication.

Schleswig-Holstein (Germany) — confirmed, substantially advanced

Schleswig-Holstein logo

By early December 2025, the northern German state reported that close to 80% of administrative workstations outside the tax administration were running LibreOffice as the binding standard, with Microsoft Office and Outlook either already uninstalled or in the process of removal, and a new-licensing rate already well below 10%. The state reported licence-cost savings already exceeding €15 million, against a one-time 2026 migration investment of €9 million. The remaining ~20% of workstations depend on specialist applications with technical ties to Microsoft formats; migration paths for these, and for the tax administration, have been defined. In parallel, the state completed the migration of more than 40,000 mailboxes (over 100 million messages and calendar items) off Exchange/Outlook to Open-Xchange and Mozilla Thunderbird, with the cutover finishing 2 October 2025.

Austrian Armed Forces / Bundesheer — confirmed, completed in 2025

Bundesheer logo

The Austrian military migrated approximately 16,000 workstations across all branches from Microsoft Office to LibreOffice, with the project finalised in 2025 and Microsoft Office 2016 removed from all machines (Office 2024 LTSC retained only under special permission for legacy macro/Access cases). The Directorate 6 (ICT & Cyber) stated the primary driver was digital sovereignty and in-house data processing, explicitly not licence savings. The Bundesheer contributed more than five person-years of upstream development back to the LibreOffice project; the migration was presented at the LibreOffice Conference 2025 in Budapest.

Denmark — Ministry of Digital Affairs — confirmed, phased, in progress

The Danish Ministry of Digital Affairs committed to replacing Microsoft 365/Office with LibreOffice, beginning July 2025 with a phased rollout (roughly half of staff in the summer, the remainder by autumn). For accuracy: earlier reporting that Denmark would abandon Windows for Linux entirely was subsequently corrected — Windows remains in use on many devices; the confirmed change is the office-suite migration. Several municipalities, including Copenhagen and Aarhus, were reported to be pursuing similar moves.

Threats to ODF Adoption and Digital Sovereignty

The year’s gains were real, but they sit alongside structural threats. The central risk is that the open-source application migrations succeed while the open format battle is quietly lost — that lock-in survives the move by relocating from the application to the document.

Format sovereignty as the overlooked layer

An office suite that does not use ODF as its native format handles ODF files imperfectly, which re-creates interoperability problems and pushes users back toward the proprietary format “for convenience.” A government can therefore adopt an open suite and an open cloud and still fail to achieve sovereignty if its documents remain in a format controlled by a single vendor. The format is the base of the stack; without it, every layer above is compromised.

The “ISO standard format” sleight of hand

When a public administration is told its documents are stored in “an ISO standard format,” the reasonable assumption is genuine openness. OOXML Transitional does not deliver it: its stacked dependencies — format, rendering and fonts — re-encode failure at each layer. A format named as a standard while defined by its own specification as provisional is the principal rhetorical obstacle to ODF adoption, and the principal target of the Foundation’s three-strand evidence work.

Initiatives that default to OOXML under a sovereignty banner

A specific and growing risk is the European sovereignty initiative that adopts open source applications and open infrastructure while defaulting to OOXML rather than ODF as its native document format. Such an arrangement re-encodes the dependency at the format layer even as it presents independence at every other layer. This is the precise failure mode Section 4.5 describes, and it gives the Foundation’s insistence on a native open format its practical
urgency.

Political reversibility

Sovereignty gains are reversible without durable policy commitment. Munich’s LiMux reversal remains the cautionary precedent, and the year offered a live counter-signal: even as Schleswig-Holstein advanced, Bavaria was reported to be pursuing a major Microsoft 365 contract. This is why a binding federal commitment to ODF, of the kind Germany set in motion in 2025, matters: it raises the cost of reversal. But commitments depend on sustained political will to carry them into enforceable practice.

Like what we do? Support the LibreOffice project and The Document Foundation – make a donation, or get involved and help our volunteers. Thank you!

The non technical dependency layers: the Calendar and the Invoice

Earlier in this series I described the invisible architecture of lock-in as three stacked layers. A document depends on its format, which depends on a rendering engine to become visible, which depends on the fonts that give it its final shape. Each layer is a dependency the user rarely sees and almost never chooses deliberately, and together they explain why “just open it in something else” so often fails. The argument has always been structural rather than moral: it does not matter whether the vendor is benevolent or predatory, because the dependency exists either way.

Two pieces of news from late June give me occasion to extend that architecture. They are not, at first glance, about formats at all. But read structurally, they reveal two further layers of dependency that sit on top of the technical ones. Layers I left implicit until now because the technical case was enough to make the point. It is worth making them explicit, because they complete the account of what dependency actually means.

The first piece of news: Microsoft has extended free security updates for Windows 10 by a further year, to October 2027. The original end date for consumer support was October 2026. Hundreds of millions of users, and the institutions that manage them, had organised their procurement, their budgets, and their migration planning around that date. Then the date moved, quietly, through an editor’s note appended to a blog post, with no formal announcement.

The second: Italy’s competition authority, the AGCM, has opened an investigation into whether Microsoft adequately informed consumers when it integrated its Copilot and Designer AI tools into Microsoft 365 and moved subscribers onto more expensive plans. The allegation, still under investigation, concerns transparency and consent: whether users were given a genuine choice, or were migrated to a costlier tier unless they actively opted out.

I want to be careful here, because the temptation is to treat these as two instances of the same thing, and they are not. They are two sides of one coin. A coin has two faces and a single substance. The substance, in both cases, is that the user is not in control of his desktop stack. The faces are different, and naming them precisely is what gives the argument its force.

The temporal layer

The Windows 10 extension is not, on its surface, bad news. A further year of free security updates is, taken in isolation, a gift to users who cannot or will not upgrade. If you read the story as a tale of corporate character – Microsoft breaking its word, Microsoft flip-flopping – you reach for the weakest version of the argument, and you hand a critic the easy reply that extending support is pro-consumer.

The structural reading is harder to answer. The point is not that the date was wrong, or that moving it was wrong. The point is that the date was never yours. The lifecycle of your own desktop – when it is supported, when it is abandoned, when you must spend money on new hardware – is governed by a vendor’s strategic calendar, not by your operational needs. You reorganised a year of planning around October 2026 because Microsoft told you to, and you will reorganise again around October 2027 for the same reason. A benevolent vendor moving the date without consulting you proves the point exactly as well as a cynical one would. You do not own the clock.

This is the fourth layer. Above format, rendering, and fonts sits time. Your dependency is not only in the file, it is in the calendar.

There is a detail in this story that sharpens the point rather than softening it. The free extension is not unconditional: to enrol without paying, a user must sign in with a Microsoft account and sync settings to the company’s cloud. So the price of keeping your old operating system alive is to move more of yourself into the vendor’s stack. The remedy deepens the dependency it claims to relieve. This is the difference, which I have written about before, between a solution and a substitution. A solution would reduce your dependence. A substitution merely relocates it from the operating system to the account.

The commercial layer

The Italian investigation looks, at first, like a different kind of story altogether: a matter of consumer-protection law, of disclosure and dark patterns, with no obvious connection to open standards. And it would be a mistake to press it into service as evidence of format lock-in, because that is not what it is about. The discipline of letting structure carry the argument requires resisting exactly that kind of stretch.

But it illustrates a different layer cleanly, and the layer is real. When your productivity suite is a proprietary bundle, the vendor can change what you are paying for, and how much, without your meaningful consent. New tools you did not ask for are folded into the package, the price rises to match, and the path to opting out is, allegedly, buried. Whether the AGCM ultimately finds against Microsoft is not the point I am making, as the investigation may take until 2027 to conclude. The point is that the arrangement permits this. The economic terms of your daily work are set by a party that is not you, and can be revised by that party at a moment of its choosing.

This is the fifth layer. Above format, rendering, fonts, and time sits price. Your dependency is in the invoice as much as in the file.

What the layers have in common

Five layers, then: format, rendering, fonts, time, price. The first three are technical and largely invisible. The last two are not technical at all, and they are the ones the user feels most directly, in a migration deadline he did not set, in a subscription cost he did not agree to. Listing them together changes the character of the argument. Lock-in is no longer a catalogue of technical grievances of interest mainly to specialists. It is a complete account of dependency, and it reaches every part of how a person works: what his documents are made of, when his tools will stop being supported, and what he will be charged for them.

What unites all five is a single absence: the user has no exit. He cannot take his documents elsewhere without loss because of the technical layers, he cannot escape the vendor’s calendar or its pricing because of the other two. Every one of these dependencies is only possible because there is no door.

That is why I have spent this series on formats, and on rendering, and on fonts, and now on calendars and invoices. They are not separate complaints. They are the same observation seen from different angles, and the observation is this: an open format and a free application are not, in the first instance, about cost or ideology. They are an exit, they are the door that makes every one of these dependencies optional rather than fixed. The Open Document Format and LibreOffice do not promise that you will never depend on anyone. They promise something narrower and more important: the dependency is one you have chosen, and one you can leave.

A vendor’s calendar will always move. A vendor’s prices will always rise. These are not scandals, they are simply what it means to be governed by someone else’s strategy. The only question that matters is whether you are free to walk away when they do. Everything in this series has been an argument that you should arrange your affairs so that you can.

Images by Manfred Steger from Pixabay

LibreOffice project and community recap: June 2026

Monthly recap banner

Here’s our summary of updates, events and activities in the LibreOffice project in the last four weeks – click the links to learn more…

LibreOffice 26.2 banner

Format Sovereignty banner

  • Our marketing and design communities worked on a new video: Join the LibreOffice Community! (This video is also available on PeerTube.)

Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

Annual Report banner, with LibreOffice community group photo

Guidebook cover

Like what we do? Support LibreOffice with a donation – or join our community and help to make LibreOffice even better! Also keep in touch – follow us on Mastodon, Bluesky, Reddit and Facebook.