Windows Server 2016 End of Life: Refresh or Migrate?

The January 2027 deadline: what actually stops working

Windows Server 2016 leaves extended support on 12 January 2027, according to Microsoft's own Community Hub guidance. From that date, machines still running it stop receiving routine security updates, bug fixes and technical support unless they are covered by Extended Security Updates (ESU), per guidance cited by PolyU.

That is a hard stop, not a soft warning. For any UK organisation still running production workloads — domain controllers, file servers, line-of-business SQL instances, IIS applications — on Windows Server 2016 past that date without ESU cover, every subsequent vulnerability disclosed in the platform becomes permanently unpatched. Mid-2026 is the practical planning window: budgets, procurement cycles and staff time all need to be locked in well before the January cliff-edge, not during it.

Why this refresh cycle costs more than the last one

Every previous Windows Server refresh cycle assumed memory was a minor line item. That assumption breaks in 2026. DRAM contract prices rose 93–98% quarter-on-quarter in Q1 2026 according to exIT Technologies, and TrendForce forecast a further 58–63% QoQ rise in Q2 2026, driven — per CREATE PCs — primarily by AI datacentre demand pulling supply away from enterprise buyers.

There is a modest silver lining: Bernstein's TrendForce-sourced forecast puts Q3 2026 QoQ growth at a comparatively gentler 13–18%, suggesting the very steepest part of the curve may be behind us. But AI Weekly's analysis is blunt about the medium term: meaningful new DRAM supply isn't expected until late 2027 or 2028 at the earliest, so relief is a long way off.

On the ground, this shows up in real UK pricing. Servnet's own tracking shows an indicative ~5.3x rise in server memory pricing from Q3 2025 to Q3 2026, with a 32GB DDR5 kit that cost under £90 in late 2024 now sitting near £300. The knock-on effect reaches finished systems too — entry-level 14-inch business laptops have moved from around £650+VAT to close to £750+VAT over the same window. If your refresh plan assumes 2024-era hardware pricing, it's already wrong.

There's a strategic backdrop to this too: the UK government has designated data centres as critical national infrastructure, and the UK AI sector reached a combined market valuation of more than $518 billion in H1 2026 — roughly a third of the entire UK tech ecosystem, with UK AI start-ups raising over $11 billion in the same half. That domestic AI build-out is part of the same demand pulling memory prices up globally, which is worth knowing when you're asked to justify a bigger-than-expected hardware quote internally.

Three real paths — and what each one commits you to

Strip away the vendor pitches and there are three genuinely distinct options, each with a different cost shape and risk profile.

Refresh on-premises hardware and move to a currently supported OS. Microsoft's own Community Hub guidance recommends Windows Server 2025 specifically for the longest support runway. The cost hit here is largely capex, and it lands directly into the memory price spike described above — configuring new servers via a server configuration specialist rather than off-the-shelf SKUs is one way to control which components you're exposed to.

Buy Extended Security Updates and keep running Windows Server 2016 for up to three more years, per Choice Solutions. This converts a capex problem into an opex one, but it is not a static cost — see the next section.

Migrate workloads to Azure. Note that Windows Server 2016 falls under the consistent ESU pricing model Microsoft introduced on 1 April 2026, under which customers pay the same list price for ESUs regardless of deployment location (Azure, on-premises or other public clouds) — so running Windows Server 2016 in Azure does not by itself remove the ESU bill; upgrading to a supported OS does. Combined with Azure Hybrid Benefit, which lets you apply existing on-premises Windows Server licences to Azure VMs at reduced (Linux-equivalent) rates, Microsoft cites savings of up to 80% — though the exact figure depends on instance type, region and whether it's stacked with other offers like Reserved VM Instances.

ESU economics: the bridge that gets more expensive every year you use it

ESU is licensed per core, not per server, and the minimums matter: at least 8 cores per processor and 16 cores per server for physical licensing, or a minimum of 8 cores per VM for virtual licensing, per Microsoft Q&A guidance. That structure alone rules out ESU as a cheap option for anything beyond a small, low-core-count estate.

The more important detail is that ESU is cumulative. SCHNEIDER IT MANAGEMENT is explicit on this: licences are purchased on a yearly basis, and enrolling late means paying for every prior year of coverage as well as the current one. There is no way to skip Year 1 and buy only Year 2 cheaply — the clock starts at the EOL date whether you've paid for it or not.

Don't assume Azure removes this cost: Windows Server 2016 is covered by the consistent ESU pricing model Microsoft introduced on 1 April 2026, under which customers pay the same list price regardless of deployment location or purchasing channel. The ESU budget is best compared against the cost of upgrading or refreshing — worth modelling properly in an IT finance calculator before committing to a multi-year ESU contract.

• •ESU minimums: 8 cores/processor and 16 cores/server (physical) or 8 cores/VM (virtual)
• •Cumulative pricing: late enrolment means back-paying for skipped years
• •From 1 April 2026, Windows Server 2016 ESUs carry the same list price in Azure, on-premises or other clouds
• •Maximum ESU runway is three years beyond the 12 January 2027 end-of-support date

Windows Server 2022 vs 2025: what's verified, and what to check yourself

Microsoft's stated position is unambiguous: the Community Hub guidance recommends upgrading straight to Windows Server 2025 for the longest support runway rather than treating Windows Server 2022 as an interim stop. If you're refreshing hardware anyway during 2026, landing on 2016-era infrastructure twice — once now on 2022, once again in a few years on 2025 — is an avoidable second migration project.

On pricing, two verified UK figures exist here, both from TrustedTech: Windows Server 2022 Standard with a 16-core licence retails at £669.99, and Windows Server 2025 Standard with a 16-core licence retails at £763.99. That gap is worth building into any comparison — but it covers only that specific edition and core count from that specific vendor, so treat any other configuration (Datacenter edition, different core counts) or any other vendor's quote as needing independent verification against your own supplier before it goes into a budget line.

Whichever version you land on, sourcing decisions still matter more than the OS choice for controlling total cost in a memory-inflated market — a Dell server configurator, HPE server configurator or Lenovo server configurator comparison, alongside refurbished servers as a lower-DRAM-exposure option for less latency-sensitive roles, are both worth running before signing off a refresh.

Which path fits your organisation

There's no single right answer, but the decision variables are consistent across UK organisations of every size.

If your estate is small, core counts are modest, and you're not already running Azure, ESU's per-core minimums and cumulative pricing make it a poor long-term fit — a hardware refresh, cushioned by sourcing refurbished units for less critical roles, is likely to be the more predictable spend even with DRAM prices elevated.

If you already run production workloads on Azure, migrating the remaining Windows Server 2016 instances there and upgrading them to a supported OS removes both the hardware refresh capex and the ESU bill — staying on Windows Server 2016 in Azure still needs paid ESU cover under Microsoft's April 2026 pricing model — and lets you apply Azure Hybrid Benefit against existing licences you've already paid for.

If you have applications with hard on-premises or data-residency constraints that rule out cloud migration entirely, ESU is your only lawful bridge — but budget for it as a cumulative, per-core cost across up to three years, and use that budgeted period to run the hardware refresh project in parallel rather than sequentially.

Pre-migration checklist for UK IT teams

Whichever path you choose, the same groundwork applies before you touch a production domain controller or line-of-business server.

Start by inventorying every Windows Server 2016 instance against its role, core count and current Azure eligibility — that single spreadsheet determines whether ESU minimums, an Azure migration, or a straight refresh is even mathematically viable for each workload. Then price the memory component of any hardware quote separately, given how sharply DRAM contract pricing has moved through 2026 — a quote that bundles memory into a flat server price can hide exactly the cost spike you need to see.

• •Map every Server 2016 instance to role, core count and Azure/on-prem status
• •Check Software Assurance or qualifying subscription status before assuming Azure Hybrid Benefit applies
• •Separate the memory line item on any refresh quote given current DRAM contract pricing
• •Model ESU as a cumulative, multi-year cost — not a single annual fee — before comparing it to refresh capex
• •Confirm ESU costs for workloads already in Azure — Windows Server 2016 ESUs carry the same list price there as on-premises

Beyond Microsoft: hybrid routes worth weighing

Many UK organisations are making this decision at the same time as a separate, related one: what to do about VMware licensing following Broadcom's changes to that ecosystem. If your Windows Server 2016 estate runs on VMware infrastructure, it's worth reviewing both decisions together rather than solving them in isolation — our guide to VMware alternatives covers that adjacent choice.

Azure-adjacent platforms — Dedicated Host, VMware Solution, Nutanix Solution, Azure Local, and Stack Hub/Edge — are themselves a form of hybrid route: they let you keep workloads in familiar environments without a full application rewrite, though Windows Server 2016 instances on them still need ESU cover, which Microsoft now prices the same regardless of deployment location. For organisations not ready to commit to a full cloud migration or a full hardware refresh in the same financial year, that combination is worth exploring properly with an engineer who can map it against your specific estate — talk to a Servnet engineer before the January 2027 deadline closes the easier options off.

Sources

Every figure in this article traces to the sources below.

• •Microsoft Community Hub — Windows Server 2016 extended support end date and 2025 upgrade recommendation
• •PolyU — impact of end of extended support on updates and technical support
• •Choice Solutions — ESU covering up to three additional years
• •SCHNEIDER IT MANAGEMENT — ESU cumulative yearly licensing structure
• •Microsoft Q&A — ESU per-core minimums; Microsoft Azure Arc Blog — consistent ESU pricing model covering Windows Server 2016
• •exIT Technologies — DRAM contract price rise Q1 2026
• •TrendForce — Q2 2026 DRAM price forecast
• •Bernstein / TrendForce — Q3 2026 DRAM price moderation forecast
• •AI Weekly — timeline for new DRAM supply
• •CREATE PCs — AI datacentre demand as memory price driver