Windows Server 2016 ends on 12 January 2027 with no published ESU price

The date is fixed and the price is not

Windows Server 2016 Standard and Datacenter reach the end of extended support on 12 January 2027. Microsoft's lifecycle page carries that date, and after it the update stream stops for the operating system: no security bulletins, no new features, no non-security hotfixes. Extended Security Updates add up to three years of critical and important patches on top, which moves the final patch to 2030 rather than 2027.

What Microsoft has not published is the price. The Register reported in February 2026 that the company confirmed the three-year programme while staying quiet on Server 2016 pricing. The precedents on the record are harder: for Windows Server 2012, Microsoft said year one of ESU was charged at 100 per cent of the full licence price, and for SQL Server 2016 the programme starts at 75 per cent of the full annual licence and rises each year after that. A budget built on either figure is a range, not a quote.

The 2012 programme is the closest thing to a dry run, and it closed on 13 October 2026 after three years. Every Server 2012 and 2012 R2 host still in service is now outside support entirely, which is the state a Server 2016 estate reaches in 2030 if the workload does not move.

Software Assurance is the gate, not the delivery tool

Azure Arc is how the updates are delivered and billed monthly, which is not the same as how the entitlement is earned. For on-premises Windows Server 2016, Microsoft requires active Software Assurance or an equivalent server subscription whether or not Arc does the delivery, and the Services Provider License Agreement is not available for this programme. An estate that bought OEM licences and never carried SA cannot close that gap with an onboarding project, however well the Arc agent installs.

Arc also assumes the machine can reach Azure regularly. Segmented production networks and isolated plant have to settle which delivery path is technically possible before the commercial question is worth answering, because a disconnected host on a paid ESU licence still needs something to patch it.

Budget approval follows the same order. A business case that lists ESU as a line item without the Software Assurance line underneath it will not survive a licence review, and a review that happens in December will not finish before the January date.

Where the free-ESU assumption breaks

Microsoft introduced a location-independent pricing rule for new ESU offers on 1 April 2026, and the Azure Local documentation lists Windows Server 2016 as a paid case. Other Microsoft pages still describe ESU for Azure virtual machines and Azure VMware Solution as free of charge. Until those statements converge, moving the workload does not settle the cost, and a business case that assumes free patches in Azure is standing on a page that may be revised.

That ambiguity is the most expensive line in the programme, because the same virtual machine can be priced as an entitlement, a subscription or a paid add-on depending on where it runs. The estate inventory is the only evidence that counts here.

Three exits and the number that decides each

The choice is rarely ESU against migration on price alone. It is whether the estate can absorb an operating system change before the 2030 ceiling, and what has to be true on the licence side for each route.

What else stops on the same date

Windows Server 2016 is not alone. Hyper-V Server 2016, Windows Storage Server 2016, Windows Server Update Services, Windows Defender, IIS 10 and .NET Framework 4.6.2 all reach end of support with it, and the System Center 2016 family, Operations Manager and Virtual Machine Manager among them, stops one day earlier.

This matters because a WSUS role or an old IIS host is often the reason a Server 2016 machine is still in the rack. Replacing the operating system without a home for that role produces a supported server with nothing left to do. Walking the dependency list against the estate is worth a morning, because WSUS and .NET Framework 4.6.2 usually appear in the same ticket as the upgrade and nobody has budgeted for either.

The upgrade path that works, and the one that does not

Since Windows Server 2025, nonclustered systems can jump up to four versions in place, so a Server 2012 R2 host can move straight to 2025 with roles, settings and data carried across. Domain controllers are the exception: Microsoft recommends building and promoting new controllers and demoting the old ones, and Windows Server 2025 requires forest and domain functional levels of at least Windows Server 2016.

Windows Server 2025 pushes the next deadline out, with mainstream support to 13 November 2029 and extended support to 14 November 2034. Hotpatching costs nothing extra on Arc-managed servers, but it needs build 26100.1742 or later, UEFI with Secure Boot, virtualization-based security and a generation 2 virtual machine under Hyper-V.

Clusters fall outside the four-version jump. A Hyper-V or failover cluster has its own upgrade path, and the sequence has to be designed around the cluster rather than around a single maintenance window, which is the step that slips in most plans.

The decision rule follows the licence rather than the workload. If Software Assurance is current and the role inventory is clean, buy ESU for the hosts that cannot move this year and upgrade the rest to Windows Server 2025. If SA is missing, ESU is not available at any price, and the only remaining question is which hardware and which roles get rebuilt first. Either way, place the order in November, because Microsoft says a Multiple Activation Key takes three to five business days to become available.