Announcing the retirement for Office Online Server

Microsoft should preserve a supported path for local document collaboration before retiring Office Online Server.

Retiring Office Online Server without a supported replacement for on-premises and private-cloud environments leaves a serious gap for customers who must retain control over their information. Microsoft’s published retirement date remains December 31, 2026, with Microsoft 365 recommended for browser-based editing and collaboration. That recommendation does not address workloads that must remain within infrastructure controlled by the customer.

For these customers, keeping documents local is a deliberate architectural requirement. Depending on the workload, regulatory obligations, contractual restrictions, information classification, or operational resilience requirements may prevent external processing. A migration deadline cannot remove those constraints.

Data sovereignty extends beyond where a file is stored. It includes where its contents are processed, who can administer the service, which jurisdiction applies, and who controls identities, encryption keys, logs, temporary files, and recovery procedures. Keeping a document in a local repository while sending its contents to an external service for rendering or editing may still cross the boundary that the organization is required to preserve. Regional hosting and encryption can address some concerns, but they do not automatically satisfy every requirement for operational control or disconnected operation.

Customer-controlled private clouds also need a credible roadmap. Organizations can modernize their infrastructure, automate deployment, strengthen access controls, and maintain disciplined patching while keeping document processing inside their own environment. Microsoft should support that form of modernization.

OOS provides practical capabilities that users depend on: Document previews, browser-based editing, and co-authoring within supported on-premises integrations. Desktop Office remains a valid option for many tasks, but it does not replace embedded browser workflows or eliminate the deployment and management burden on endpoints. The impact is already concrete in Power BI Report Server: Microsoft documents the end of support for hosting Excel workbooks through OOS after November 2026. Opening those workbooks in desktop Excel changes the workflow; moving them to Power BI Service changes the hosting model. Power BI Report Server documentation (https://learn.microsoft.com/en-us/power-bi/report-server/excel-oos)

There is also a mismatch in the product roadmap. Microsoft has committed to supporting SharePoint Server Subscription Edition and Exchange Server Subscription Edition until at least December 31, 2035. Retiring an important document service years earlier reduces the capabilities available to customers investing in those supported platforms. Those customers deserve a clear replacement roadmap. Microsoft’s server support commitment (https://learn.microsoft.com/en-us/lifecycle/additional-support-server-modern-lifecycle-policy)

The reported support arrangement through December 2028 is welcome, but its terms need to be published clearly. A customer shared a CSAM communication describing continued technical support and discretionary security fixes, and Stefan Goßner subsequently confirmed the report while stating that no public announcement had been released. Customers need to understand eligibility, coverage, and the status of dependent integrations before relying on that arrangement. Discussion on Stefan Goßner’s blog (https://blog.stefan-gossner.com/2025/10/21/retirement-date-for-office-online-server-has-been-announced/#comment-58048)

I urge Microsoft to take the following steps:

Publish a clear security maintenance commitment through at least 2030 or 2031, with defined coverage, eligibility, and patch delivery. This could focus on security and essential compatibility fixes, without requiring continued feature development.

Provide a supported successor for on-premises and customer-controlled private clouds, preserving local rendering, editing, and co-authoring, including operation without external connectivity.

Preserve document viewing and previews as a minimum baseline, through an official local viewer and rendering service for supported SharePoint and Exchange scenarios.

Offer a supported hybrid option for workloads permitted to use external processing, with explicit data-flow documentation, access controls, auditing, and retention policies.

Publish the impact on each integration and clarify licensing, including replacement rights and the commercial treatment of capabilities customers will lose.

A longer transition period would reduce immediate disruption, but customers who must remain local also need a lasting solution. Otherwise, the foreseeable choices are reduced functionality, costly workflow redesign, or continued use of unsupported software. That outcome creates avoidable security and operational risk.

Microsoft should give customers a supported way to modernize while retaining sovereignty over their data. A credible local roadmap would protect existing investments, preserve essential workflows, and demonstrate that Microsoft’s commitment to on-premises and private-cloud customers extends to the capabilities they use every day.