Is Windows Server 2022 end of life in October 2026?

No. Mainstream support ends 13 October 2026 US Pacific Time (14 October in Australia), after which the operating system moves to security-only servicing. Free security updates continue under extended support until 14 October 2031, with nothing to buy and no enrolment required. The genuine end-of-life date is 2031.

Will Office keep working on Windows Server 2022 after October 2026?

Yes, it keeps running, but it becomes an unsupported configuration. Microsoft 365 Apps freezes at Version 2608 — the August 2026 build — and receives security-only updates until 10 October 2028. After that date the apps receive no updates at all, so October 2028 is the hard deadline for Office on these servers.

Does this affect Windows Server 2022 file servers or domain controllers?

No. The October 2026 change only bites where Microsoft 365 Apps is installed, which in practice means Remote Desktop Services session hosts, Citrix farms and terminal servers. Domain controllers, file and print servers, SQL Server and Hyper-V hosts simply move to security-only servicing and remain supported until 14 October 2031.

Can Office LTSC be used on a Windows Server 2022 terminal server instead?

Yes. Office LTSC 2024, the volume-licensed perpetual version, is supported on Windows Server 2022 and receives five years of mainstream support from its 2024 release, with no extended support afterwards. It gets no feature updates and lacks cloud features such as real-time co-authoring and Copilot, so it works best as a bridge for a farm with a planned retirement date.

Does moving to Windows Server 2025 fix this permanently?

No — it resets the clock. Microsoft 365 Apps is supported on Windows Server 2025 while it is in mainstream support, which ends in October 2029, so the same freeze mechanics return in three years. Azure Virtual Desktop and Windows 365 avoid the recurring deadline because they deliver Windows 11 sessions that stay current under the Modern Lifecycle Policy.

No, Windows Server 2022 isn't dying in October 2026

Windows Server 2022 leaves mainstream support on 13 October 2026, but it is not a security cliff: free security updates continue under extended support until 14 October 2031. Two things do stop in October — non-security fixes for the operating system, and support for Microsoft 365 Apps, which matters most on remote desktop servers.

Expect a wave of alarming headlines about this date, because "end of support" articles rarely distinguish between mainstream ending and security updates ending. They are five years apart here. A Windows Server 2022 domain controller or file server faces no October emergency at all. A Windows Server 2022 session host with Office installed faces a real one, and it is getting almost no coverage. This guide separates the two.

What does not happen on 13 October 2026?

Windows Server 2022 follows Microsoft's Fixed Lifecycle Policy: five years of mainstream support, then five years of extended support. The October 2026 date closes the first phase only. Extended support is not a paid programme and does not need to be enrolled in — it is the standard second phase, during which security updates keep arriving through Windows Update at no charge until 14 October 2031.

Security updates continue every month, free, until 14 October 2031
Servers keep running, keep activating and are not forced onto a newer version
There is nothing to buy — paid Extended Security Updates only enter the conversation after 2031
Cyber-insurance and vendor questionnaires that ask about "supported operating systems" are still answered yes: the platform remains in extended support

Anyone quoting October 2026 as the date Windows Server 2022 becomes dangerous to run is misreading the lifecycle page. The equivalent moment for this product is October 2031, and Windows Server 2016 — whose extended support ends 12 January 2027 — is the estate that deserves the urgency this year.

What actually stops in October 2026?

Three things end when mainstream support closes, and they are worth naming precisely.

1Non-security servicing for the operating system stops. Bug fixes, reliability improvements and feature changes end; from October 2026 the OS receives security patches only.
2Support for Microsoft 365 Apps on Windows Server 2022 ends. This is the consequential one, covered in the next section.
3A footnote for Azure estates: Microsoft's lifecycle page notes that hotpatching on Windows Server 2022 Datacenter: Azure Edition is supported through the end of mainstream support.

Why is Office the real October deadline?

Microsoft 365 Apps — the subscription Office desktop applications included in most Microsoft 365 business and enterprise plans — is governed by the Modern Lifecycle Policy, which requires the apps to run on a Windows version that is in mainstream support. When Windows Server 2022 exits mainstream support in October 2026, Microsoft 365 Apps on that operating system becomes an unsupported configuration, even though the operating system itself remains supported for another five years.

The apps do not stop working, and Microsoft has published a defined wind-down rather than a hard cut. Devices running Microsoft 365 Apps on Windows Server 2022 receive feature updates until Version 2608 ships — under Microsoft's year-month numbering, the August 2026 build — and then freeze on that version.

"In the interest of maintaining security while customers complete their migrations to a supported configuration, Microsoft will continue providing security updates for Microsoft 365 desktop apps running on Windows Server 2022 until October 10, 2028."

— Microsoft, Windows Server end of support and Microsoft 365 Apps

So the practical shape of it: Office on a Windows Server 2022 session host freezes at Version 2608 in late 2026, receives security-only updates for roughly two years, and receives nothing at all after 10 October 2028. New Microsoft 365 features, including the Copilot capabilities Microsoft ships almost monthly, stop appearing on those servers while continuing to arrive on every laptop in the business. Support calls about the frozen version can also be met with "unsupported configuration" from vendors. October 2028 is the same terminal date Microsoft set for Office on Windows Server 2016 and 2019, which froze a year earlier — every Office-on-Windows-Server arrangement converges on it.

Who does this actually hit?

This deadline lands on one specific pattern: Windows Server 2022 used as a shared desktop, with Office installed on it. In Australia that pattern is concentrated in a few places.

Remote Desktop Services session hosts delivering Office alongside line-of-business applications
Citrix Virtual Apps and Desktops farms built on Windows Server 2022 VDAs with Microsoft 365 Apps installed
The single "terminal server" common in accounting and professional-services firms, where practice management software and Excel live side by side for remote staff
Bureaus and hosting providers that deliver client desktops from Windows Server session hosts

Accounting firms are the sharpest case. Excel is not incidental on those servers — it is half the job — and the same firms tend to keep server infrastructure for a long time because it works. A Windows Server 2022 terminal server installed in 2022 or 2023 feels nowhere near retirement age, which is exactly why this deadline will be missed.

Equally important is who this does not hit. Windows Server 2022 machines running as domain controllers, file and print servers, SQL Server hosts, Hyper-V hosts or application servers have no Office installed and therefore no October 2026 deadline. Those machines are secure and supported until 2031, and nobody should be sold an urgent migration for them on the back of this date.

What are the exit paths for an RDS farm running Office?

Rebuild the session hosts on Windows Server 2025

Microsoft 365 Apps is supported on Windows Server 2025 while that release is in mainstream support, which runs to October 2029. Rebuilding session hosts on 2025 is the most direct like-for-like path: the farm architecture, licensing model and management stay familiar. The honest caveat is that it buys three years before the same freeze mechanics arrive, so it suits businesses that want one more on-premises cycle while planning a longer-term move.

Move desktop delivery to Azure Virtual Desktop or Windows 365

Microsoft's own guidance page for this deadline recommends Windows 365 or Azure Virtual Desktop for organisations whose server no longer supports Microsoft 365 Apps. Both deliver Windows 11 sessions that stay current under the Modern Lifecycle Policy, which removes the recurring server-OS deadline from desktop delivery entirely. Azure Virtual Desktop suits businesses that want pooled multi-session economics and control; Windows 365 suits those that want a fixed-price cloud PC per user with less to operate. Either way, this is where Microsoft's remote-desktop investment is going, and a farm rebuild forced by the Office deadline is the natural moment to weigh it.

Swap to Office LTSC 2024 on the existing farm

For a farm that must stay on Windows Server 2022, Office LTSC 2024 — the volume-licensed perpetual version — is supported on Windows Server 2022 and carries five years of mainstream support from its 2024 release, with no extended support to follow. It receives no feature updates and lacks the cloud-backed capabilities of Microsoft 365 Apps, including real-time co-authoring and Copilot, and it means buying licences for software the Microsoft 365 subscription already includes elsewhere. It is a legitimate bridge for a farm with a fixed retirement date, not a destination.

There is also a fourth, entirely defensible option: accept the freeze deliberately. A firm that plans to move to Azure Virtual Desktop in 2027 can run frozen Version 2608 with security updates in the meantime. The distinction that matters is choosing that position with the October 2028 end date written into the plan, rather than discovering the freeze when a feature fails to arrive.

What should happen before October 2026?

1August: list every Windows Server 2022 machine and flag the ones with Microsoft 365 Apps installed — session hosts, Citrix VDAs and terminal servers. This is usually a short list, and everything not on it can be stood down from this deadline.
2September: pick a path per farm — Windows Server 2025 rebuild, Azure Virtual Desktop or Windows 365, Office LTSC 2024, or a deliberate freeze with a dated exit. Confirm line-of-business vendors support the chosen platform before committing.
3Before October 2026: execute, or document the freeze decision with its 10 October 2028 end date and the budget cycle that funds the move.
4Separately: park Windows Server 2022 machines without Office until the real planning window closer to 2031, and spend the recovered urgency on any remaining Windows Server 2016, which loses all security updates on 12 January 2027.

Frontrow's view is that October 2026 is a sorting exercise, not an emergency. Most Windows Server 2022 estates need nothing this year. The minority running Office on session hosts need a decision — and they have a published, two-year grace period in which to execute it well rather than quickly.