Microsoft 365 Apps on Server 2022 Support Ends October 14, 2026

Windows Server 2022 can remain securely serviced until October 14, 2031, but organizations using it to host Microsoft 365 Apps should not mistake that date for an Office support guarantee. For Remote Desktop Services and virtual desktop deployments, the practical decision arrives on October 14, 2026, when support for Microsoft 365 Apps on Windows Server 2022 ends; administrators should migrate those application hosts to a supported platform unless they are prepared to operate an unsupported configuration.
Microsoft’s lifecycle documentation confirms that Windows Server 2022 leaves Mainstream Support on October 13, 2026, then remains in Extended Support through October 14, 2031. WindowsForum user reports about the Server 2022 lifecycle have focused on that transition from mainstream to extended support. The important planning issue is that the operating system and Microsoft 365 Apps have separate support timelines.
October 14, 2026 is specifically the support end date for Microsoft 365 Apps on Windows Server 2022. It is not a universal deadline for every Office product, every perpetual Office edition, or every application installed on Server 2022. Administrators must check the lifecycle and supported operating systems for each installed product.

Current Server 2022 role	Required decision
Does not host Microsoft 365 Apps	Treat retention or migration as an operating-system lifecycle decision through October 14, 2031, while checking every other application separately
Hosts Microsoft 365 Apps	Verify supported target platforms, complete a pilot, and migrate before October 14, 2026

The Operating System Is Not Reaching End of Life​

Windows Server 2022 does not reach the end of its overall support lifecycle in October 2026. It moves from Mainstream Support into Extended Support, which continues through October 14, 2031.
That distinction matters for servers running file services, directory infrastructure, line-of-business applications, or workloads that do not depend on products with shorter support requirements. Administrators may conclude that Windows Server 2022 remains suitable for some stable roles, subject to their organizations’ security, compliance, hardware, application-support, and operational requirements.
The WindowsForum user reports supplied for this issue identify October 13, 2026 as the end of Mainstream Support and October 14, 2031 as the end of Extended Support. Those operating-system dates do not extend the supported life of applications installed on the server.
Microsoft 365 Apps creates the earlier decision point. A lifecycle inventory that records only “Windows Server 2022—supported until 2031” can therefore misclassify shared Office hosts as low-priority systems. The inventory must identify the applications and deployment images associated with each host.

---

RDS and VDI Hosts Face the Earlier Deadline​

The mismatch is particularly important on Remote Desktop Session Host servers and other shared application platforms. These systems may deliver Word, Excel, Outlook, PowerPoint, or subscription editions of Visio and Project to many users from a relatively small number of hosts.
Migration planning must cover more than installing a newer operating system. A shared Office environment can depend on activation configuration, license eligibility, user profiles, Outlook settings, add-ins, printers, file associations, authentication components, profile containers, macros, document-management systems, and third-party integrations. Each dependency must be validated for the proposed architecture.
Windows Server 2025 is Microsoft’s current Long-Term Servicing Channel release, but that fact alone does not establish support for every Microsoft 365 Apps deployment. Before choosing it as a destination, administrators must consult Microsoft’s current Microsoft 365 Apps supported-operating-system matrix and verify licensing, application compatibility, activation, and multi-session requirements.
Microsoft also recommends evaluating Windows 365 and Azure Virtual Desktop when a Windows Server version does not support Microsoft 365 Apps. They should not be treated as interchangeable or automatically validated migration targets. Before selecting either service, verify:

• Microsoft 365 Apps and Office deployment requirements
• License eligibility and activation design
• Line-of-business application and add-in compatibility
• Identity, authentication, and conditional-access dependencies
• User-profile, Outlook, and data-storage requirements
• Printing, peripherals, and local-resource redirection
• Multi-session behavior and expected capacity
• Network latency, service availability, regional support, and data-location requirements
• Management, security, monitoring, backup, and recovery responsibilities

The target should follow the workload and the validated requirements. An organization may evaluate Windows Server 2025 for a conventional on-premises architecture after confirming its current support status. Windows 365 may fit a suitable dedicated cloud-PC model, while Azure Virtual Desktop may fit a suitable pooled or multi-session design. None should be selected solely because it appears on a generic modernization list.
A successful base-platform deployment also does not prove that Office is ready. The pilot must demonstrate Microsoft 365 sign-in, activation, profile loading, Outlook behavior, add-ins, document workflows, protected content, printing, and representative multi-session use.

Unsupported Means the Combination Leaves Microsoft’s Support Matrix​

After October 14, 2026, Microsoft 365 Apps on Windows Server 2022 is an unsupported operating-system and application combination. Administrators should not infer a specific launch or failure behavior from the support date.
Microsoft warns that running Microsoft 365 Apps on an unsupported operating system can cause performance and reliability problems, including features not working as expected. That is enough to make migration necessary for organizations that require a supported configuration, without speculating about whether a particular application will open after the deadline.
Testing must cover complete workflows rather than a simple launch check. Identity services, cloud connections, add-ins, document-management integrations, protection controls, and authentication processes can change independently of the Server 2022 operating system. Opening a document successfully does not demonstrate that the environment is supported or that every dependent workflow remains reliable.
WindowsForum reports about Microsoft 365 Apps on Windows 10 similarly centered on an application-support date tied to a particular operating system. For Server 2022 planning, the useful principle is to track the operating system and each major application as separate lifecycle items.

Use This Migration Decision Procedure​

The remediation path should be executable, not merely a planning checklist:

1. Find every affected host and image. Identify all Windows Server 2022 systems containing Microsoft 365 Apps, including production RDS hosts, published-application servers, VDI pools, test systems, disaster-recovery machines, powered-off templates, and image-building pipelines.
2. Record the existing deployment. Capture the Microsoft 365 Apps edition, build, update channel, deployment configuration, activation configuration, update controls, and assigned owner. Document license eligibility against current product terms and the organization’s Microsoft agreement.
3. Check Microsoft’s current supported-OS matrix for each candidate. Do not assume that Windows Server 2025, Windows 365, Azure Virtual Desktop, or another platform supports the intended Office deployment merely because the platform is current. Verify Microsoft 365 Apps support and relevant multi-session, licensing, and activation conditions.
4. Select the target architecture. Choose an on-premises server, Windows 365, Azure Virtual Desktop, or another confirmed supported design based on application compatibility, identity, profiles, capacity, operations, regional availability, service requirements, and cost.
5. Create a representative pilot. Include normal user personas, access methods, policies, security controls, profile technology, applications, add-ins, printers, and expected concurrency. Do not limit testing to an administrator account.
6. Validate the complete user experience. Test activation, Microsoft 365 sign-in, profile creation and loading, Outlook, add-ins, macros, printing, protected content, file associations, authentication, document-management integrations, and multi-session behavior. Test performance under a representative load.
7. Prepare migration and rollback plans. Separate the plans for the host platform, Microsoft 365 Apps deployment, profiles, user data, dependent applications, and access configuration. Assign owners and completion dates.
8. Migrate before October 14, 2026. Move production users only after the pilot’s acceptance criteria have been met. Any system that cannot move should enter a documented exception process with a business owner, risk acceptance, compensating controls, and a firm exit date.
9. Retire old hosts and images. Remove obsolete Server 2022 Office hosts, templates, snapshots, deployment tasks, and recovery images. Otherwise, a later pool rebuild or disaster-recovery operation could silently reintroduce the unsupported combination.

The required inventory output should classify every Windows Server 2022 host as:

• No Microsoft 365 Apps
• Migrate to Server 2025 after support-matrix validation
• Evaluate Windows 365 or Azure Virtual Desktop after full requirements validation

A spreadsheet containing only server names and operating-system lifecycle dates is insufficient. It will not identify which machines face the earlier Microsoft 365 Apps deadline, and it may omit dormant images capable of recreating those machines.

---

Staying Put Is a Business Exception, Not a Lifecycle Strategy​

Some organizations may remain on Windows Server 2022 with Microsoft 365 Apps after October 2026 because a dependent application, vendor certification, budget cycle, or infrastructure project prevents migration. That decision should be recorded as an exception rather than justified with “Windows Server is supported until 2031.”
The exception should identify affected users and workflows, the business owner accepting the risk, monitoring and compensating controls, and the planned exit date. It should also account for possible performance, reliability, or feature problems associated with running Microsoft 365 Apps on an unsupported operating system.
Compliance consequences will depend on the organization’s policies, contracts, insurance terms, and regulatory obligations. Administrators should nevertheless distinguish between an operating system remaining in Extended Support and an application being deployed on a supported operating system. They are not the same assurance.

Frequently Asked Questions​

Does Windows Server 2022 reach end of support in October 2026?​

No. Mainstream Support ends October 13, 2026, but Extended Support continues through October 14, 2031.

Is October 14, 2026 a deadline for every Office product on Server 2022?​

No. It is the support end date for Microsoft 365 Apps on Windows Server 2022. Perpetual Office editions and other installed applications have their own lifecycle and supported-operating-system requirements, which administrators must check separately.

What changes for Microsoft 365 Apps on Server 2022 after October 14, 2026?​

The combination leaves Microsoft’s supported platform matrix. Microsoft warns that Microsoft 365 Apps on unsupported operating systems can encounter performance, reliability, and feature problems.

Must every Server 2022 host migrate to Server 2025?​

No. Hosts without Microsoft 365 Apps can be evaluated against the Server 2022 lifecycle and their other application requirements. For affected Office hosts, Server 2025 is only a candidate until Microsoft’s current supported-OS matrix and the organization’s deployment requirements have been verified.

Are Windows 365 and Azure Virtual Desktop ready-made replacements?​

Not automatically. Microsoft recommends evaluating them when a Windows Server version does not support Microsoft 365 Apps, but organizations must validate Office deployment, licensing, applications, identity, profiles, printing, multi-session behavior, capacity, and regional or service requirements before choosing either architecture.

What should administrators do first?​

Find every Server 2022 host and image containing Microsoft 365 Apps. Then check Microsoft’s current supported-OS matrix for each proposed target, select an architecture, run a representative pilot, validate activation and user workflows, migrate before October 14, 2026, and retire the old hosts and images.

---

References​

1. Primary source: learn.microsoft.com
   
   

   Ending Support in 2026 - Microsoft Lifecycle | Microsoft Learn

   Find out which products will retire, reach end of support or move from mainstream support to extended support in 2026.

   learn.microsoft.com
2. Primary source: WindowsForum
   
   

   Windows Server 2022 Mainstream Support Ends October 13, 2026 | Windows Forum

   Windows Server 2022 will leave mainstream support on October 13, 2026, giving administrators less than three months to decide whether five more years of...

   windowsforum.com

 

[ChatGPT]

Microsoft 365 Apps on Windows Server 2022 should be treated as a migration workload now, not as a platform that remains strategically current until Server 2022 leaves Extended Support. Most RDS administrators should either upgrade compatible session hosts to Windows Server 2025 or move users to Windows 11-based desktops; holding at Version 2608 is a defensible bridge only when the organization has a funded, tested exit plan before October 10, 2028.
Microsoft’s support schedule creates three separate deadlines. Feature development stops when Version 2608 reaches the applicable update channel, normal Microsoft 365 Apps support ends with Windows Server 2022 Mainstream Support on October 13, 2026, and security-only Office servicing continues for two more years.

Version 2608 Starts the Freeze, Not the Outage​

Microsoft says Windows Server 2022 devices will receive Microsoft 365 Apps feature updates until Version 2608 is released. Those installations will then remain on Version 2608 and receive security updates through October 10, 2028, according to Microsoft’s Windows Server support guidance for Microsoft 365 Apps.
That does not mean Word, Excel, Outlook, PowerPoint, or other installed apps suddenly stop opening. It means Server 2022 becomes a frozen Office platform: security fixes continue, but new features and feature-level improvements do not.
The timing is less precise than a conventional end-of-support date. As of July 14, 2026, Current Channel and Microsoft’s newly unified enterprise channel were on Version 2606, while Microsoft had not published Version 2608 release details. The practical freeze therefore depends on when Version 2608 becomes available to each organization’s channel, rather than on one confirmed global date.
Administrators should not turn “2608” into an assumed August deadline or schedule a production change around an unannounced release day. The meaningful trigger is when Version 2608 is actually offered to the channel assigned to a particular Server 2022 installation.
The next boundary is fixed. Microsoft 365 Apps support on Windows Server 2022 ends on October 13, 2026, when the operating system leaves Mainstream Support. Windows Server 2022 itself remains in Extended Support until October 14, 2031, but that longer OS lifecycle does not extend full Microsoft 365 Apps support.
This distinction matters in support cases. A server can remain supported as a Windows Server operating system while its Microsoft 365 Apps deployment is outside the normally supported configuration.

---

Inventory the Estate Before Choosing a Destination​

The first migration task is not selecting Azure Virtual Desktop or ordering Server 2025 licenses. It is discovering every Server 2022 system on which Microsoft 365 Apps is installed, including lightly used RDS collections, administrative jump hosts, application servers with Office automation dependencies, and dormant disaster-recovery images.
Use the organization’s existing endpoint management, software inventory, configuration management, or vulnerability-management platform to build a report containing at least:

• Each device’s Windows Server edition and version.
• Whether Microsoft 365 Apps is installed.
• The installed Microsoft 365 Apps version and assigned update channel.
• Whether the server provides shared interactive sessions.
• The applications, add-ins, macros, printers, profile tools, and authentication components required by its users.
• The server owner, user group, business function, and planned retirement date.

Do not group every Office-bearing server under “RDS.” A multiuser session host, a published-application server, and a back-end system using Office in a workflow may have very different migration paths. The inventory must identify the workload as well as the installed product.
Create a separate exception list for hosts that cannot yet move. Each exception should name an owner, explain the blocker, identify the intended replacement, and carry a target date. Without those fields, “hold at 2608” can quietly become an unplanned production standard.
Microsoft’s parallel changes around Windows 10 and Microsoft 365 Apps offer a useful warning: an operating system may continue functioning after the preferred Office configuration has stopped advancing. WindowsForum’s earlier coverage of the Windows 10 feature-update cutoff showed the same need to separate application servicing, operating-system servicing, and real-world usability rather than treating them as one deadline.

Server 2025 Is the Least Disruptive RDS Choice​

Windows Server 2025 is the most direct destination for organizations that still need traditional Remote Desktop Services and want to preserve a server-based shared-session architecture. Microsoft supports Microsoft 365 Apps on Windows Server 2025 during the operating system’s Mainstream Support period, which is scheduled to end in October 2029.
That provides a longer runway, but it is not a permanent resolution. An organization beginning a substantial RDS redesign should consider whether migrating to another server platform for roughly three additional years of full Microsoft 365 Apps support is preferable to moving users onto a Windows client-based desktop model.
Server 2025 is the stronger choice when the current environment depends heavily on RDS collections, established server management practices, local infrastructure, or applications already validated for Windows Server. It can also reduce the number of architectural changes introduced in one project.
The upgrade still requires application testing. Office add-ins, profile handling, authentication flows, document-management integrations, line-of-business applications, and peripheral redirection may be more important to the outcome than Office itself. A successful Microsoft 365 Apps installation does not prove that an RDS workload is ready for production.

Windows 11 Desktops Break the Server Lifecycle Link​

Azure Virtual Desktop is the natural alternative when an organization wants Windows 11 multi-session rather than another server-based Office deployment. It moves the user environment onto a Windows client platform while retaining pooled, remotely delivered desktops.
This route is attractive for larger or variable user populations, organizations already operating in Azure, and teams prepared to manage image lifecycle, profiles, capacity, connectivity, and cloud costs. It is not merely a hosted replacement for an RDS Session Host; it changes the control plane and operating model.
Windows 365 is better aligned with users who need persistent, individually assigned Cloud PCs and predictable per-user provisioning. It can simplify parts of desktop delivery, but dedicating a Cloud PC to each user is materially different from concentrating many users on shared RDS hosts.
Microsoft explicitly recommends Windows 365 or Azure Virtual Desktop for customers moving away from unsupported Windows Server configurations. That recommendation reflects Microsoft’s direction, but administrators should still choose according to workload density, user persistence, networking, management skills, and application behavior—not branding alone.
A third option is hosting virtual Windows client devices with Microsoft 365 Apps on Windows Server virtualization infrastructure. Microsoft says this remains supported while the host Windows Server version is supported. This model can preserve on-premises control while separating the Office desktop lifecycle from the guest host’s server-session role, although it replaces shared sessions with individually managed client virtual machines.

Holding at 2608 Requires More Control, Not Less​

A controlled Version 2608 hold is reasonable when an organization cannot complete migration by October 13, 2026, provided decision-makers understand what the extension covers. Microsoft is promising security updates through October 10, 2028—not ongoing feature compatibility or a continuation of full support.
Administrators should allow the production environment to reach Version 2608 through its intended servicing channel rather than treating an unpublished build as something to pin preemptively. Before broad deployment, validate 2608 in a representative test collection containing the same add-ins, profile technology, policies, authentication methods, and published applications used in production.
After the freeze begins, monitor whether Server 2022 hosts remain on Version 2608 and continue receiving security servicing. Unexpected version movement, failed updates, channel changes, or inconsistent builds across a collection should be investigated rather than accepted as harmless drift.
Keep a known-good recovery path for the shared image or host pool, and document the update state before each maintenance cycle. Troubleshooting should first establish whether the affected host is actually on Version 2608, whether it is using the expected channel, and whether other hosts in the same collection show the same behavior.
The largest risk is not that Office immediately becomes insecure after October 2026. It is that a two-year security bridge creates false confidence while newer Microsoft 365 features, service changes, add-ins, or integrations evolve around a frozen desktop release. Microsoft itself warns that using Microsoft 365 Apps on older, unsupported operating systems can lead to reliability or performance problems as features and updates change.

---

Match the Platform to the Constraint​

The decision can be reduced to the constraint that matters most.
Choose Windows Server 2025 when preserving conventional RDS architecture and minimizing operational change outweighs the limited October 2029 Microsoft 365 Apps support horizon. Choose Azure Virtual Desktop when pooled Windows 11 multi-session desktops fit the workload and the organization can operate the Azure-based platform.
Choose Windows 365 when users benefit from persistent, individually assigned desktops and the organization prefers Cloud PC provisioning over shared-session density. Choose virtual Windows client desktops on supported Windows Server hosts when on-premises infrastructure must remain but Office users can move away from server sessions.
Hold Server 2022 at Version 2608 only when migration cannot be completed safely before October 13, 2026. The hold should have executive acceptance, named workload owners, regular servicing validation, and a migration deadline comfortably ahead of October 10, 2028.
Microsoft 365 Apps LTSC may deserve evaluation where a workload needs a deliberately static Office feature set rather than the Microsoft 365 Apps service model. It should not be treated as an automatic licensing swap or a way to avoid platform planning; administrators must separately validate whether its capabilities, servicing model, and application requirements fit the users involved.

The Remaining Administrative Questions​

Does Microsoft 365 Apps stop working on October 13, 2026?
No. Full support ends on that date, but Microsoft says installations held on Version 2608 will continue receiving security updates until October 10, 2028.
When exactly will Server 2022 stop receiving feature updates?
Microsoft has not published a universal Version 2608 release date. The freeze occurs when Version 2608 is released through the update channel used by the device.
Does Windows Server 2022 reach end of support in 2026?
It leaves Mainstream Support on October 13, 2026, but remains in Extended Support until October 14, 2031. That OS extension does not preserve full support for Microsoft 365 Apps.
Is upgrading to Windows Server 2025 enough?
It restores a supported Microsoft 365 Apps configuration during Server 2025 Mainstream Support, currently listed through October 2029. Organizations should still decide whether that runway justifies another server-session migration instead of moving to Windows 11 desktops.
Version 2608 is a pause point, not a destination. Administrators who inventory their Server 2022 Office footprint now can use the security-only period as an engineered migration window; those who wait until October 2028 will discover that Microsoft supplied extra servicing time, not an extra migration plan.

---

References​

1. Primary source: learn.microsoft.com
   
   

   Windows Server end of support and Microsoft 365 Apps - Microsoft 365 Apps | Microsoft Learn

   Provides admins using Microsoft 365 Apps with information about which versions of Windows Server are supported.

   learn.microsoft.com
2. Primary source: WindowsForum
   
   

   Microsoft 365 Apps: End of Updates on Windows 10 by October 2025 | Windows Forum

   Microsoft is taking yet another significant step in phasing out Windows 10 support, this time by announcing the end of updates for Microsoft 365 apps like...

   windowsforum.com

 

[ChatGPT]

Windows Server 2022 can remain in service after October 13, 2026 because it enters Extended Support and continues receiving security updates, but organizations that deliver Microsoft 365 Apps through RDS, VDI, or published applications need a separate plan: support for Microsoft 365 Apps on Server 2022 ends on that same date, as does support for Office LTSC 2021.
That distinction matters because the operating system and the Office session-host stack do not share the same support outcome. A Server 2022 file server, infrastructure server, or line-of-business workload may continue under Extended Support. A shared environment that runs Office for many users has a more immediate application-platform deadline.
The practical question is not, “Must every Server 2022 machine be replaced in 2026?” It is, “Which Server 2022 machines are part of an Office delivery service, and what must change before the Office support deadline?”
WindowsForum members have seen this pattern in earlier Microsoft 365 retirement discussions: a product retirement rarely affects one isolated component. It exposes the add-ins, profiles, licensing, workflows, and administrative processes built around that component. For October 2026, the sharpest impact is on shared Office delivery rather than every Windows Server 2022 workload.

The October 2026 deadline belongs to the Office session-host stack​

Windows Server 2022 entering Extended Support does not make every server an emergency replacement project. Security servicing continues for the operating system, so organizations should avoid treating ordinary Server 2022 workloads as though they all face the same deadline.
RDS, VDI, and published-app deployments are different. A single session host can provide Outlook, Excel, Word, and other Office applications to many users. That makes a platform mismatch more consequential: Office updates, add-ins, sign-in flows, profiles, application publishing, and endpoint controls all converge in one shared environment.
Microsoft lists October 13, 2026 as the end of support date for Microsoft 365 Apps on Windows Server 2022. Office LTSC 2021 also reaches end of support on October 13, 2026. Those dates should drive planning for Office session hosts even where the underlying Server 2022 operating system remains supported through Extended Support.
For many organizations, the appropriate path will be to retain Server 2022 only where it is still suitable for non-Office workloads while moving Office session delivery to a platform supported for the organization’s chosen Office deployment. Depending on the environment, that might mean rebuilding RDS hosts on a newer supported platform, evaluating Azure Virtual Desktop or Windows 365 for appropriate user groups, or reducing dependence on server-hosted Office where business applications allow it.
Those are options, not automatic replacements. The best target depends on application compatibility, user-location requirements, identity architecture, licensing, profile tooling, and the organization’s ability to operate a new delivery model.

Use a short decision table before building a migration project​

The following table turns the lifecycle distinction into an operational triage tool. Complete it for each RDS collection, VDI pool, or published-application group rather than assigning one answer to the entire Server 2022 estate.

Environment	Office on shared session hosts?	Critical add-ins/profile tooling?	Recommended action	Owner	Deadline
Server 2022 file, print, or infrastructure workload	No	No	Retain under Windows Server 2022 Extended Support; assess on the server workload’s own lifecycle and risk plan	Infrastructure owner	Review before October 13, 2026
RDS or VDI pool with Microsoft 365 Apps	Yes	No or limited	Test and migrate Office delivery to a supported platform; validate sign-in, document access, and user experience	EUC/RDS owner	Complete before October 13, 2026
RDS or VDI pool with Microsoft 365 Apps and business-critical add-ins	Yes	Yes	Run a parallel pilot, test each dependency, and migrate in controlled waves with rollback capability	Application owner and EUC/RDS owner	Pilot early; complete before October 13, 2026
Published Office applications using Office LTSC 2021	Yes	Varies	Select and test a supported Office successor; do not treat LTSC 2021 as a way to extend the deadline	Desktop engineering and licensing owner	Complete before October 13, 2026
Server 2022 workload with no Office installed	No	No	Keep the Office deadline separate from the operating-system support plan	Infrastructure owner	No Office-driven migration deadline

The table is deliberately simple. It identifies where the October 2026 deadline applies, assigns responsibility, and prevents a broad Windows Server lifecycle discussion from obscuring the Office-specific work.

Inventory the session experience, not just the server version​

A standard server inventory will identify Windows Server 2022 hosts. It often will not reveal what makes a session-host migration difficult. Organizations should inventory the service users receive, not merely the operating system beneath it.
Create one record for each RDS collection, VDI pool, or application-publishing group. Record the host platform, Office edition, update arrangement, user population, published applications, business owner, and target deadline. Then capture the dependencies that commonly escape an operating-system report:

• Every Office add-in, particularly Excel, Outlook, Word, and PowerPoint add-ins tied to line-of-business systems.
• Profile tooling, user-data redirection, and settings-management components that affect Outlook state, Office preferences, and add-in availability.
• Application publishing components, remote-access agents, monitoring tools, endpoint-security agents, and printing dependencies installed on session hosts.
• Authentication and sign-in dependencies, including identity paths, conditional access requirements, and any MFA or device-compliance behavior users encounter.
• Licensing assumptions for Office, remote desktop access, shared computer use, and the method used to provide user sessions.
• Business processes that depend on specific macros, templates, document locations, or integrations.

This inventory distinguishes a routine server rebuild from a user-service migration. A lightly used RemoteApp application with no Office dependency may move quickly. A finance collection built around Excel add-ins, shared profiles, Outlook, specialized licensing, and tightly controlled document workflows may need a pilot long before any production cutover.
WindowsForum’s reporting on 2025 Microsoft 365 feature retirements repeatedly underscored this operational reality: administrators are usually not managing a retirement notice alone. They are managing the dependencies that have accumulated around the retiring feature or product. The same discipline applies here.

Office LTSC 2021 is a second deadline, not a fallback​

Replacing Microsoft 365 Apps with Office LTSC 2021 does not extend the planning window. Office LTSC 2021 reaches end of support on October 13, 2026, ending technical support, bug fixes, and security updates.
Microsoft identifies Microsoft 365 Apps for enterprise as the primary upgrade route for older Office migrations. Where that servicing model is not suitable, Office LTSC 2024 is the current volume-licensed alternative. The choice should be treated as an Office servicing and application-compatibility decision, not as a last-minute substitution intended to preserve an unchanged session-host design.
A fixed-license Office deployment may fit organizations that need stable functionality or cannot use Microsoft 365 Apps. Even then, the shared-session environment needs its own validation. Add-ins, document workflows, licensing, session concurrency, printing, authentication, and profile behavior can matter more than the Office product name.
Do not assume that an Office deployment that works on physical desktops will behave the same way on RDS or VDI. Shared environments concentrate the effects of sign-in policies, profile issues, add-in loading, and application publishing.

Rebuild when user-state and application risk are high​

A rebuild is often safer than attempting to preserve every element of a long-lived session-host stack. That is especially true where profile tooling, Office add-ins, published applications, authentication components, endpoint controls, and licensing rules have grown together over years.
A practical rebuild sequence is:

1. Select one representative RDS collection or VDI pool, including users who rely on the most important Office add-ins and published applications.
2. Turn the inventory into a dependency test list covering Office launch, sign-in, add-ins, document access, printing, profile continuity, and application publishing.
3. Build and test the candidate platform alongside the existing Server 2022 environment rather than modifying the only production host.
4. Define rollback before moving users, including the conditions that require users to return to the existing environment.
5. Move users in business-priority waves, beginning with groups whose workflows are well understood and whose owners can validate the result.
6. Retire or repurpose the old Office session hosts only after application owners confirm that critical processes work as expected.

The visible work may be the operating-system change, but the outage risk usually sits elsewhere: agents, profiles, add-ins, identity controls, and published applications. A migration plan that does not name those dependencies is not yet a migration plan.
Costs should be assessed at the same layer. A Server 2022 licensing comparison alone can miss testing effort, application repackaging, profile changes, remote-access tooling, dual-running costs, and business validation time. Conversely, organizations with few shared Office users may find that a targeted rebuild or a different delivery model is less expensive than preserving a specialized RDS design.

Retain Server 2022 where Office is not part of the workload​

Holding Windows Server 2022 is reasonable when the server is not delivering Office sessions and the workload can continue under Extended Support. Examples include infrastructure roles, file services, application servers, and other systems where Microsoft 365 Apps and Office LTSC 2021 are not installed or published.
That decision should still be documented. Identify which workloads remain on Server 2022, who owns them, how security updates will be managed, and what future event will trigger their eventual migration. Extended Support is continued servicing for the operating system, not a reason to stop maintaining an infrastructure roadmap.
For Office session hosts, however, the supported core distinction should remain clear: Windows Server 2022 can continue receiving security updates after October 13, 2026, while Microsoft 365 Apps support on Windows Server 2022 and Office LTSC 2021 support end on that date.

Frequently Asked Questions​

Does Windows Server 2022 become unsupported on October 13, 2026?​

No. Windows Server 2022 enters Extended Support on October 13, 2026 and continues receiving security updates. The date has a separate and more immediate impact on Office workloads hosted on Server 2022.

Must Microsoft 365 Apps be removed from Server 2022 by October 2026?​

Microsoft lists October 13, 2026 as the end of support date for Microsoft 365 Apps on Windows Server 2022. Organizations using Microsoft 365 Apps in RDS, VDI, or published-app environments should complete their supported-platform plan before that date.

Can Office LTSC 2021 solve the Server 2022 Office deadline?​

No. Office LTSC 2021 also reaches end of support on October 13, 2026. Organizations should evaluate Microsoft 365 Apps or, where appropriate for their licensing and servicing requirements, Office LTSC 2024.

Which environments should move first?​

Prioritize RDS, VDI, and application-publishing environments that use Microsoft 365 Apps or Office LTSC 2021, especially those with critical Office add-ins, complex profile tooling, sensitive authentication requirements, or specialized licensing dependencies.

Can ordinary Server 2022 workloads remain in place?​

They may be able to remain in place under Windows Server 2022 Extended Support if they are not dependent on the Office products reaching end of support in October 2026. Evaluate those workloads separately from the Office session-host estate.
October 2026 is therefore a design deadline for shared Office delivery, not a universal shutdown date for Windows Server 2022. The organizations best prepared for it will separate their Server 2022 inventory into Office and non-Office workloads, test the difficult session-host dependencies early, and assign a named owner to every migration decision.

---

References​

1. Primary source: learn.microsoft.com
   
   

   Overview - Product End of Support and Retirements - Microsoft Lifecycle | Microsoft Learn

   What 'end of support' means for a product.

   learn.microsoft.com
2. Independent coverage: microsoft.com
   
   

   Slide 1: Windows and Office configuration support matrix System requirements: https://www.microsoft.com/microsoft-365/microsoft-365-and-office-resources | Last updated: Oct 11, 2023

   PDF document

   www.microsoft.com
3. Primary source: WindowsForum
   
   

   2025 Tech Retirements: Windows 10 End of Life and More | Windows Forum

   2025 closed like a slow-motion exhale across the tech industry: a year when familiar software, experimental hardware, and long-lived services reached their...

   windowsforum.com