Windows Server 2016 and 2019 End of Life: Dates, ESU Costs and Your Options
Windows Server 2016 support ends Jan 12, 2027 and 2019 ends Jan 9, 2029. See every end of life date, ESU costs and eligibility, and your upgrade options.

Windows Server 2016 reaches end of life on January 12, 2027, and Windows Server 2019 follows on January 9, 2029. Windows Server 2012 and 2012 R2 are already done. Their last paid Extended Security Update shipped on October 13, 2026.
If 2016 still runs in production, one decision stands between you and January: buy Microsoft's Extended Security Updates (ESU) through Azure Arc, or move the workload. The ESU rules changed in 2026.
Two assumptions I relied on during the 2012 cycle no longer hold. ESU now costs the same in Azure as on-premises, and the price holds flat across all three years.
What follows is the decision that comes before the mechanics: the dates, what ESU costs and who qualifies, and which path fits which workload. The mechanics themselves live in our technical guide on planning a Windows Server upgrade or move to Azure.
Windows Server End of Life Dates for Every Supported Version
Windows Server 2016 extended support ends January 12, 2027, with paid ESU available through January 2030. Windows Server 2019 ends January 9, 2029, and Windows Server 2022 ends October 14, 2031. Windows Server 2025 is the only version still in mainstream support. Support for 2012 and 2012 R2, including ESU, ended October 13, 2026.
These are the dates Microsoft publishes on its lifecycle pages. Microsoft lists each end time as 6:59:59 AM Pacific on the following day, which is midnight UTC. Plan around the calendar date in the table.
The timeline below puts all five versions on one axis. Mainstream support is gold, security-only extended support is gray, paid ESU is hatched, and the red line marks today. Look at where the red line crosses each bar.
If you track deadlines across more than Windows Server, our 2027 end-of-life calendar puts every major vendor date in one place.
Mainstream Support vs Extended Support vs ESU, in Plain Words
Microsoft's Fixed Lifecycle Policy gives each Windows Server release three phases. Each one gives you less than the one before.
One date catches people off guard. Windows Server 2022 left mainstream support on October 13, 2026. A server you upgrade to 2022 today lands in security-only support on its first day.
Windows Server 2016 End of Life: What Changes on January 12, 2027
After January 12, 2027, Microsoft stops shipping security updates for Windows Server 2016 unless the server is enrolled in paid ESU. The server keeps booting and serving users. New vulnerabilities stay open, Microsoft support cases end, and auditors start treating the server as an exception you have to justify.
An unsupported server does not stop working on the deadline. That is what makes it dangerous. It keeps running, so the risk stays invisible until something forces it into view.
After extended support ends, Microsoft stops issuing security updates. Extended Security Updates cover only Critical and Important security fixes, and they explicitly exclude new features, non-security hotfixes, and design changes.
So an unsupported box accumulates unpatched vulnerabilities with no vendor path to close them and no support line to call when it breaks.
Two exposures grow the longer the server stays in production:

Compliance and Cyber Insurance Exposure on an Unsupported OS
PCI DSS v4.0 added Requirement 12.3.4, mandatory since March 31, 2025. It requires a review of your hardware and software at least every 12 months, a record of vendor end-of-life announcements, and a remediation plan for end-of-life technology approved by senior management.
Requirement 6.3.3 sets a one-month window to install critical security patches. A 2016 server without ESU fails that test the first time Microsoft ships a critical fix it can't receive.
HIPAA's Security Rule works through risk analysis instead of naming operating systems. An unpatchable server that holds ePHI belongs in that analysis, with a documented mitigation or a retirement date next to it.
Cyber insurance comes down to what you attested to. If your last application said you run no unsupported operating systems, that answer changes on January 13, 2027. Read the questionnaire before your renewal, then fix either the estate or the answer.
Software and Agent Support Drop-Off on Windows Server 2016 and 2019
Application vendors drop old operating systems on their own schedules, often before Microsoft does. Microsoft itself is an example: Microsoft 365 Apps get security updates on Windows Server 2016, 2019 and 2022 only until October 10, 2028.
For a Remote Desktop host on 2019, that means Office stops getting security fixes three months before the operating system does. At some point a business application you need will not certify or install on Server 2016, and the upgrade you deferred becomes a blocker to work that has to get done.
Windows Server 2016 Extended Security Updates: Cost, Eligibility and How to Buy
Windows Server 2016 ESU delivers Critical and Important security updates for up to three years, through January 2030. Microsoft sells it through Azure Arc as a monthly per-core charge. You need Software Assurance, a SPLA license or a Server Subscription. Since April 1, 2026, the list price is the same in Azure and on-premises.
Buying Windows Server 2016 ESU Through Azure Arc: Requirements and Billing
Microsoft opened 2016 ESU configuration through Azure Arc on August 3, 2026, and billing starts January 13, 2027. The setup is light, but a few rules carry real cost if you miss them.
The rule that matters most is back-billing. A license you create after January 12, 2027 is billed back to that date, and Microsoft does not waive it. Waiting until February saves nothing. It only moves the whole charge into one invoice.
Microsoft's retail price list sets the Azure Arc ESU meters for Windows Server 2016 at $0.007132 per core-hour for Standard and $0.041067 per core-hour for Datacenter, effective August 1, 2026. Over a full year, that comes to $62.48 per Standard core and $359.75 per Datacenter core.
In practice, a 16-core Standard host costs about $1,000 a year to keep patched, and a 16-core Datacenter host costs about $5,756. A Standard license on a physical host covers up to two VMs. Datacenter covers every VM on the host, which is where the higher rate earns its keep.
Windows Server 2016 ESU in Azure: Same List Price as On-Premises
For 2012 R2, moving a server into Azure made ESU free. I used that lever, and so did most of the teams I compared notes with. It does not carry over to 2016.
Microsoft's March 27, 2026 licensing update set one list price for ESU offerings released from April 1, 2026, wherever the server runs (Azure, on-premises or another cloud) and whichever channel you buy through. Microsoft's Azure Local documentation names Windows Server 2016 as covered by the change.
That rewrites the old advice. Rehosting a 2016 server to an Azure VM still gets aging hardware off your risk list. It no longer cuts the ESU bill, and moving SQL Server to an Azure VM no longer brings free Windows Server updates with it.
Is Windows Server ESU Worth It? When to Buy vs Migrate
ESU has a legitimate use. It buys clean time when you have a short, funded runway to a known target, a legacy application mid-remediation, or a workload already scheduled to move inside the ESU window. Used that way, it is a bridge.
It becomes money burned when it substitutes for a plan. The per-core price stays flat, so the bill itself doesn't climb. Everything around it does: application vendors dropping support, audit findings, and another year of age on the hardware underneath.
ESU also ends in January 2030 whatever you decide, so every month you buy only delays a migration you still have to run.
The emergency premium is the real cost. The scenario that ends most of these delays is not a budget review. It is an unpatched server that gets breached, or aging hardware that fails with no vendor left to restore it, taking every system that depends on it down with it.
At that point the migration still happens. It just happens at 2 a.m., under incident conditions, at a multiple of the planned cost, on the attacker's or the hardware's timeline instead of yours.
That is the difference between a project and a crisis. The technical work is nearly identical. The cost, the risk, and the control are not.

The calculator below shows where the bridge stops paying for itself. Enter your host or VM count, cores and edition, the months you expect to need, and your one-time migration quote. It returns ESU spend by year and the month where cumulative ESU passes the cost of moving.
Windows Server 2019 End of Life: January 9, 2029
Windows Server 2019 left mainstream support on January 9, 2024 and receives security updates only until January 9, 2029. Microsoft has not announced Extended Security Updates for 2019. If it does, the April 2026 pricing rules mean the same list price in Azure and on-premises.
What Security-Only Support Means for Windows Server 2019 Today
Since January 2024, 2019 has received monthly security updates and nothing else. A driver problem, a performance bug or a missing feature in the OS stays as it is. Windows Server 2022 joined it in the same position on October 13, 2026.
Will Windows Server 2019 Get ESU?
As of November 2026, Microsoft has announced nothing. For 2016, the ESU announcement came in February 2026, less than eleven months before extended support ended. If Microsoft follows that pattern for 2019, a decision would surface in early 2028.
I wouldn't put money in a budget for an offer that doesn't exist yet. Plan the 2019 exit around January 9, 2029.
Plan Windows Server 2019 Upgrades With Your 2016 Project or Wait?
Bundle the 2019 servers that share risk with your 2016 servers. Leave the rest for a later wave.
Either way, target 2025. An upgrade from 2019 to 2022 lands on another security-only release.
Windows Server 2012 and 2012 R2 End of Life: After ESU Ended
Microsoft shipped the final Windows Server 2012 and 2012 R2 Extended Security Update on October 13, 2026. Azure Arc ESU licenses for 2012 deactivated at midnight UTC on October 14. Microsoft has offered no fourth year, so any 2012 server still running receives no security fixes at all.
The deactivated license resources stay visible in the Azure portal, but they can't enroll servers or deliver updates. If you still run 2012 R2, three moves matter this quarter.
Windows Server Upgrade Paths From 2016 and 2019 to 2022 or 2025
Windows Server 2016 and 2019 both upgrade in place directly to 2022 or 2025 on standalone servers. 2012 R2 goes directly to 2025, but not to 2022. Failover clusters move one version per rolling upgrade, so a 2016 cluster needs three passes to reach 2025. Each upgrade needs a license for the target version.
If you are going to move, move somewhere with runway. Landing on 2019 or 2022 spends the migration effort on a platform that is already in security-only support.
Target Windows Server 2025 or Azure. Keep 2022 as the fallback for applications whose vendors haven't certified 2025 yet, and know that it puts you in security-only support from the day you land.
Use the checker below to see whether Microsoft supports a direct in-place upgrade from your current version, and the shortest route when it doesn't. Flip the cluster option to see how many rolling passes a failover cluster needs.
In-Place Upgrade vs Clean Install vs Move to Azure
In-place is fastest when it applies. Since Windows Server 2025, standalone servers can jump up to four versions in one upgrade, and Microsoft now delivers in-place upgrades as a feature update through Windows Update as well as from media.
A clean install wins when the hardware is out of warranty or the server has years of configuration drift you'd rather leave behind. If the host OS is part of a hypervisor decision, our Hyper-V vs VMware vs Nutanix comparison covers that choice.
Moving to Azure makes sense when you want out of the hardware cycle altogether, or when a data center lease is ending. For 2016 it no longer saves ESU money, so judge it on run cost and operations. Our roundup of cloud migration services covers the partners who do this work.
Windows Server Migration Options by Workload
There is no single right answer for the whole estate. Microsoft defines five migration methods, and each one fits a different situation.
In-place carries hard restrictions that break real migrations if you ignore them:

Mapped to real workloads, the defaults look like this. They apply to 2019 servers as well as 2016.
The mechanics of each of these paths, from Azure Migrate to FSMO transfers, are covered step by step in the Windows Server upgrade and Azure migration guide. If part of this estate is identity infrastructure, our guide on migrating from on-prem Active Directory to Microsoft Entra ID covers the identity side in depth.
If your 2016 session hosts serve VDI users, our guide to moving to Azure Virtual Desktop or Windows 365 covers that path.
Should You Upgrade Windows Server In-House or Hire a Migration Partner?
Run it in-house when the conditions line up: standalone servers, supported in-place paths, staff who have done Windows Server migrations recently, downtime tolerance that fits a maintenance window, and a timeline with real slack before the deadline.
Bring in a partner when any of these are true:
A good migration partner does the work in-house teams under-scope: full dependency mapping before touching anything, a documented rollback plan for every workload, and a per-workload path decision instead of a blanket approach.
If the real gap is ongoing capacity rather than this one project, hiring a managed service provider may solve more than the migration.
How to Choose a Windows Server Migration Partner
Not every partner is worth hiring. Evaluate on the parts that protect you when something goes wrong.
The same discipline you would apply to any technology purchase applies here. Our IT vendor selection criteria and checklist and best practices for the vendor selection process both apply directly to choosing a migration partner.
Windows Server End-of-Support Checklist
You do not need the whole plan today. You need to convert an open-ended risk into a scoped project.
Work through the checklist below. It follows the order I'd use on a real estate, and your progress stays saved in your browser.
Find a Windows Server Migration Partner Before the Deadline
A server that no one migrated gets breached, or the aging hardware under it fails with no support contract left, and suddenly the systems your business runs on are down with no clear way back. The migration you kept deferring still happens. It just happens as emergency recovery, at a premium, on the worst possible night.
The calmer version starts now, while the servers are still running and the choice is still yours. You scope the estate, decide the path per workload, and line up help for the parts that carry real risk.
That last step is where finding the right partner matters, and where it usually gets slow. TechnologyMatch connects you with pre-vetted Windows Server and cloud migration vendors matched to your workloads, timeline, and compliance requirements, so you can compare options and start conversations without weeks of cold research. Match with vendors who fit your situation, and reach out when you're ready.
Also read: Windows 10 ESU Year 2: What It Costs Now, and When Replacing the PC Is Cheaper
Get Help with Your Migration
TechnologyMatch lets you find pre-vetted Windows Server and cloud migration vendors based on workloads, compliance requirements, and deadline, so you skip weeks of cold research and start conversations with vendors who actually fit. Match with the right ones, and reach out when you're ready.
FAQ
Is Windows Server 2016 still supported?
Yes, until January 12, 2027. It has received security updates only since mainstream support ended on January 11, 2022. After January 12, the only way to keep getting security patches is paid Extended Security Updates through Azure Arc, available through January 2030.
How long will Windows Server 2019 be supported?
Until January 9, 2029. Mainstream support ended January 9, 2024, so 2019 receives security updates only. Microsoft has not announced Extended Security Updates for 2019.
How much do Windows Server 2016 ESUs cost?
Microsoft's Azure Arc meters charge $0.007132 per core-hour for Standard and $0.041067 for Datacenter, effective August 1, 2026. That is about $62 per Standard core and $360 per Datacenter core per year, with minimums of 16 cores per physical server and 8 per VM. The price stays flat across all three years.
Can I get Windows Server 2016 ESU without Azure Arc?
Microsoft built the 2016 program around Azure Arc. The main exception is VDI, where Microsoft directs you to Multiple Activation Keys through Volume Licensing. Volume Licensing ESU for 2016 can't transition to Arc later, so choose the route per server group up front.
Are ESUs free in Azure?
For Windows Server 2016, no. Since April 1, 2026, Microsoft charges the same list price for new ESU offerings in Azure, on-premises and in other clouds. The free Azure ESU that applied to 2012 and 2012 R2 ended with that program on October 13, 2026.
Can you upgrade Windows Server 2016 directly to 2025?
Yes, on standalone servers. Windows Server 2025 accepts in-place upgrades of up to four versions, so 2016 and 2019 go directly to 2025. Failover clusters move one version per rolling upgrade, so a 2016 cluster needs three passes. Domain controllers and certificate authorities are safer to migrate than to upgrade in place.
What is the difference between Windows Server 2019 and 2022 support?
Both now receive security updates only. 2019 entered that phase on January 9, 2024 and ends January 9, 2029. 2022 entered it on October 13, 2026 and ends October 14, 2031, which gives it almost three more years of patches.
What happens to Windows Server 2012 R2 now that ESU has ended?
It receives no security updates of any kind. The last ESU update shipped October 13, 2026, and Azure Arc ESU licenses deactivated the next day. Isolate any 2012 R2 server still running, then upgrade it in place to 2025, migrate its roles, or retire it.
What happens if we don't upgrade Windows Server 2016?
It keeps running after January 12, 2027, but newly disclosed vulnerabilities stay open, Microsoft support cases end, and PCI DSS assessments will expect a dated, approved remediation plan. Application vendors also drop support over time. Paid ESU buys up to three years of security patches and ends in January 2030.


