Microsoft has confirmed that Microsoft 365 Apps running on Windows Server 2022 will stop receiving feature updates once Version 2608 reaches your update channel, locking those installations into a security-only servicing mode until October 10, 2028. Full support ends even sooner—when Windows Server 2022 exits Mainstream Support on October 13, 2026—forcing IT administrators to start planning migrations now.
The Countdown Starts with Version 2608
According to Microsoft’s updated support guidance for Windows Server, devices running Office apps on Server 2022 will continue to get new features only until Microsoft 365 Apps Version 2608 is released. After that, they’ll be pinned to that version, receiving only critical security patches for roughly two more years. Microsoft hasn’t set a universal release date for Version 2608, but as of mid-2025 the Current Channel and the new unified enterprise channel sat around Version 2606. The freeze will happen whenever your assigned update channel first delivers the 2608 build—timing may vary per environment.
The next hard deadline is October 13, 2026, when the operating system leaves Mainstream Support. While Windows Server 2022 itself remains in Extended Support until 2031, that longer OS lifecycle does not extend full support for the Office suite. After that October 2026 date, Microsoft will no longer provide regular technical support or non-security fixes for Microsoft 365 Apps on that platform.
What It Means for Your Organization
For IT teams managing Remote Desktop Services (RDS), application servers, or automation hosts, the implications are significant:
- No panic now, but no waiting. Office will keep working and remain fully supported until October 2026. However, the planning clock is ticking. Every month without a migration strategy shrinks your safety margin.
- A feature frozen island. Once Version 2608 arrives, no new capabilities will appear. If your users rely on Teams integrations, real-time co-authoring improvements, or AI-powered features, they’ll be stuck while cloud-connected colleagues move forward.
- Security bridge, not a destination. The security-only extension until 2028 is designed explicitly to give organizations time to migrate. It is not a new support lifecycle. After October 10, 2028, even security updates stop.
- Support complications. Trying to open a case for an Office problem on Server 2022 after October 2026 will likely meet with limited assistance, because the configuration will be outside the normally supported state.
How We Got to This Deadline
This news is part of Microsoft’s steady march toward modern desktop infrastructure. The Modern Lifecycle Policy demands that customers keep both the OS and the apps in a supported state. Server 2022, released in 2021 with a five-year Mainstream Support window, is simply hitting the end of its fully supported period for this workload.
A look at recent history shows a consistent pattern:
| Server Version | Microsoft 365 Apps Support Ends | Extended Security Updates Until | Final Office Version Frozen On |
|---|---|---|---|
| Windows Server 2016 | October 14, 2025 | October 10, 2028 | Version 2602 |
| Windows Server 2019 | October 14, 2025 | October 10, 2028 | Version 2608 |
| Windows Server 2022 | October 13, 2026 | October 10, 2028 | Version 2608 |
| Windows Server 2025 | October 2029 (Mainstream Support end) | Not yet defined | Not applicable yet |
Microsoft’s stated preference is for customers to move to Windows 365 or Azure Virtual Desktop. The company’s documentation says clearly: “If your organization is using a version of Windows Server that doesn’t support Microsoft 365 Apps, we recommend that you move to Windows 365 or Azure Virtual Desktop.”
Your Action Plan: From Inventory to Exit
Here’s how to tackle the transition in a structured way without letting panic drive decisions.
Step 1: Complete a Thorough Inventory
Before you can choose a destination, you need to know exactly what you have. Use your existing configuration management or vulnerability scanning tools to build a report that captures:
- All Windows Server 2022 systems with Microsoft 365 Apps installed—not just RDS session hosts but also back-end servers that run Office automation, jump hosts, and disaster recovery images.
- The installed Office version and update channel for each.
- Whether the server delivers shared interactive desktops, published apps, or unattended workflows.
- Critical dependencies: add-ins, macros, authentication providers, printer mappings, profile management tools, and line-of-business integrated applications.
- Ownership and business function: which department runs it, who the point-of-contact is, and any known future retirement plans.
Grouping every Office installation under “RDS” is a mistake. A multi-user session host, a published app server for a LoB program, and a back-end process using Excel automation may each need a different migration approach.
Step 2: Choose Your Migration Path
You have several realistic options. Evaluate each against your workload density, application compatibility, cost model, and in-house expertise.
| Option | Description | Pros | Cons |
|---|---|---|---|
| Windows Server 2025 with RDS | Upgrade session hosts to the newest server OS. | Least architectural disruption; full M365 Apps support until October 2029. | Still a server platform; you’ll face another deadline in about three years. |
| Azure Virtual Desktop | Pooled Windows 11 multi-session desktops in Azure. | Modern client OS; flexible scaling; Microsoft-preferred path. | Shifts management and cost to the cloud; requires AVD skills. |
| Windows 365 Cloud PCs | Persistent, individually assigned Windows 11 desktops as a service. | Simple provisioning; predictable per-user pricing. | Less dense than shared hosts; cost scales with user count. |
| On-premises virtual Windows 11 | Run Windows 11 VMs on supported Windows Server Hyper-V hosts. | Keeps data on-site; uses familiar virtualization. | Each VM is a full client OS needing management; no shared sessions. |
| Hold at Version 2608 (temporary) | Let Office freeze on Server 2022, rely on security patches. | Buys time if migration can’t finish before October 2026. | No new features; must have a solid, funded exit plan well before October 2028. |
Microsoft explicitly recommends Windows 365 and Azure Virtual Desktop for unsupported server configurations. However, the best choice depends on your specific environment. For example, if your application set is validated only on Windows Server and you need to keep the shared-session model, Server 2025 remains viable—but recognize it’s a three-year bridge, not a permanent fix.
Step 3: Plan Around the Version 2608 Freeze (If You’re Staying Temporarily)
If you cannot complete migration by October 2026, you must operate within the extended security window. Here’s how to do it safely:
- Let the freeze come naturally. Do not arbitrarily pin a build; allow your test and production environments to receive Version 2608 through their normal update channel. Validate everything in a pilot that mirrors production—same add-ins, same profile solutions, same authentication.
- Monitor continuously. Once the freeze takes effect, keep an eye on version numbers. Unexpected movement away from 2608, channel changes, or split-state collections are red flags.
- Document your configuration. Keep a known-good recovery image and note the update state before each maintenance cycle. Troubleshooting should first check: Is the host still on Version 2608? Is it on the expected channel? Are other hosts showing the same behavior?
- Set an internal hard deadline. The external deadline is October 10, 2028. Aim to have all users migrated by mid-2028 at the latest. The extra time is a buffer, not a strategy.
Step 4: Don’t Ignore Windows Server 2019 and 2016
While the news highlights Server 2022, older servers are on even tighter tracks. Windows Server 2019 and 2016 already lost full Microsoft 365 Apps support in October 2025 and will also stop receiving security updates on October 10, 2028. If you still have those in production, they should be prioritized even higher. Their final Office version (2602 for Server 2016) is already frozen; you’re operating on borrowed time.
What to Watch Next
The upcoming release of Version 2608 will be the immediate trigger for the feature freeze. Once Microsoft publishes a specific release date for that build on your channel, you’ll know exactly when the clock starts. Keep an eye on your admin dashboards and on Microsoft’s Microsoft 365 Apps update history page.
More broadly, Microsoft’s trajectory is unmistakable: the future of enterprise productivity desktops is on client-based Windows, whether delivered via the cloud or on local virtual machines. Server-based shared sessions are becoming a legacy approach. While Windows Server 2025 offers a short reprieve, it’s unlikely that the next server release will stretch that support any further. The prudent move is to start shifting to Windows 11 multi-session architectures now, even if you use Server 2025 as an interim step.
The good news is that you have time. The security-only commitment gives you until 2028 to complete a methodical migration, test thoroughly, and bring users along. But that window is finite. Use the next months to inventory, plan, and pilot. On October 11, 2028, the patches stop—and by then, you need to be somewhere else.