Windows Server 23H2 AC: EOL Action Plan (Oct 24, 2025)

The Clock Is Ticking: Windows Server 23H2 AC Ends on October 24, 2025

Microsoft Windows Server 23H2 AC (Azure Channel) reaches end of life on October 24, 2025. With roughly three months left, a full migration to a supported release before that date is no longer realistic for most estates. That doesn’t mean you should do nothing. This article provides a last-call action plan to inventory, isolate, and document your exposure, and to secure a support contract for day one after EOL.

What Actually Changes on October 24, 2025?

When a Windows Server release exits support, the following happens:

• No more security patches. Microsoft will not release any new updates for Windows Server 23H2 AC after October 24, 2025.
• No more bug fixes or hotfixes. Any non-security issues will not be addressed by Microsoft.
• No vendor SLAs. If you have a Microsoft support agreement that covers this version, it will no longer apply. You cannot open a support case for this OS.

This is not an LTS (Long-Term Servicing) release. The latest build in this line is 10.0.25398. After October 24, running this version exposes your infrastructure to unpatched vulnerabilities and compliance gaps.

Your Last-Call Action Plan (Week by Week)

Given the time left, the goal is to reduce risk and document your position for auditors and insurers. Full migration is not the only path; third-party support can keep a secure posture after the vendor’s cutoff.

Week 1: Inventory all affected systems

• Identify every server running Windows Server 23H2 AC. Use your CMDB, AD, or a scanning tool.
• Record the role of each server (e.g., file server, domain controller, application host).
• Note which servers are internet-facing, which are internal, and which hold sensitive data.

Week 2: Assess migration feasibility and prioritise

• For each server, determine if an in-place upgrade to a supported release (e.g., Windows Server 2022 or 2025) is possible. Check application compatibility.
• If no upgrade path exists, can the workload be moved to a newer OS or to Azure?
• If migration is not viable before October 24, label the server as “staying on 23H2 AC after EOL.”

Week 3: Isolate and harden remaining servers

• Place servers that cannot be migrated into a separate network segment with strict firewall rules.
• Disable unnecessary services, ports, and protocols.
• Apply the latest available patches today (before EOL). There will be no more after October 24.
• Enable enhanced logging, monitoring, and alerting for these systems.

Week 4: Document exposure for auditors and insurers

• Create a formal inventory of all servers that will remain on Windows Server 23H2 AC after October 24.
• Document the business justification for each (e.g., application dependency, vendor support delay).
• Note the risk acceptance and any compensating controls (isolation, monitoring, etc.).
• Share this documentation with your compliance, risk, and insurance teams.

Week 5: Secure a support contract for day one after EOL

• Third-party maintenance providers can extend security patching and support for Windows Server 23H2 AC beyond Microsoft’s end-of-life date.
• Evaluate providers that offer hotfixes, vulnerability patches, and vendor-agnostic support for this version.
• Finalise a contract that covers October 24, 2025, onward — ideally signed before the EOL date to ensure continuity.

Why Third-Party Support Makes Sense Here

When Microsoft stops supporting a Windows Server release, third-party support keeps you protected. A provider like 3rd Party Support can deliver custom patches, security updates, and technical assistance for the exact version you’re running (10.0.25398). This buys you time to plan a controlled migration without rushing into a risky upgrade window.

For more details on the lifecycle of Microsoft Windows Server, see the vendor page on our site. The official lifecycle source is endoflife.date/windows-server.

Next Steps

Time is short. Begin your inventory today. If you need help evaluating extended support options, contact us to discuss a third-party maintenance agreement that fits your timeline.

Make sure your systems are not left exposed on October 25, 2025. Act now.