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 project and community recap: October 2026

Monthly recap banner

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

  • We announced LibreOffice 26.8.1, with around 40 bug fixes focused on compatibility with Microsoft Office files, along with more reliable text and CSV import across a range of character encodings.

LibreOffice 26.8 banner

  • In our Community Member Monday interview, Adlair Cerecedo-Méndez described how he helped Mexico to develop Office GOBMX, a LibreOffice-based suite for public institutions, and shared lessons about migration, training and digital sovereignty.

Adlair Cerecedo-Méndez

  • At LinuxDays in Prague, Mike Saunders gave a talk on where LibreOffice is going, including the project’s September download figures and current direction.

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.

  • The QA community published its QA/Dev Report for September, covering contributions across LibreOffice, bug reports and fixes, and work by testers and developers.

Chart showing resolution of bugs

  • Our latest State of the Project slide deck looked at October 2025 to September 2026: 297 developers contributed 11,676 commits, alongside data on downloads, donations and community activity.

State of the Project banner

The Document Foundation's new logo

LibreOffice Conference 2026 group photo

LibreOffice migration workshop in Nairobi

Rubber ring

  • A post on the developer blog showed how to connect a Python webview to LibreOffice and use it to send UNO commands, a useful approach for building extension interfaces.

WebUNO connecting a webview to LibreOffice

  • In The Politics of Standards, we looked at how technical standards shape who can participate in an ecosystem and why open, clearly specified standards matter to users and public institutions.

World map of LibreOffice download

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.

LibreOffice community members at a hackathon in Nepal

  • We invited developers and contributors to submit talks for the FOSS Office DevRoom at FOSDEM 2027, covering topics such as interoperability, accessibility, localisation, security and office software development.

LibreOffice at FOSDEM

  • Finally, we released LibreOffice 26.8.2, with around 35 fixes for stability, multimedia playback, legacy file compatibility, Calc and hyphenation.

LibreOffice 26.8 banner

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.

Quick recap of the LibreOffice Conference 2026

A recap of the LibreOffice Conference 2026, which took place in September in Pordenone, northern Italy. Thanks to the local team for organising the 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.

LibreOffice Conference 2026 group photo – and final video updates

LibreOffice Conference 2026 group photo

Last month we had the LibreOffice Conference 2026 in Pordenone, northern Italy. Huge thanks to the organisers for such a great event! At lunchtime on the final day we took a group photo, which you can see above – but of course, some people had left by then, so thanks to those people as well for attending 😊

We’ve also finalised the YouTube playlist with 32 talks from the event. For a few talks which had recording issues, we don’t have videos of them, but the volunteer organisers did a great job recording the vast majority of talks.

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.

The videos are also available on the Pordenone LUG’s PeerTube channel.

Now we’re looking ahead to the VII Latin American Congress of LibreOffice, and FOSDEM. We hope to see you there!

Community Member Monday: Adlair Cerecedo-Méndez

Adlair Cerecedo-Méndez

( Note: this is a translation of an article on the Spanish-language blog)

For Adlair Cerecedo-Méndez, his work with LibreOffice began as a response to a specific need: helping the Mexican government obtain an office suite tailored to public institutions. Over time, that technical work also became an experience in collaborating with the international LibreOffice community and an opportunity to promote free software in the public sector.

Although Adlair had already been using LibreOffice since the OpenOffice days, his professional involvement with the project took shape around 2020, when he was invited to collaborate on the development of a government office suite. The initiative was part of a broader vision: reducing dependence on proprietary solutions, making use of free software, and strengthening the state’s own technological capabilities.

Building on an existing platform

Office GOBMX did not necessarily start out based on LibreOffice. At first, the possibility of creating a suite from scratch was considered, but the technical analysis revealed the scale of the challenge: developing, maintaining, and evolving an application of that kind would require considerable time and resources.

LibreOffice offered a mature, cross-platform, open-source foundation backed by an international community. Adapting it to government needs made more sense than reinventing an entire office suite. That was how the Office GOBMX approach was born: starting with existing technology and adapting it to the needs of public institutions.

The goal included reducing licensing costs, but it also involved moving toward greater technological autonomy. For Adlair, sovereignty does not mean switching tools overnight. It is a gradual process that allows the state to decide which technologies it uses, understand them, modify them, and maintain them with its own expertise.

Migration is also a human process

Implementation brought challenges involving compatibility with documents, macros, formats, and processes that had been built over many years around other tools. It was also necessary to determine what could work as-is and what required adaptation or reimplementation.

But the greatest challenge, Adlair recalls, was resistance to change. Office tools are part of many people’s daily routines, and a migration can disrupt familiar habits and procedures. That is why simply installing software is not enough: it is necessary to analyze processes, test compatibility, migrate documents, train users, and provide guidance and support.

Coexistence with Microsoft Office was also part of the transition. In public administration, documents circulate among government institutions, citizens, businesses, and vendors. Although LibreOffice provides interoperability with widely used formats, some complex documents, templates, and macros require special attention. The strategy, Adlair explains, must be gradual: promote open formats such as ODF without disrupting work or losing the ability to exchange files with the existing ecosystem.

Adapt, Audit, and Learn

Open-source software made it possible to develop components for specific institutional needs. One example is a document validator created to analyze internal elements in files generated with Microsoft tools and obtain technical evidence about the information they contained. In a government context, Adlair points out, it is important to understand those elements before assuming they are irrelevant or have no implications.

The ability to work with the code was also valuable when dealing with legacy processes, such as old macros and workflows associated with Microsoft Access. Rather than accepting the limitations of a closed tool as unavoidable, the team was able to address those cases from an adaptation and migration perspective.

At the same time, the Office GOBMX experience offers lessons that may be useful to other public administrations. Although each government has different needs, many of the challenges are recurring: technological dependence, legacy documents, interoperability, training, and resistance to change. The methodology—from planning and compatibility analysis to implementation and ongoing support—can provide a useful reference.

From Technical Experience to Community

Adlair’s relationship with the international LibreOffice community grew stronger in 2023, when he attended the Latin American LibreOffice Conference in Mexico City. There, he met members of the community and gained a closer understanding not only of the software, but also of the collaboration that sustains it.

From his perspective as a member of The Document Foundation, that connection is especially valuable: people who implement LibreOffice in government environments can share real-world cases, interoperability needs, and lessons learned from large-scale deployments. In turn, the community provides expertise and a shared space for contributing to the project’s development.

For Adlair, continued compatibility with Microsoft Office documents will remain important—not as a goal of permanent dependence, but as a way to lower the barriers to adoption. Better interoperability makes the transition easier and allows organizations to move gradually toward open formats such as ODF.

In that sense, Office GOBMX is more than a switch from one office suite to another. It is an experience that shows how public institutions can adapt open technologies, preserve technical knowledge, and build their own capabilities. Adlair continues to promote its adoption among government agencies, hoping that these lessons can also reach state governments and other institutions throughout the country.