Quick answer: Windows Server 2016 reaches the end of extended support on 12 January 2027. Mainstream support ended on 11 January 2022. After the end date there are no more routine security updates, bug fixes or assisted support unless the server is enrolled in paid Extended Security Updates (ESU), which Microsoft offers through Azure Arc for up to three years. Microsoft recommends moving to Windows Server 2025.
If a Windows Server 2016 machine still runs file shares, Active Directory, Exchange, SQL or line-of-business software in your company, the date to plan around is 12 January 2027. The server will keep running on 13 January, but it stops receiving standard security fixes. This guide sets out what ends, what ESU costs you in practice, and a short plan to decide per server.
Key dates
| Milestone | Date |
|---|---|
| Mainstream support ended | 11 January 2022 |
| Extended support ends (end of life) | 12 January 2027 |
| ESU licences configurable in the Azure portal | 3 August 2026 |
| Azure Arc ESU generally available | 6 August 2026 |
| ESU billing starts | 13 January 2027 |
| Latest ESU coverage ends | January 2030 |
Some lifecycle pages print the end as an early timestamp on 13 January because of time zones. The official end date is 12 January 2027, Pacific time.
What stops on 12 January 2027
Since January 2022 the server has received security fixes only. After the end date Microsoft provides no security updates, no non-security updates and no free or paid assisted support for the product under the standard lifecycle. The same date applies to the rest of the 2016 family: Hyper-V Server 2016, IIS 10 on Windows Server 2016, WSUS for Windows Server 2016 and .NET Framework 4.6.2, according to one migration guide.
A new vulnerability found after that date stays unpatched on a standard 2016 server. For machines that hold customer data, take payments or expose remote access, that is a compliance and insurance question as well as a technical one.
Extended Security Updates: what is actually on offer
- Coverage: Critical and Important security updates only, for up to three years after 12 January 2027. No new features and no full product support.
- Editions: Standard and Datacenter.
- How to buy: through Azure Arc, billed monthly per core, or through volume licensing, billed annually.
- Late enrolment: one provider notes that licences set up after the end-of-support date are back-billed to 13 January 2027, with no waiver.
- Price: Microsoft’s pages we checked did not give a single list price, and commentary disagrees on how steeply year two and year three rise. Ask your Microsoft partner for a quote for your core count.
Earlier versions of this page said that ESU might not exist for Server 2016. That is out of date. Microsoft announced the programme in February 2026 and made the Azure Arc version generally available in August 2026.
Your options
| Option | Best when | Watch out for |
|---|---|---|
| Upgrade to Windows Server 2025 | The application supports it | Licensing, driver and application compatibility |
| Migrate or rebuild the workload (new server or cloud) | The old server can be retired | Data migration and downtime planning |
| Buy ESU as a bridge | An app cannot move before January 2027 | Recurring cost, and the server still ages |
| Do nothing | Rarely, for isolated test machines | Unpatched vulnerabilities, audit findings |
One commentary says moving a 2016 server to Azure no longer gets free security updates the way older versions did. Confirm the current terms with Microsoft before you rely on a cloud move as a patching shortcut.
An 8-week plan
- Inventory. List every Windows Server 2016 and Hyper-V Server 2016 machine, its role, owner and the applications on it.
- Decide per server. Choose upgrade, rebuild or ESU as a temporary bridge, and write down who signs off.
- Test. Run the application on Windows Server 2025 in a lab before you touch production.
- Back up. Take a verified backup and keep it until the migration is stable.
- Migrate the lowest-risk servers first, then domain controllers and databases.
- Enrol the leftovers in ESU before the end date to avoid back-billing.
Related lifecycle dates worth checking
SQL Server 2016 reached end of extended support on 14 July 2026 and has its own ESU path, which is separate from the operating system. Windows Server 2022 mainstream support ended on 13 October 2026. If you run Exchange on a 2016 server, also read our Exchange Server instability guide, because the October 2026 Windows update affected Server 2016 too.
Frequently asked questions
When does Windows Server 2016 reach end of life?
Extended support ends on 12 January 2027. Mainstream support ended on 11 January 2022.
Is there Extended Security Updates for Windows Server 2016?
Yes. Microsoft announced ESU in February 2026 and made the Azure Arc version generally available in August 2026, covering Critical and Important updates for up to three years.
What happens to my server on 13 January 2027?
It keeps running, but standard security updates, bug fixes and assisted support stop unless you have ESU.
What should I upgrade to?
Microsoft recommends Windows Server 2025. Check application compatibility and licensing first.
How much does ESU cost?
Prices depend on your cores and licensing route and Microsoft’s public pages do not give one list price. Ask your Microsoft partner for a quote.
Sources
- Microsoft Windows Server blog: Windows Server 2016 end of support
- Microsoft Lifecycle: Windows Server 2016
- Redmond Dispatch: Azure Arc ESU generally available
- ecorpit: Windows Server 2016 end of support migration playbook
- o365hq: Windows Server 2016 end of support, upgrade, migrate or buy ESU
- endoflife.ai: Windows Server 2016 end of life
Last checked: 15 November 2026. Microsoft lifecycle terms and ESU pricing can change, so confirm with Microsoft or your licensing partner before you commit.

