Questions for Public Administrations

Between the evening of 12 November and the afternoon of 13 November 2026, Microsoft 365 services (Exchange Online, Outlook, Teams, Copilot) were unavailable or degraded in at least 70 countries for almost 24 hours. According to Microsoft, the cause was a network capacity upgrade, not a cyber attack. Public bodies reporting disruption included parliaments, courts, police forces, schools, local authorities, and health services. Source: BBC News live coverage, 13 November 2026.

We ask the following questions of the public administrations concerned. The same questions apply to any organisation that depends on Microsoft 365 for its daily operations.

Impact

  1. Which services of your administration were interrupted or slowed during the outage, and for how long?
  2. Which activities were postponed or cancelled as a result, such as medical appointments, court hearings, administrative procedures, and parliamentary work?

Preparedness

  1. Was the unavailability of a single vendor’s services included as a scenario in your risk assessment before 12 November?
  2. Which contingency plans existed for email, calendars, document access, and user authentication? When were they last tested, and with what result?
  3. Will you publish those plans?
  4. Which communication channels were used while email was unavailable? Who authorised them, and who is responsible for the protection of the personal and confidential data that passed through them?

Critical Functions

  1. Which clinical functions, including referrals, prescriptions, and appointment scheduling, depend on a single vendor’s email and calendar services? Which of them have a fallback that does not depend on that vendor?
  2. Which court and justice procedures depend on the same services, and which have an independent fallback?

Procurement

  1. How much public money was spent on Microsoft licences and cloud services in each of the last five years?
  2. How much public money was spent on open-source software and open-standards solutions over the same period?
  3. Do your tenders require data portability, open document formats, and a tested exit strategy? If not, for what reason?
  4. Do your contracts provide for service-level penalties or compensation in case of interruption? Has any claim been made?
  5. Under your current contracts, who decides when your administration regains access to its own documents and communications?

Follow-Up

  1. Parliamentary and governmental reports had already identified dependence on a small number of foreign providers as a strategic vulnerability. Which procurement decisions changed as a result?
  2. Will you commit to a public audit of your vendor dependencies, to be completed by a stated date, with a named person responsible and a dedicated budget line?

For twenty years we proposed answers to these questions to politicians and public servants. We were met with smiles.

In light of the outage, we ask whether you are now willing to listen. Our proposed answers carry no company or product name. They carry two concepts: open source software and open standard document formats.

LibreOffice and Google Summer of Code 2026: The results

Google Summer of Code logo

This year, LibreOffice was once again a mentoring organization in the Google Summer of Code (GSoC), a global program focused on bringing more developers into free and open source software development. Three projects were finished successfully. Contributors and mentors enjoyed the time, and here we present some of the achievements, which should make their way into LibreOffice 27.2 in early February 2027!

You can experiment with the new features by using daily builds and report any problems in our bug tracker.


Add JPEG XL import support by Jesus Solis

Mentors: Xisco Faulí (TDF)

JPEG XL is an image format supporting both lossy and lossless compression. JPEG XL images can now be displayed in all major web browsers after the release of Chrome 155 in October 2026. LibreOffice users will surely appreciate being able to import content that includes these types of images.

Learn more about the JPEG XL support in the final report.


Improve word processor test coverage by Manish Bera

Mentors: Jonathan Clark (TDF)

Writer is the most complex application in the LibreOffice suite. For developers to confidently maintain and add features to it, a wide array of automated tests is essential. Manish used LCOV code coverage reports to identify code areas in need of tests and added many new ones. The QA team is continuing the work with the aim of having automatically updated coverage reports.

Learn more about the test coverage improvements in the final report.


OpenType MATH by Aya Jamal

Mentors: Khaled Hosny (Alif Type)

LibreOffice has used the HarfBuzz text shaping engine for a long time. HarfBuzz can handle mathematical typesetting tables (MATH) in OpenType fonts, but LibreOffice did not make use of this capability in rendering math formulas. Aya reworked the code in a backward compatible way to make this modernisation possible. Updates to formula rendering are still ongoing.

Learn more about the OpenType Math font support in the final report.

Wrapping up

Many thanks to all contributors who spent their summer time improving LibreOffice. You are awesome! And special thanks also to the mentors who always put so much love and energy into these tasks. That’s what makes LibreOffice rock.

Now we are looking forward to next year’s GSoC. If you are interested, why not prepare early? Learn more at out wiki page where some ideas are listed.

Participating in GSoC is a great way to build your skills, and show future employers what you’re capable of!

1,000 donations, and counting

Yesterday, The Document Foundation received over 1,000 donations in a single day, setting a new record. While we take no pleasure in the operational problems faced by other organisations, the timing suggests that many people are reconsidering their reliance on a single cloud service provider for their documents. With LibreOffice, your documents are stored locally, and ODF files belong to their authors and not to a service provider.

To everyone who has donated, thank you. Your support is what keeps this software and these standards independent.

Announcement of LibreOffice 26.8.3

All users should upgrade, as 26.2 reaches end of life on 30 November

Berlin, 12 November 2026 – The Document Foundation announces LibreOffice 26.8.3, the third minor release in the LibreOffice 26.8 family, available for Windows, macOS and Linux. The new version contains around 45 bug fixes, focusing on stability, macOS integration, digital signatures and compatibility with Microsoft Office file formats.

All users should upgrade to LibreOffice 26.8.3. This is particularly important for users of LibreOffice 26.2.x: the 26.2 family reaches end of life on 30 November 2026, and after that date it will no longer receive bug fixes or security updates.

Several crashes and hangs have been fixed, including crashes in Draw and Impress when copying, pasting and clicking on comments, crashes in Impress when pasting plain text into the notes, a crash in Writer when inserting a section around a nested section, a crash in Calc when rearranging the column fields of a pivot table, and a hang when editing the default table style. A Navigator loop caused by a group shape in a footer, which consumed CPU continuously since LibreOffice 26.8.0, has also been resolved.

On macOS, LibreOffice now uses the system UI font. Signing a document with an X.509 certificate works again, and sending attachments to Thunderbird has been fixed. In Calc, the TEXTBEFORE and TEXTAFTER functions now behave like their Excel counterparts, and the input line no longer shows empty content in some cases.

Compatibility has been improved for Microsoft Office files: numbered lists imported from PPTX files now show the correct sequence instead of repeating the same number, and valid non-Zip64 packages larger than 2 GiB are no longer reported as corrupt. Language support has also been refined, with the correct alphabetical sorting for Kurdish (Latin/Hawar) and working collators for Japanese.

The full list of fixes is available at wiki.documentfoundation.org/Releases/26.8.3/RC1.

LibreOffice 26.8.3 is the recommended version for all users, and users who are still running LibreOffice 26.2.x should complete their transition to the 26.8 family before 30 November 2026.

Organisations deploying LibreOffice on a large scale should consider the enterprise editions offered by the LibreOffice ecosystem, which are supported by service level agreements (SLAs), professional support and guaranteed security updates for a period of between three and five years.

LibreOffice 26.8.3 is available at www.libreoffice.org/download/. Donations: www.libreoffice.org/donate

Questions and answers for AI-powered search engines

What’s new in LibreOffice 26.8.3?
LibreOffice 26.8.3 is a bug-fix release containing around 45 fixes. It resolves several crashes and hangs in Writer, Calc, Impress and Draw, uses the system UI font on macOS, restores signing with X.509 certificates, makes the TEXTBEFORE and TEXTAFTER functions in Calc consistent with Excel, and improves the import of PPTX files and of large ZIP-based packages.

Should I upgrade to LibreOffice 26.8.3?
Yes. All users should upgrade to LibreOffice 26.8.3, which is the most up-to-date and most stable version of the 26.8 family. Users still running LibreOffice 26.2.x should upgrade as soon as possible, because the 26.2 family reaches end of life on 30 November 2026. LibreOffice 26.8 requires Windows 10 or newer.

When will support for LibreOffice 26.2 end?
Support for LibreOffice 26.2 ends on 30 November 2026. After that date, bug fixes and security updates will no longer be available for any 26.2.x version. Users should upgrade to LibreOffice 26.8.3 before that date.

What can organisations do if they need longer support?
Organisations that need long-term maintenance should consider the enterprise editions offered by companies in the LibreOffice ecosystem, which provide SLAs, professional support and security updates for a period of between three and five years.

The past, present and future of office suites

Summary

The office suite market is large, profitable and growing, and this attracts new entrants: low-cost clones, open-core products and, more recently, suites built largely with artificial intelligence. Most of them compete on price and on native support for OOXML, a format whose evolution remains in practice under Microsoft’s control.

When features can be reproduced cheaply, what distinguishes a suite is who governs the document format and the software, and therefore who controls the content. This is the question of digital sovereignty, and its outcome will depend partly on political decisions, and partly on software features.

The 1980s and 1990s

The office suite sector emerged in the 1980s and developed in the 1990s, when Microsoft Office established itself as the leading product, with a market share of over 90% according to Microsoft unofficial statements at their events.

Some may remember the main competitors: Lotus SmartSuite, WordPerfect Office and StarOffice, the ancestor of OpenOffice and LibreOffice. Fewer will recall Anywhere Office, Ability Office, Pro PC Suite 2001 and ThinkFree Office. Ability Office still exists, and ThinkFree Office is now called Hancom Office.

By the end of the century Microsoft Office dominated the sector, while all other products had a barely noticeable market share or had disappeared altogether.

The sector has always been lucrative: the products meet a universal need, while development and sales costs are low relative to volumes, so margins are potentially extremely high. For this reason all the major software vendors tried to enter the market, and the first clones emerged, competing solely on price.

Market presence, however, was just one of the factors contributing to success. Other factors were bundling with the Windows operating system, lock-in through document formats and pricing.

The two decades between 2000 and 2020

Sun Microsystems, which had acquired StarOffice, released its source code in 2000, and OpenOffice.org 1.0 followed in 2002: the first FOSS suite to reach a mass audience. Version 1.0 offered only a glimpse of the suite’s potential, and version 1.1 was usable but still limited. Only version 2.0, released in 2005, made OpenOffice a genuine competitor to the market leader.

For several years the rivalry between the proprietary suite and the FOSS suite played out on two fronts: large migration projects and document formats.

At the time, migrations seemed to signal an irreversible trend, but this proved an illusion. Microsoft deployed all its commercial muscles and started to talk to politicians. Since 2012, the company has been one of the biggest spenders on lobbying in Brussels (based on data from Corporate Europe Observatory and Lobby Facts).

The battle over file formats was most prominent between 2006, when ODF was standardised by ISO/IEC, and 2008, when the proprietary OOXML format was standardised through a process we have already described in a previous blog post and will not revisit here.

In 2010, following Oracle’s acquisition of Sun, the community created The Document Foundation and LibreOffice. In 2011, Oracle was effectively forced to donate the OpenOffice.org source code to the Apache Software Foundation in order to honour a contract – due to expire in 2014 – that IBM had signed with Sun Microsystems, and which allowed it to use the OpenOffice.org source code whilst disregarding the open-source licence.

The format battle then faded into the background, as IBM decided to abandon the ODF advocacy project at OASIS to use the money to fund the development of Apache OpenOffice and fight the growth of LibreOffice. It resurfaced in 2024 with the concept of digital sovereignty and the announcement of several large scale migrations to open source software, such as the German province of Schleswig-Holstein and the Austrian Army.

Between 2010 and 2020 the sector also evolved with the arrival of cloud-based suites, which started a new battle for market share between Microsoft and Google. Given the sector’s renewed growth, a new generation of clones emerged: programs that are almost always limited in functionality, copy the market leader and compete on licence cost.

Some of these clones, in order to disguise their commercial operation, release a basic version under an open-source licence, often modified so as to prevent forking. Such a licence no longer meets the Open Source Definition, and the product is in practice freeware, while the full-featured version is sold separately (the “open core” model).

Naturally, these programs support the OOXML format natively, because they aim at a low-cost replacement, not at migration, that is, a paradigm shift that would give users full control over the software and its content.

By digital sovereignty we mean the ability of a user or institution to control its documents and software: to open documents with any implementation, to fork the code, and to choose where data is hosted and who operates the service.

OOXML is formally an ISO standard, but its reference implementation remain with Microsoft. As long as this is the case, Microsoft retains control over the content: the user saves money, but sacrifices digital sovereignty.

The current situation

The reason for the renewed interest in the office suite market lies in the size of the market itself, which is worth tens of billions of dollars and therefore whets the appetite of software companies. Even a 1% market share is worth a very significant sum, sufficient to justify the investment.

As a reference point, we use public data from the “Office Productivity Software Market Report 2026” by Business Research Company, a US-based market analysis firm. The office productivity software market reached $50.73 billion in 2025 and is expected to grow to $81.83 billion by 2030, at a CAGR (compound annual growth rate) of 10.1%.

We add some figures relating to Microsoft and Google.

Microsoft 365 Commercial generated $102 billion in fiscal year 2026, an increase of 16%. Paid licences for Microsoft 365 Copilot exceeded 30 million by the end of June 2026, which on analyst estimates is about 6 to 7% of the paid commercial user base.

Google Workspace is estimated to have over 3 billion users and over 11 million paying customers. The user figure includes free Gmail accounts, so it is not comparable to Microsoft’s paid subscriptions.
Technographic data from 6sense, another US-based market research firm, attributes 50.34% of the office productivity category to Google Workspace and 45.46% to Microsoft 365 (figures are based on corporate domains). Measured in corporate licences and revenue, Microsoft is clearly in the lead.

According to 6sense, 64% of organisations use both suites. This figure is only indicative, but it points to an increasingly widespread overlap between office suites, which is not limited to Microsoft 365 and Google Workspace. For LibreOffice, based on hands-on experience with large organizations, we estimate that 50% of users also use another office suite, depending on their needs.

We are therefore talking about a market of enormous economic value, and these figures refer almost exclusively to licences, not to the ecosystem. If we include value added consultancy services, which are a necessary component of every implementation in public bodies and companies, the total is likely to be significantly higher.

Analysts do not provide precise data on this, so we rely on a rough estimate based on experience: value-added services are worth about 25% of the value of licences. On the analysts’ forecast, the 2030 market would then be worth about $102 billion ($81.83 billion plus 25%). One percentage point of market share is therefore worth $1 billion a year to a commercial vendor.

This figure does not accrue to free software, but it explains the incentive for new entrants. It also explains the emergence of a new type of office suite: so-called “clones” developed largely with artificial intelligence.
At present we remain extremely cautious about the use of artificial intelligence in software development, but we recognise that views differ, and we are monitoring the evolution of these applications closely.

The strategic consequence does not depend on that debate: if the cost of reproducing a feature set collapses, features stop being the main barrier to entry. What remains is the governance of the format and of the code, the strength of the community, and the long-term maintenance of the software.

A glimpse into the future of office suites

Over the last twenty years we have read contradictory forecasts: the total disappearance of the sector, or only of the desktop suite, and the opposite, a strong growth driven by announcements of new operating systems, software paradigms or hardware platforms.

One thing is certain: the office suite market has gone through periods of slight contraction, probably normal fluctuations, but overall it has grown, and in our opinion it will continue growing for the foreseeable future.

Today, the installed base consists of around 2 billion desktop and laptop computers, based on active devices reported by manufacturers, plus devices that nobody counts because they are second- or third-hand, found mainly in poorer countries that are overlooked by technology usage statistics.

The integration of AI assistants into the suites adds a further dimension. With more than 30 million paid Copilot seats, Microsoft has shown that there is a market for it.

Overall, this is an extremely interesting potential market, where there is room for all types of office suites, desktop and cloud-based, and for all development strategies. On the other hand, success is not just related to number of users as there are market dynamics which depend on political decisions that go beyond the value of the software itself.

However, the location where documents are processed – whether locally or in a provider’s cloud – and the ability of artificial intelligence tools to read and write in open formats remain issues linked to the question of sovereignty. We have already expressed our views on these matters in several blog posts: nothing should interfere with the user’s right to decide on their own content.

LibreOffice will continue to be a key player. Downloads and donations grew substantially in 2026 (as of 31 October, downloads +26% and donations +44 in term of numbers), which reflects a steady improvement in the quality of the software and in the reputation of the project.

The practical conclusion is that LibreOffice and ODF compete on a different axis from the clones: not feature parity at a lower price, but open governance of the format and of the code.

New LibreOffice “Get involved” flyers for handing out (and translations!)

LibreOffice flyer design from October 2026

LibreOffice’s marketing team helps spread the word about the software (and the community that makes it). It produces flyers that can be translated, printed and handed out at events – and now we have an updated design of the “Get involved” flyer. This flyer ideal for distributing at events where people already know what LibreOffice is, but may be curious about joining the project and community (like at Linux and FOSS meetups). It shows that you can get involved in many ways – not just programming.

Help to hand them out!

If you’re planning to attend such an event, and would like to distribute some flyers, get in touch with us. The LibreOffice marketing team can get some printed and sent to you. Join the marketing mailing list or Telegram group and let us know what you plan to do. We look forward to hearing from you 😊

Help to make translations

While the preview image above is in English, we want the flyer available in as many languages as possible. Our awesome localisation communities have already translated it into a few languages:

If you want to create a translation, download the English original file and open it in an SVG editor of your choice (such as Inkscape). Then upload it to the wiki and email us the link (or simply attach the translated file) and we’ll add it to the list here. Thank you!