Quick answer. As of September 2026, Microsoft supports Microsoft 365 Apps on Windows Server 2022 only while Windows Server 2022 is in Mainstream Support, which ends on October 13, 2026; Microsoft will keep sending security updates for Microsoft 365 desktop apps on those hosts until October 10, 2028, but feature updates stop at Version 2608, and for a version of Windows Server that doesn’t support Microsoft 365 Apps, Microsoft recommends moving to Windows 365 or Azure Virtual Desktop, while Windows Server 2025 session hosts remain supported for Microsoft 365 Apps during their own Mainstream Support. Microsoft Learn’s Microsoft 365 Apps migration from Windows Server page lists Windows Server 2022 itself as supported until October 2031, so the decision is about Microsoft 365 Apps on the hosts, not about the servers.
The support notice usually lands on a remote-desktop farm that was built on Windows Server 2022 because it was current, and whose servers still have years of support ahead of them. The published desktops and RemoteApp programs on those hosts carry the enclave users, the contractor access path and the line-of-business apps, so the question the notice raises is not whether the servers stay up but where each group of users goes next. The most common triggers we see are a Microsoft end-of-support deadline landing on production, repeated unexplained outages or slowdowns, a security incident or a failed penetration test, and a compliance requirement such as HIPAA, GDPR, NIST SP 800-171, or CMMC 2.0 that your current environment cannot evidence. This guide takes Microsoft’s own statements, read on 2026-09-24, and turns them into a host decision per user group.
Three dates, three meanings: what ends, what continues, what does not change
When someone on the steering group says the servers are supported for years, so nothing changes, separate the three dates before the conversation goes further, because each governs something different.
What ends on October 13, 2026 is Microsoft 365 Apps support on those hosts. Microsoft’s Windows Server end of support and Microsoft 365 Apps page says “Microsoft 365 Apps is supported on Windows Server 2022 while it’s in Mainstream Support.” and “Mainstream Support for Windows Server 2022 ends in October 2026.” Microsoft’s Ending Support in 2026 page says “The following products will be moving from Mainstream to Extended Support in 2026.” and lists Windows Server 2022 with the date October 13, 2026. Microsoft’s Deploy Microsoft 365 Apps by using Remote Desktop Services page says the same thing for session hosts: “Microsoft 365 Apps (Version 2302 or later) is supported on Windows Server 2022 only until October 2026.”
The security-update bridge is what continues until October 10, 2028, and it is not support. Microsoft’s Windows Server end of support and Microsoft 365 Apps page says “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.” It also says “Devices running Microsoft 365 Apps on Windows Server 2022 will receive feature updates until Version 2608 is released.” and “Devices will remain on Version 2608, receiving only security updates until October 10, 2028.” Microsoft’s page does not give a release date for Version 2608, and neither does this guide.
Windows Server 2022’s own support does not change. Microsoft’s Microsoft 365 Apps migration from Windows Server page says “Support for Windows Server itself isn’t impacted.” and, in its list of end-of-support dates for Windows Server, gives “Windows Server 2022: October 2031”. Microsoft’s Ending Support in 2026 page says “Extended Support includes security updates at no cost, and paid non-security updates and support.”
Read the three together and one planning rule follows: a host still running Microsoft 365 Apps after October 13, 2026 will be receiving security updates and will be outside Microsoft’s support statement at the same time. Both halves belong in the risk register. Microsoft’s Windows Server end of support and Microsoft 365 Apps page gives the reason in its own words: “This policy requires customers to use Microsoft 365 Apps on a Windows operating system that is currently in support.” and “Using Microsoft 365 Apps on older, unsupported operating systems may cause performance and reliability issues over time.” If the farm still has Windows Server 2019 hosts in it, those are already past this point: the same page says “Support for Microsoft 365 Apps on Windows Server 2019 ended on October 14, 2025.”
Sort the users before choosing the host
When the first instinct is to pick one destination for the whole farm, stop and sort the users first, because a single answer almost never fits the enclave desktop, the contractor path and the published line-of-business apps at once. Microsoft’s Remote Desktop Services overview in Windows Server describes what the farm delivers: “Remote Desktop Services is a role-based infrastructure in Windows Server that lets authorized users connect over the network to:” a full desktop, session-based or virtual machine based, and RemoteApp programs.
- Inventory the session hosts, the published desktops and RemoteApp programs on each, and the user groups that use them.
- Tag each user group by the one constraint that decides its destination: it must stay on hosts you run, it can share pooled multi-session hosts, it needs a desktop of its own, or it sits inside a GCC High boundary.
- Confirm today’s Microsoft 365 Apps version on every host. Microsoft’s Microsoft 365 Apps migration from Windows Server page says “Only Version 2302 or later of Microsoft 365 Apps is supported on Windows Server 2022.”
- Carry shared computer activation into every design where users share a host. Microsoft’s Overview of shared computer activation for Microsoft 365 Apps says “Shared computer activation is required for scenarios where multiple users share the same computer and the users are logging in with their own account.”
The tags, not the product preferences, decide the sections that follow.
Hosts you keep running: Windows Server 2025 session hosts
If a user group’s apps or its boundary require session hosts you run yourself, the move is to Windows Server 2025 hosts. Microsoft’s Windows Server end of support and Microsoft 365 Apps page says “Microsoft 365 Apps is supported on Windows Server 2025 while it’s in Mainstream Support.” and “Mainstream Support for Windows Server 2025 ends in October 2029.” Footnote 5 of Microsoft’s Office and Windows configuration support matrix says the same: “Microsoft 365 Apps on Windows Server 2025 is supported during the Windows Server mainstream support period.”
Check the licenses before the first new host goes live. Microsoft’s License Remote Desktop Services with Client Access Licenses (CALs) page says “The RDS CAL for your users or devices must be compatible with the version of Windows Server that the user or device connects to.” and gives the case that matters here: “For example, if you have RDS CALs for Windows Server 2022, you can connect to a session host running Windows Server 2022 or earlier, but you can’t use them to connect to a session host running Windows Server 2025.” Which licenses to hold is a question for your license agreement and your licensing counsel; this guide only describes Microsoft’s compatibility statement.
What this path does not change is the shape of the question. Microsoft’s page ties Microsoft 365 Apps on Windows Server 2025 to that version’s Mainstream Support, which ends in October 2029, so a farm rebuilt on Windows Server 2025 meets the same decision again. Plan the rebuild with that date written into it.
Hosts that stay in your building: Azure Virtual Desktop on Azure Local
If a user group’s data or latency keeps its hosts on premises, Microsoft names a hybrid option. Microsoft’s Microsoft 365 Apps migration from Windows Server page says “If an on-premises session host deployment is required, Azure Virtual Desktop on Azure Local allows you to deploy session hosts to your on-premises Azure Local infrastructure.” and “Azure Virtual Desktop service components, including host pools, workspaces, and application groups, remain deployed in Azure.” Microsoft’s support statement for Microsoft 365 Apps is written per Windows Server version and names no hosting exception, so choose the session-host operating system on this path against the same statement as any other host.
Leaving session hosts you run: the two destinations Microsoft recommends
When the tags say a user group no longer needs hosts you run, the destinations are the two Microsoft names. Microsoft’s Windows Server end of support and Microsoft 365 Apps page says “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.”
For pooled users, this guide’s destination is Azure Virtual Desktop. Microsoft’s What is Azure Virtual Desktop? page says “Azure Virtual Desktop is a desktop and app virtualization service that runs on Azure.” and lists, among its uses, “Replace existing Remote Desktop Services (RDS) deployments.” Microsoft’s Windows Enterprise multi-session FAQ says “Windows 10 Enterprise multi-session and Windows 11 Enterprise multi-session, allows multiple concurrent interactive sessions.” and “Previously, only Windows Server could do this.”
Users who need a desktop of their own go to Windows 365 in this guide’s plan. Microsoft’s What is Windows 365? page says “Windows 365 is a cloud-based software-as-a-service (SaaS) that automatically creates a new type of Windows virtual machine (Cloud PCs) for your end users.” For government users, Microsoft’s What is Windows 365 Government? page says “Windows 365 Government is a cloud-based service that automatically creates virtual machines (Cloud PCs) for US government users.”
Our planning rule is simple: send pooled task users toward multi-session hosts, and send users who need a desktop of their own toward a Cloud PC. The choice between the two services, their licensing and their government deployment paths is a separate decision, taken after the user groups are sorted.
What changes inside a GCC High boundary
If a user group sits inside a GCC High boundary, check how its desktops will be managed before choosing multi-session hosts for it. Microsoft’s Microsoft Intune for US Government GCC High and DoD service description, last updated June 24, 2026, says “The following features aren’t available and there’s currently no planning to support these features for GCC High and DoD environments:” and lists “Windows Enterprise multi-session remote desktops (AVD)” among them. The same Intune fact, with the rest of that list, is covered in Is Microsoft Intune CMMC Compliant? What It Covers, and What It Does Not.
For a GCC High user group, settle the management path against Microsoft’s current list before the design is drawn, and re-read the list on the day you decide. Which cloud the tenant belongs in is a separate decision, and so is the authorization of any service; this guide makes no statement about either.
When this guide is the wrong starting point
If any of these situations describes your estate, the question changes shape:
- If the hosts run Windows client virtual machines rather than session hosts, Microsoft’s statement is different. Microsoft’s Microsoft 365 Apps migration from Windows Server page says “Hosting virtual Windows client devices with Microsoft 365 Apps on Windows Server remains supported as long as the Windows Server version is supported.”
- If the hosts run Office LTSC rather than Microsoft 365 Apps, Microsoft’s statement for Microsoft 365 Apps does not govern them, and the Office version, with its own support dates, is a separate decision.
- If the plan is to stay on Version 2608 until October 10, 2028, read how Microsoft describes that period on its Windows Server end of support and Microsoft 365 Apps page: security updates continue “while customers complete their migrations to a supported configuration”. It is a bridge for the move, and this guide does not recommend it as a destination.
- Microsoft’s pages are not your contract. Your license agreements govern what you may run and where.
- If Microsoft changes these dates, parts of this guide change with them. Re-read Microsoft’s pages on the day you decide.
What to ask of whoever helps
When you brief whoever helps with the move, internal team or outside firm, hold them to these criteria:
- An inventory of hosts, published apps and user groups before any estimate.
- Each user group assigned to a host path, with its deciding constraint written down.
- The Microsoft 365 Apps version and shared computer activation checked on every host.
- The RDS CAL version checked before any Windows Server 2025 host goes live.
- For GCC High user groups, the management path checked against Microsoft’s current Intune government list.
- Test users moved and confirmed before the farm is drained.
- People who have planned and run governed Microsoft 365 migrations in regulated estates, with senior, US-based delivery.
- A plain statement of what the engagement produces, and what it does not.
How i3solutions answers
i3solutions plans and runs governed Azure and Microsoft 365 migrations with senior, U.S.-based engineers. When a remote-desktop estate has to move before a Microsoft date, the work runs as a project: the host and user-group inventory, the user-group map to Microsoft’s host paths, the build of the chosen path, Microsoft 365 Apps packaging with shared computer activation, test users and cutover.
Embedded specialists can join your own team where it needs them for the design, build and testing. i3solutions has been a Microsoft partner since 1997 and has delivered 600+ implementations across aerospace and defense, financial services, and health sciences. An i3solutions engagement does not produce managed-service ownership, a replacement for the internal team, open-ended scope expansion, or vendor lock-in.
The migration service is described on Cloud Consulting and Migration, and the wider Microsoft practice on Microsoft Consulting Services Built for Enterprise Complexity.
Key Takeaways
- According to Microsoft, Microsoft 365 Apps is supported on Windows Server 2022 only while Windows Server 2022 is in Mainstream Support, which ends on October 13, 2026.
- According to Microsoft, security updates for Microsoft 365 desktop apps on Windows Server 2022 continue until October 10, 2028, with devices remaining on Version 2608; that is a bridge for the move, not support.
- According to Microsoft, Windows Server 2022 itself is supported until October 2031; the date that matters here is the one for Microsoft 365 Apps on the hosts.
- According to Microsoft, Microsoft 365 Apps is supported on Windows Server 2025 while it is in Mainstream Support, which ends in October 2029, and RDS CALs for Windows Server 2022 cannot be used to connect to a Windows Server 2025 session host.
- Sort the user groups first; send each to Windows Server 2025 hosts, Azure Virtual Desktop or Windows 365 by the constraint that decides it, and check GCC High groups against Microsoft’s Intune government list.
Frequently Asked Questions
Does Microsoft 365 Apps stop working on Windows Server 2022 after October 13, 2026?
No, but it leaves Microsoft’s support statement. According to Microsoft, “Microsoft 365 Apps is supported on Windows Server 2022 while it’s in Mainstream Support.” and Windows Server 2022 will leave Mainstream Support on October 13, 2026. According to Microsoft, “Devices will remain on Version 2608, receiving only security updates until October 10, 2028.” According to Microsoft, “Using Microsoft 365 Apps on older, unsupported operating systems may cause performance and reliability issues over time.”
Is Windows Server 2022 itself still supported after October 2026?
Yes. According to Microsoft, “Support for Windows Server itself isn’t impacted.” Microsoft lists “Windows Server 2022: October 2031” among its end-of-support dates for Windows Server, and says “Extended Support includes security updates at no cost, and paid non-security updates and support.”
Is Microsoft 365 Apps supported on Windows Server 2025 session hosts?
Yes, for now. According to Microsoft, “Microsoft 365 Apps is supported on Windows Server 2025 while it’s in Mainstream Support.” and “Mainstream Support for Windows Server 2025 ends in October 2029.”
Do our Windows Server 2022 RDS CALs work with Windows Server 2025 session hosts?
No. According to Microsoft, “For example, if you have RDS CALs for Windows Server 2022, you can connect to a session host running Windows Server 2022 or earlier, but you can’t use them to connect to a session host running Windows Server 2025.”
What does Microsoft recommend instead of Windows Server session hosts?
For a version of Windows Server that no longer supports Microsoft 365 Apps, Microsoft says “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.” According to Microsoft, “Azure Virtual Desktop is a desktop and app virtualization service that runs on Azure.” and “Windows 365 is a cloud-based software-as-a-service (SaaS) that automatically creates a new type of Windows virtual machine (Cloud PCs) for your end users.”
Planning the Decision
If your steering group needs the host and user-group inventory, a host-path map for each user group and a first-move plan before October 13, 2026, the next step is a conversation about your estate.
