ModernEndpoint

Four Microsoft End-of-Support Dates Converge This October

menahem suissa

menahem suissa

— 16 min read
Share
Governance

Four Microsoft End-of-Support Dates Converge This October

Most IT teams track end-of-support dates one product at a time. This October, four converge at once — and at least one of them is easy to miss because it doesn't look like an end-of-support event at all.

4 min read WindowsMicrosoft 365Lifecycle

What's actually ending

Office 2021, Project 2021, and Visio 2021 all reach end of support in October 2026. Windows 11 24H2 exits its serviced lifecycle for consumer and Pro editions the same month. And Windows Server 2012 / 2012 R2 hits the end of its third and final year of Extended Security Updates — the paid safety net Microsoft sold specifically to buy organizations time past the 2023 extended-support cutoff.

None of these are edge cases. Office 2021 shipped as the perpetual-license alternative to Microsoft 365 for exactly the organizations that don't want subscription billing — which usually means the ones with the least appetite for frequent migrations. Windows Server 2012 still runs production workloads in more environments than anyone likes to admit. If your organization bought ESU for it in 2023, this October is the deadline you paid to postpone.

Warning

End of support means end of security updates. Everything else about these products keeps working exactly as before — which is the whole problem. Nothing visibly breaks on the cutoff date. The exposure just stops getting patched.

Office, Visio, Project 2021 — what changes and what doesn't

These are perpetual-license products, not subscriptions, so nothing gets uninstalled and no license expires. What ends is Microsoft's obligation to ship security fixes for newly discovered vulnerabilities. An unpatched Office 2021 install in October 2026 is functionally the same risk profile as an unpatched Windows XP box was in its final years — it works fine until it's the entry point in an incident report.

The practical fix is licensing, not engineering: move affected users to Microsoft 365 Apps or the current LTSC channel. The harder part is finding out who's still on 2021 in the first place, since perpetual licenses don't show up in the same telemetry subscription seats do.

Windows 11 24H2 — the one that's easy to miss

This isn't a product retirement — it's a servicing-channel boundary, and that distinction is exactly why it gets missed. Home and Pro editions of 24H2 get a shorter serviced window than Enterprise and Education editions of the same build. A fleet running mixed editions can have some machines quietly age out of security updates while others on the identical OS build keep receiving them, with no obvious signal that anything changed.

Confirm which edition each device is actually running before assuming 24H2 coverage extends further than it does. Feature-update version alone doesn't tell you the support end date — edition does.

Windows Server 2012 — the ESU cliff

Extended Security Updates were always a countdown, not a reprieve. Year 3 ending this October means the ESU purchase your organization made in 2023 — treating this as "three more years to migrate" — reaches its actual deadline now, not later. There is no Year 4 to buy. Any workload still on 2012 or 2012 R2 after this window closes runs on an OS Microsoft will never patch again, on purpose, permanently.

If migration hasn't already started, October isn't a planning deadline anymore — it's a cutover deadline.

What to actually do this week

  1. Inventory before you plan. Pull real numbers on Office 2021 seats, 24H2 edition mix, and any Server 2012/2012 R2 instances — don't estimate from memory.
  2. Prioritize Server 2012 first. It's the only one of the four with zero further extension available at any price.
  3. Treat 24H2 as an edition audit, not a version check. Confirm Enterprise/Education vs Home/Pro on every device before assuming coverage.
  4. Move Office 2021 holdouts to a subscription or current LTSC channel — the migration path is licensing, not a technical blocker.

Final thoughts

Every one of these four dates was known years in advance. What makes them worth a single article instead of four separate reminders is that they land in the same month, and the one most likely to get missed — 24H2's edition-dependent window — is also the one with no dramatic announcement attached to it. The Server 2012 ESU deadline is loud because organizations paid money for it. The Office 2021 deadline is loud because it's a well-publicized product retirement. The 24H2 edition boundary is quiet, which is exactly why it's worth checking this week instead of assuming it's someone else's problem.

Read more