Tall stacks of paper files and folders crowd a desk in an office under fluorescent ceiling lights.

Office Online Server end of support: what to do by 31 December

Office Online Server end of support is 31 December 2026: SharePoint Server keeps running, but browser editing loses support. The options and a dated plan.

In short

  • Microsoft ends support for Office Online Server on 31 December 2026: from then, it says, OOS gets no security updates, bug fixes or technical support, and it names no on-premises successor for browser editing.
  • Microsoft will not block Office Online Server in SharePoint Server after 31 December 2026, but it will not be supported in any configuration, even beside SharePoint Server Subscription Edition.
  • For documents that stay on SharePoint Server, Microsoft points to desktop editing with Microsoft 365 Apps or Office LTSC 2024, whose mainstream support ends on 9 October 2029 with no extended phase.
  • Nextcloud with Collabora Online keeps browser editing of Word, Excel and PowerPoint files on your own servers; complex layouts, missing fonts and macros need testing with real documents first.
On this page (8)

Office Online Server end of support is on 31 December 2026: Microsoft announced on 21 October 2025 that from then, Office Online Server (OOS) “will no longer receive security updates, bug fixes, or technical support”. OOS is the server that lets SharePoint Server users view and edit Word, Excel and PowerPoint documents in the browser. Microsoft will not block it in SharePoint Server, but from 1 January 2027 it is unsupported in every configuration, with no security updates promised, and Microsoft’s recommended path is Microsoft 365, which does not suit documents that must stay on your own servers.

As of 9 November 2026, 52 days remain to choose between the cloud, desktop-only editing and a browser editor on your own servers. This post covers what ends, which farms it affects, Microsoft’s alternatives, the unofficial 2028 date, the options and a dated plan.

What ends with Office Online Server end of support?

Microsoft’s lifecycle page for OOS lists the retirement as 1/1/2027 6:59:59 AM Pacific Time, which is how its lifecycle pages mark the end of 31 December 2026.

The SharePoint team’s post of 12 November 2025 sets out what that means for SharePoint Server:

  • Browser editing. “Users will lose the ability to view, edit, and collaborate on Office documents directly in the browser.” Office client applications “can still be used”.
  • Previews. SharePoint Server relies on OOS for previews of Word, Excel, PowerPoint and PDF documents, and “these thumbnails will no longer be actively supported in libraries and search results.”
  • Every configuration. OOS “will not be supported in any configuration after retirement, including scenarios where it is paired with SharePoint Server Subscription Edition.”
  • Nothing is switched off. “Microsoft will not actively block the use of OOS in SharePoint Server after its retirement. However, no further updates will be provided, including security updates.”

What changes for SharePoint Server on 1 January 2027

Unsupported from 1 January 2027

  • Viewing, editing and co-authoring in the browser through OOS
  • Previews of Word, Excel, PowerPoint and PDF files in libraries and search

Still supported

  • SharePoint Server Subscription Edition, until at least 31 December 2035
  • Microsoft 365 Apps for Enterprise and Office LTSC 2024 as desktop clients

What stops is the patching, and OOS has needed it regularly. Microsoft published an OOS security update every month from July to October 2026, and the update of 13 October 2026 lists 40 CVEs, for Excel remote code execution and information disclosure vulnerabilities. From 1 January 2027, Microsoft promises no fix for flaws of that kind.

Which SharePoint Server farms are affected, and when?

Every farm that uses OOS, though some are already past support. SharePoint Server 2019 and SharePoint Server 2016 left extended support on 14 July 2026, so a farm on either is already unsupported. A farm on SharePoint Server Subscription Edition is the new case: the server is supported until at least 31 December 2035, its browser editing only until 31 December 2026.

Two dates sit beside it. Office LTSC 2021 left support on 13 October 2026, so users who fall back on the desktop need a newer Office. And an OOS server on Windows Server 2016 loses its operating system’s extended support on 12 January 2027.

Power BI Report Server goes first: its documentation says users “will no longer be able to host Excel workbooks in PBIRS using OOS after November 2026”.

Office Online Server and the dates around it

  1. 21 October 2025: Microsoft announces the retirement of Office Online Server.
  2. 12 November 2025: The SharePoint team says OOS will not be blocked, nor supported in any configuration.
  3. 14 July 2026: SharePoint Server 2016 and 2019 leave extended support.
  4. 13 October 2026: Office LTSC 2021 leaves support.
  5. 31 December 2026: Office Online Server end of support.
  6. 12 January 2027: Windows Server 2016 leaves extended support.
  7. 9 October 2029: Office LTSC 2024 leaves mainstream support, with no extended phase.
  8. 31 December 2035: SharePoint Server Subscription Edition is supported until at least this date.
Dates from Microsoft’s posts and lifecycle pages, end dates read as the last day of support.

What does Microsoft recommend instead?

The retirement post gives one path: “our recommended path is to transition to Microsoft 365”. The browser options it names, Office for the Web and SharePoint Embedded, both run in Microsoft 365, and it names no on-premises successor for browser editing.

For organisations that stay on SharePoint Server Subscription Edition, the post says “Microsoft 365 Apps for Enterprise and Office LTSC 2024 remain supported desktop clients for viewing and editing documents hosted on those servers.” Office LTSC 2024 is the perpetual version, and its lifecycle page shows mainstream support to 9 October 2029 and no extended phase. Microsoft’s partner notice on the end of Office LTSC 2021 presents it as the exception: “In cases where regulatory, connectivity, or technological constraints prevent the use of cloud solutions, customers might consider the latest supported on-premises alternatives, including Office LTSC 2024”.

Desktop-only editing keeps documents on your servers but changes the work: every document opens in a local application, every workstation needs a supported Office installation, and co-authoring in the browser ends.

The 2028 date is not a public commitment

On the blog of Stefan Goßner, a Senior Escalation Engineer for SharePoint at Microsoft whose blog says its views do not necessarily reflect Microsoft’s, a commenter quoted on 20 March 2026 an email from their Microsoft account manager: from 1 January 2027, Microsoft “may address security issues at its discretion”, and “The final release date for any potential Office Online Server security update will be December 31, 2028.” Asked on 17 September 2026 whether this was verified, Goßner answered “Yes”, then that “a public statement for this has not been released and there is currently no plan to do so.” Whether it applies to every customer is unclear, and as of 9 November 2026 the lifecycle page still shows the same retirement date. Plan on 31 December 2026.

Why the cloud path does not fit every SharePoint Server farm

Some organisations run SharePoint Server by choice, for data under official or professional secrecy, patient records, confidential research, or sites with no reliable connection.

For Swiss public bodies, the line is written down. privatim, the conference of Swiss data protection commissioners, says in version 3.02 of its cloud fact sheet, dated 2 October 2026, that public bodies outsourcing particularly sensitive personal data, or personal data under a statutory duty of secrecy, to SaaS from large international providers (“wie Microsoft, Google, AWS und SAP”) is “in den meisten Fällen aufgrund des untragbaren Risikos unzulässig”: not permissible in most cases because of the unacceptable risk, in our translation. The fact sheet is guidance for public bodies, not law.

Where some documents can move, Microsoft 365 is a real option with its own questions: in Switzerland, where Microsoft 365 data sits from 14 December 2026 depends on a tenant setting. For documents that must stay on premises, Microsoft’s answer after 31 December 2026 is the desktop.

What are the options for SharePoint Server after 2026?

There are four main options, and they can be mixed library by library.

Option Documents stay Browser editing The catch
Microsoft 365 In Microsoft’s cloud Office for the web Not open to data that must stay on your servers
SharePoint Server, desktop only On your servers None Office LTSC 2024 support ends 9 October 2029, no extended phase
OOS kept without support On your servers Yes, unpatched No security updates from Microsoft after 31 December 2026
Nextcloud with Collabora Online On your servers, or a region you choose Yes A migration, and complex files to test first

Some vendors also sell a proprietary replacement for the browser-editing layer alone, outside this comparison; it keeps documents, permissions and the farm on SharePoint Server’s own lifecycle.

Keeping OOS without support is what happens by default. If you choose it, do so in writing, with an owner and an end date, and keep OOS on the internal network with an Allow List that names only your SharePoint hosts: Microsoft’s planning guide warns that with an empty list, OOS “allows file requests to hosts in any domain”.

What to do, and by when

31 December 2026 is Microsoft’s date for Office Online Server, the end of November 2026 its date for Excel workbooks hosted through OOS in Power BI Report Server, and 12 January 2027 its date for Windows Server 2016. The other dates are our suggestion, as of 9 November 2026.

  1. List every OOS binding by 30 November 2026. In each SharePoint farm, Get-SPWOPIBinding lists the farm’s WOPI bindings, those to OOS among them. Record the farm’s version, the OOS servers and their Windows Server version, the sites that edit in the browser, and any Power BI Report Server workbooks.
  2. Sort documents by where they may live by 15 December 2026. For each site or library, record whether it may move to Microsoft 365, must stay on your servers, or can be archived.
  3. Check desktop Office by 15 December 2026. Users who will edit on the desktop need Microsoft 365 Apps or Office LTSC 2024, since Office LTSC 2021 left support on 13 October 2026.
  4. Decide the fate of OOS by 31 December 2026. To disconnect it once desktop Office is ready, save the output of Get-SPWOPIBinding, then run Remove-SPWOPIBinding -Server with your OOS host name, first with -WhatIf; browser viewing, editing and previews then stop across the farm until libraries move. To keep it, record a risk acceptance with an owner and an end date, and keep it internal with a set Allow List. An OOS server on Windows Server 2016 also loses operating system support on 12 January 2027.
  5. Test an open-source editor by 31 March 2027. Take one team and its heaviest documents, open and save them in the browser editor, reopen them in desktop Office, and set the criteria and a decision date in advance (how to design a pilot).
  6. Move the first libraries by 30 June 2027. Start with the documents that must stay on your servers and that people edit together, or record why you are not moving them.

Browser editing on your own servers: what open source gives, and what it does not

The reason these farms exist, documents on your own servers, does not depend on Office Online Server. Nextcloud holds the files and folders. Collabora Online, the LibreOffice engine run on a server, opens Word, Excel and PowerPoint files in the browser and saves them back in the same format, so a .docx stays a .docx. Both are open source and run on hardware you choose. This route moves libraries off SharePoint Server; it does not replace the editor inside the farm. The code is public, so the editor does not end when one company’s support does: if one supplier stops, another can carry it on. Each supported Collabora version still has its own support window, so upgrades stay part of running it.

What open source does not give you on its own:

  • Identical rendering of every file. Ordinary documents keep their layout. Differences show in complex layouts, in documents set in fonts the server does not have, and in macro-enabled files, whose macros stay off by default. Test with your own heaviest documents, and keep desktop Office for the people who need it.
  • The Microsoft 365 features around the editor. Copilot, Loop components and co-editing with people still on Microsoft 365 do not come across. SharePoint’s metadata columns and content types have no one-to-one equivalent: in Nextcloud they become tags, folders or a workflow.
  • A free production editor. Collabora does not recommend its free development edition for production; the supported build is a per-user subscription.
  • Someone who runs it. An editor on your own servers is a service to size, patch, monitor and back up, as OOS was.

A test ends in a decision when its criteria are set in advance: in the Swiss Federal Chancellery’s proof of concept for open-source office automation, 73 people rated 12 scenarios and the results were published.

None of this is new to anyone who ran OOS, which also had to be sized, patched and, ideally, kept off the internet. The difference is that the code is open and the stack stays yours, to run yourself or to hand to another operator.

How Pilae fits

Office Online Server ends on Microsoft’s date; the reason for keeping documents on your own servers does not. Pilae operates open-source apps on your premises or on dedicated machines in Pilae Cloud. Operation on your premises starts on the Business plan.

  • Files and browser editing on your servers. Nextcloud replaces OneDrive, SharePoint and Google Drive, and Collabora Online edits Word, Excel and PowerPoint files in the browser (sovereign workplace). The Collabora subscription is held in your name, and we price it with you before you commit.
  • Difficult files found before anyone switches. A sample of your heaviest documents is opened and saved in Collabora, then reopened in desktop Office, and you see the list of what changed. Desktop Office keeps working through the Nextcloud sync client for the files that need it, though people editing a synced copy do not co-author live with people in the browser (Collabora Online).
  • Libraries moved, permissions rebuilt. Every site, library and list is inventoried, and libraries go to Nextcloud group folders. SharePoint permissions do not transfer, so access is rebuilt against your directory groups and checked with each owner. On an agreed day, a final delta copy runs and SharePoint goes read-only (SharePoint alternative).
  • Patched in your window, on the record. Upstream advisories for every app you run are tracked against your versions, and a fix is planned as soon as it is published. The Pilae Agent applies it in your maintenance window once you, or a rule you set, approve it, and records the run.
  • Your storage, your keys, a way out. On premises, your apps, files, databases and backups stay on machines and storage you own (on premises). Backups are encrypted before they leave the machine, with keys you hold, and every plan includes a written exit plan: your data, configuration and runbooks in open formats.

Our plans and prices are on the pricing page. If you run SharePoint Server, talk to an engineer: we go through your farms, the documents people edit in the browser today, and which libraries could move first.

Cover: photo by Wesley Tingey on Unsplash, redrawn in pixels.

Talk to an engineer about a gradual way off Microsoft 365

Thirty minutes with an engineer, a written plan and a fixed price for the first workload.

Book 30 minutes

Tell us what you need to run.