Office Online Server Retiring Dec 2026: What Breaks & How to Migrate

Office Online Server (OOS) reaches end of support on December 31, 2026. After that date, Microsoft stops all security updates, bug fixes, and technical support. Your OOS instances won't stop running overnight, but every day past the deadline you operate unpatched infrastructure that no vendor will help you fix, no auditor will accept, and no insurer will cover.

The real problem isn't the server going dark — it's the integrations that depend on it. SharePoint Server, Exchange Server, Skype for Business Server, and Power BI Report Server all lose supported browser-based Office functionality. If you're running SharePoint Server SE or Exchange Server SE, those products remain fully supported, but they lose a critical piece of their document workflow stack.

This guide covers exactly what breaks, who is affected, the real migration paths (including where each falls short), and a step-by-step transition plan.

For the full picture of every Microsoft product retirement hitting in 2026 — SharePoint 2019, Exchange 2016, Project Online, SharePoint Add-ins, and more — see our Microsoft 2026 End-of-Support Timeline.

What Is Office Online Server and Where Is It Used?

Office Online Server is the on-premises server product that provides browser-based versions of Word, Excel, PowerPoint, and OneNote inside your own datacenter. It was introduced in 2016 as the successor to Office Web Apps Server 2013, designed to bring browser-based Office capabilities into datacenter environments. Microsoft positioned OOS as a way for security- and compliance-sensitive organizations to host Office web experiences without moving content to Microsoft's cloud.

OOS is a service layer, not just a copy of Office installed on a server. Microsoft documents dedicated OOS servers with their own DNS and certificate setup, firewall rules, load balancing for multi-server farms, and host-specific connection points — SharePoint WOPI bindings and Exchange WacDiscoveryEndpoint settings. On the SharePoint side, OOS works only with claims-based web applications, and Microsoft strongly recommends HTTPS because the OAuth tokens exchanged between SharePoint and OOS can be intercepted and replayed over HTTP. (learn.microsoft.com)

OOS integrates with four primary products:

• SharePoint Server (SE, 2019, 2016): In-browser document viewing, editing, co-authoring, and document previews in libraries
• Exchange Server (SE, 2019, 2016): Rich attachment preview in Outlook on the web (OWA)
• Skype for Business Server: High-fidelity PowerPoint rendering, presenter notes, and in-meeting annotations
• Power BI Report Server: Hosting and rendering Excel workbooks in the browser

The December 31, 2026 Retirement: What Microsoft Announced

Microsoft has announced the end of support and retirement for Office Online Server effective December 31, 2026. After this date, OOS will no longer receive security updates, bug fixes, or technical support. (techcommunity.microsoft.com)

This is part of Microsoft's ongoing push toward cloud-first solutions. All future engineering investment in browser-based Office editing goes into Office for the Web inside Microsoft 365.

The risks of running past the deadline:

• No security updates. Systems running OOS will be exposed to the evolving threat landscape. Unsupported server software parsing complex file formats (Office documents, PDFs) is a high-value target for attackers. Any zero-day discovered in the WOPI protocol or Office rendering engine stays open permanently.
• Compliance violations. Unsupported software puts regulated organizations at risk of non-compliance. For most regulated entities, running an unpatched document rendering server is an immediate audit finding.
• No technical support — not even paid incidents.

What Breaks: Impact on SharePoint, Exchange, Skype, and Power BI

This is not just a server retirement. It's a capability removal from four product ecosystems that remain otherwise supported.

SharePoint Server (SE, 2019)

You lose:

• In-browser document viewing and editing for Word, Excel, PowerPoint, and OneNote files in document libraries. Clicking a document will prompt a download or attempt to open the desktop client.
• Document previews — hover-over and panel previews of Office and PDF files in SharePoint libraries and search results stop rendering.
• Real-time co-authoring in the browser for on-prem content.
• PDF rendering within SharePoint (OOS handles this).
• Excel Calculation Services for farms that depend on OOS for server-side Excel rendering.

Documents on SharePoint Server SE can then only be edited with desktop versions of Office. Some desktop co-authoring remains for Word, PowerPoint, OneNote, and Visio — but Excel is the biggest functional loss because the Excel desktop client does not support co-authoring workbooks in SharePoint Server. If your business users hear "desktop fallback" and assume they keep the same collaboration behavior, reset that expectation early. (techcommunity.microsoft.com)

Exchange Server (SE, 2019)

OOS powers rich attachment preview in Outlook on the web. After December 31, 2026, when users click on a Word, Excel, or PowerPoint attachment in OWA, the preview pane goes blank. They must download the file and open it in a desktop app. Exchange Online is not affected — the cloud service does not use OOS. (techcommunity.microsoft.com)

For organizations that enforced view-only attachment policies through OOS to prevent data leaks, this is a security model change, not just a UX regression. Forcing file downloads to endpoints increases the attack surface.

Skype for Business Server

The retirement affects organizations using Skype for Business for rich PowerPoint presentations:

• High-fidelity PowerPoint rendering loses its visual quality
• Presenter notes and in-meeting annotations stop functioning
• Embedded videos in slides play at lower quality
• Core meeting tools — whiteboards, polls, app sharing — remain unaffected

Microsoft advises migrating to Teams, which provides real-time collaboration, integrated chat, and seamless file sharing. For presentations, the replacement is screen sharing or Teams Live Events. (techcommunity.microsoft.com)

Power BI Report Server (PBIRS)

The PBIRS timeline is tighter than OOS itself:

• January 2026: PBIRS removes the option to configure OOS for Excel workbook hosting.
• November 2026: Support for hosting Excel workbooks via OOS in PBIRS ends.
• December 31, 2026: OOS end of support.

If you rely on PBIRS + OOS for Excel workbook rendering, your migration clock is shorter than you think. Microsoft points customers to Excel desktop, Excel for the web, or the Power BI service. (learn.microsoft.com)

If you built custom document portals around OOS Online Viewers or used OOS-style editing inside a line-of-business app, Microsoft's forward path is cloud-backed services such as SharePoint Embedded and the Microsoft 365 Document Collaboration Partner Program. Microsoft has not announced a new on-prem successor that preserves OOS's role. (learn.microsoft.com)

Who Is Actually Affected

The organizations hit hardest are exactly the ones that can't move fast: government agencies, defense contractors, financial institutions, healthcare systems, and universities. These organizations deployed OOS specifically to keep document collaboration within their own datacenters, satisfying strict data sovereignty and compliance requirements.

The mismatch is the problem. Microsoft has committed SharePoint Server SE, Exchange Server SE, and Skype for Business support through at least December 31, 2035 — while ending support for the browser Office component in 2026. The host products live on, but a core capability disappears.

Government and public sector organizations face the most severe impact. Strict security and data sovereignty requirements legally prevent cloud adoption in many cases, and since Microsoft will not be offering an equivalent on-premises successor from 2026 onwards, the recommended alternative is often not a realistic option for security-critical environments.

That said, Microsoft 365 is not automatically unusable for regulated workloads. Microsoft documents SharePoint Online compliance planning around retention, DLP, sensitivity labels, information barriers, and publishes deployment guidance for highly regulated sites and sovereign controls. Those controls address many compliance objections — but not all of them. If your environment is fully disconnected or legally barred from Microsoft 365, the desktop-client fallback is the realistic Microsoft-supported path. (learn.microsoft.com)

Organizations already dealing with the SharePoint Server 2019 end-of-support in July 2026 or the SharePoint Add-ins retirement in April 2026 are stacking multiple migration projects into a single calendar year. That's a resourcing problem on top of a technical one.

Migration Path 1: Microsoft 365 and Office for the Web

This is Microsoft's official recommendation and the only path that preserves browser-based document editing with full Microsoft support. Office for the Web inside Microsoft 365 is the direct functional replacement for OOS. (techcommunity.microsoft.com)

What you gain:

• Full browser-based editing and co-authoring for all Office file types
• Continuous updates — no more patching OOS servers
• Integration with Teams, OneDrive, SharePoint Online, and the full Microsoft 365 ecosystem
• Compliance features (DLP, sensitivity labels, eDiscovery) that exceed what on-prem can deliver
• AI features including Copilot

What it costs you:

• Per-user-per-month licensing (Microsoft 365 E3/E5 or Business plans)
• Data moves to Microsoft's cloud — may conflict with data residency or sovereignty requirements
• Identity infrastructure changes (Microsoft Entra ID sync)
• Network bandwidth and latency considerations for document-heavy workflows
• Change management for users accustomed to on-prem file shares and local URLs

Who this works for: Organizations already using Microsoft 365 for email or other workloads, or those without hard data sovereignty constraints. Organizations with 150 or more licenses can engage Microsoft FastTrack for migration planning support.

For custom app scenarios where documents were rendered through OOS Online Viewers, Microsoft now points to SharePoint Embedded, where content lives in the customer's Microsoft 365 tenant and can be opened in Office web and desktop clients.

Migration Path 2: Office LTSC 2024 / Desktop Client Fallback

For organizations using SharePoint Server SE or Exchange Server SE, Microsoft 365 Apps for Enterprise and Office LTSC 2024 remain supported desktop clients for viewing and editing documents on these servers. This is the "stay on-prem but lose browser editing" path. (techcommunity.microsoft.com)

What this means in practice:

• Users click a document in SharePoint → it opens in desktop Word/Excel/PowerPoint instead of the browser
• OWA attachment previews stop working — users download attachments to view them
• No browser-based co-authoring on on-prem content
• Mobile and thin-client users lose document access entirely (no desktop app = no document)
• Excel co-authoring is gone. The Excel desktop client does not support co-authoring workbooks in SharePoint Server. (learn.microsoft.com)

Who this works for: Organizations that cannot move data to the cloud, have desktop apps deployed everywhere, and can accept losing browser-based workflows.

This is a fallback, not a replacement. It buys time but doesn't buy a future.

Migration Path 3: Third-Party On-Premises Alternatives

For organizations that must keep browser-based editing on-prem, third-party products fill the gap Microsoft is leaving.

ONLYOFFICE Docs

ONLYOFFICE Docs offers a web-based document editing experience that can run entirely on-premises, in private or public cloud environments, or in hybrid configurations. It uses Office Open XML as its core format, providing strong .docx/.xlsx/.pptx compatibility. It integrates with SharePoint via standard WOPI bindings, as well as Nextcloud and other platforms. Licensing is per-seat or perpetual.

Collabora Online

Built on LibreOffice technology, Collabora Online can integrate with SharePoint Server and can be deployed on-prem or in a private cloud.

Trade-offs of third-party alternatives:

• Neither product has the same integration depth as OOS had with SharePoint and Exchange — expect custom configuration work
• OWA attachment preview replacement is not a standard feature of either; you'll need workarounds or accept the loss
• You're trading Microsoft support for a different vendor's support — evaluate their track record and SLAs carefully
• Format fidelity for complex documents (macros, embedded objects, advanced formatting) varies
• Introduces a new vendor and infrastructure management into your stack

Step-by-Step Transition Plan for Document Workflows

Whether you're moving to Microsoft 365, falling back to desktop clients, or adopting a third-party solution, the transition follows the same structural phases. The safest pattern: assess, pilot, migrate incrementally, then decommission.

Step 1: Inventory All OOS Dependencies

List every SharePoint farm with OOS bindings, every Exchange server with a WacDiscoveryEndpoint, every Skype deployment using PowerPoint sharing, every PBIRS instance hosting Excel through OOS, and any custom portal using Online Viewers. Most failed plans scope only SharePoint and miss the rest.

Run this on your SharePoint farm to see current WOPI bindings:

Get-SPWOPIBinding
Get-SPWOPIZone

For Exchange, check the WAC discovery endpoint configuration:

Get-MailboxServer | Format-List Name, WacDiscoveryEndpoint

Document every integration point. Many organizations discover OOS dependencies they didn't know about — custom applications using the WOPI protocol, internal portals embedding document previews, or line-of-business apps rendering Excel reports server-side.

Step 2: Define the Target Experience Per Workflow

Separate view-only, edit in browser, co-authoring, OWA attachment preview, PowerPoint meeting presentation, and Excel workbook hosting. These are different behaviors, and they don't all map to the same replacement.

Step 3: Sync Identities and Map Permissions

If migrating to Microsoft 365, identity mapping is non-negotiable. Microsoft's guidance is explicit: if required users and groups are not synchronized to Microsoft Entra ID, their permissions will not migrate. (learn.microsoft.com)

• Deploy Microsoft Entra Connect (formerly Azure AD Connect) to synchronize on-prem Active Directory with Microsoft Entra ID
• Configure hybrid identity — federated or password hash sync, depending on your security requirements
• Fix identity mismatches — resolve NoMatch and weak matches before moving a single high-value library
• Review conditional access policies to ensure document access works from all required devices and locations
• Assess network readiness — Microsoft 365 traffic patterns differ from on-prem; run the Microsoft 365 Network Connectivity Test

If staying on-prem with desktop fallback:

• Validate Office LTSC 2024 or Microsoft 365 Apps are deployed to all workstations that need document access
• Update SharePoint default open behavior — after removing OOS bindings, SharePoint defaults to the desktop client
• Test thin-client and mobile scenarios to identify users who will lose access

Step 4: Scan Content and Remediate Blockers

Use SPMT's scan and assessment features to inventory sites and download the risk report before scheduling a cutover. Fix blockers in a deliberate prep phase, not during a weekend migration window. (learn.microsoft.com)

Know the hard limits of Microsoft 365 before you move:

• Maximum file size: 250 GB
• Decoded path limit: 400 characters
• Permission-heavy structures need redesign: more than 100,000 children in a structure requires phased security migration
• Supported limit for unique permissions: 50,000 (Microsoft recommends keeping the count closer to 5,000)
• List-view threshold: 5,000 items — poor list design can trigger this after migration (support.microsoft.com)

If document approvals are part of your OOS-dependent process, audit workflows separately. SPMT can move certain SharePoint 2010 out-of-box workflows to Power Automate, but SharePoint Designer workflows and SharePoint 2013 workflows are not supported in that path. See our guide to InfoPath & SharePoint Workflows ending in 2026 for details.

Step 5: Pilot with Real Users

Choose a business area that uses documents heavily and validate:

• Version history preservation
• Permissions mapping accuracy
• Office open behavior (browser and desktop)
• Excel workbook functionality
• OWA attachment handling
• Workflow and form dependencies

If you're modernizing the SharePoint structure during this move, validate the hub and site design during the pilot — not after the bulk wave. For a deep dive into site topology decisions, read our guide on modern SharePoint architecture.

Step 6: Migrate in Waves

SPMT supports preserving permissions and version history and can rerun tasks to pick up new or changed content with incremental passes. Microsoft warns not to rename or move migrated files before the final migration pass, or you risk overwriting content during later runs. (learn.microsoft.com)

Step 7: Cut Over and Decommission OOS

After validation, switch users to the target experience. Then sever the connections to OOS.

For SharePoint, remove all WOPI bindings:

# Remove all WOPI bindings from the SharePoint farm
Get-SPWOPIBinding | Remove-SPWOPIBinding -Confirm:$false
 
# Verify bindings are removed
Get-SPWOPIBinding

For Exchange, clear the WAC discovery endpoint at both the organization and mailbox-server level:

Set-OrganizationConfig -WACDiscoveryEndpoint $null
Get-MailboxServer | Set-MailboxServer -WacDiscoveryEndpoint $null

Recycle the OWA application pool in IIS on each Exchange server after clearing the endpoints.

Once all bindings are removed and traffic has ceased, decommission the OOS farm:

Remove-OfficeWebAppsMachine

Decommission the OOS VMs or physical servers. Remove all associated DNS records pointing to internal and external OOS URLs to prevent dangling DNS vulnerabilities. Store final configuration backups and decommission logs.

Step 8: Validate and Communicate

Test every workflow that previously depended on OOS:

• Open Word/Excel/PowerPoint files from SharePoint libraries
• Preview attachments in OWA
• Render reports in PBIRS (if applicable)
• Run meeting presentations in Teams or Skype (if applicable)

Update helpdesk scripts and send user communications explaining the new document handling behavior before go-live. Your support team needs to know the new behavior before users start filing tickets.

Why Cloud Is the Only Sustainable Path Forward

OOS is not an isolated retirement. It's part of a systematic removal of on-prem self-sufficiency:

• SharePoint 2013 workflows — retired from Microsoft 365 tenants April 2, 2026
• SharePoint Add-ins and Azure ACS — retired April 2, 2026
• SharePoint Server 2019 — end of extended support July 14, 2026
• InfoPath Forms Services in SharePoint SE — unsupported after July 14, 2026
• Project Online — retired September 30, 2026
• Office Online Server — retired December 31, 2026

SharePoint Server SE will be supported until 2035, but it will be a diminished product — no browser editing, no legacy workflows, no add-ins. The on-prem story becomes "store files and serve pages, but for anything modern, use the cloud."

Microsoft has been unusually clear about the direction. The alternatives it now documents are Microsoft 365, SharePoint Embedded for app scenarios, FastTrack for migration planning, and supported desktop clients. There is no announced Microsoft plan to keep a supported on-prem browser Office server alive after 2026. (techcommunity.microsoft.com)

From Microsoft's perspective, the cloud delivers richer collaborative features — real-time co-authoring, integrated security and compliance controls, tighter Teams/OneDrive/SharePoint integration — that are costly to replicate in isolated datacenters. For organizations that can move, the argument for Microsoft 365 is strong: a continuously updated platform, better security tooling, and the full weight of Microsoft's engineering investment. The on-prem path gets narrower every year.

For organizations that genuinely cannot move — government, defense, critical infrastructure — third-party alternatives and the desktop fallback are viable interim solutions. But they require an honest assessment: are you choosing on-prem because of a real regulatory constraint, or because of organizational inertia? The answer should drive your strategy.

Moving document workflows — with metadata, version history, permissions, and user expectations intact — from on-prem to cloud is non-trivial. It touches identity systems, network architecture, compliance posture, and end-user behavior simultaneously. That's exactly the kind of problem where a migration partner earns their keep.