Windows Server 2016 End of Life: 12 January 2027, and What to Do With the App on It

The last security update ships on 12 January 2027. For most small companies the hard part is not the operating system, it is the one business application nobody dares to touch that runs on top of it.

Oct 16, 2026

Updated

An old server tower with a cracked shield and an expired calendar, its applications carried along a glowing path to a modern container stack under an intact shield

In short: Windows Server 2016 reaches end of life on 12 January 2027, with its last regular security update that day. After that, every new vulnerability stays open unless you pay Microsoft for Extended Security Updates (ESU). Those are now on sale through Azure Arc for up to three years, but Microsoft still has not published the price, and they cover only the Standard and Datacenter editions. Its siblings are already gone: SQL Server 2016 on 14 July 2026, Windows 10 Enterprise LTSB 2016 on 13 October 2026. For many small and mid-sized companies, the server is the easy part. The hard part is the business application on it: an ERP, a quoting tool, an intranet or an Access database someone built years ago. This post covers the dates, what ESU costs and covers, which version to move to, and what to do with the app.


When does Windows Server 2016 support end?

On 12 January 2027. Microsoft's lifecycle page lists mainstream support ending on 11 January 2022 and extended support on 12 January 2027 (Pacific time), for the Datacenter, Standard, Essentials and MultiPoint Premium editions. Containers built on the 2016 base image follow the same dates.

Until then it gets security fixes only. After that, nothing, unless you pay for ESU.

The dates that matter around it

ProductEnd of supportSource
SQL Server 201614 July 2026 (passed). ESU until July 2029Microsoft lifecycle
Windows 10 Enterprise LTSB 2016, IoT Enterprise 2016 LTSB13 October 2026 (passed)Help Net Security
Windows Server 201612 January 2027. ESU until January 2030Microsoft lifecycle
Windows Server 20199 January 2029Microsoft lifecycle
Windows Server 2022Mainstream ended 13 October 2026; extended until 14 October 2031Microsoft lifecycle
Windows Server 2025Mainstream until 13 November 2029; extended until 14 November 2034Microsoft lifecycle

If the application on your 2016 server uses SQL Server 2016, its database is already out of support. That is often the more urgent half.

What Extended Security Updates buy you, and what they cost

Microsoft made Windows Server 2016 ESU enabled by Azure Arc generally available in August 2026. What is confirmed:

  • Coverage: critical and important security updates for up to three years, through January 2030. No new features, no non-security fixes, no design changes, and no technical support.
  • Editions: Standard and Datacenter only.
  • Eligibility: Software Assurance, a server subscription, or licences from a hosting provider (SPLA).
  • Delivery: each server runs the Azure Connected Machine agent (version 1.62 or later) and is enrolled in the Azure portal. Enrollment opened on 3 August 2026.
  • Billing: monthly, per core, by edition, starting 13 January 2027. A server enrolled later is back-billed to 12 January 2027, so enrolling late saves nothing.

What is not confirmed: the price. As of early November 2026 Microsoft had not published it. Some sites quote figures; none of them cite a Microsoft price list, so we do not repeat them. Ask your licensing partner for a written quote per core.

Is ESU free in Azure? It was for Windows Server 2012 virtual machines. On 27 March 2026 Microsoft announced that new ESU offerings from 1 April 2026 carry the same list price inside and outside Azure. It has not said Windows Server 2016 is an exception, so do not plan a "move to Azure for free updates" around it.

ESU is worth buying when you have a dated plan to leave. Bought instead of a plan, it is a monthly bill on a server that gets no better.

First, find out what the server actually does

Before choosing, list what runs on it. In the small companies we work with, a "2016 server" is usually one of two things, and they have different answers.

Windows infrastructure: Active Directory, file shares, print, Exchange, Remote Desktop. That is a Windows upgrade or a move to Microsoft 365, and it is the job of your IT provider. It is not what we do, and we will tell you so. One useful fact for that job: Windows Server 2025 domain controllers need the domain at the Windows Server 2016 functional level or higher.

A business application: a .NET or PHP web app on IIS, a SQL Server database, a scheduled job that sends invoices, an Access front end used by three people every day (Access 2021 itself lost support on 13 October 2026). That is where the risk sits, because:

  • it often runs on old versions of its own stack (.NET Framework, SQL Server, PHP) that are out of support on their own schedule;
  • the person who wrote it has often left, and nobody knows what an operating system upgrade will break;
  • it is often reachable from the internet, to serve a customer portal or a field team, so an unpatched server is directly exposed.

What to do, by situation

Your situationWhat to doRough cost
Only Windows roles (AD, files, print)Upgrade to Windows Server 2025 or move to Microsoft 365, with your IT providerLicences plus their time
A healthy, documented app that must stay on WindowsUpgrade in place to Windows Server 2025, after testing on a copyLicences plus testing
A critical app you cannot move before JanuaryBuy ESU, with a written exit datePer-core monthly fee, price not yet published
An app nobody can change, or one exposed to the internetAudit it, then move it off the server$2,900 audit, then $5,000 to $18,000 per module
A small piece: an Access front end, a scheduled job, a reportRebuild that piece first as a small hosted tool$1,900 fixed starter
Server 2016 EssentialsNot covered by ESU. Upgrade or move before 12 January 2027Depends on what runs on it

Your three options for the application

1. Upgrade in place to Windows Server 2025. Least change, and right when the app is healthy, documented and Windows-bound. Skip 2022 for a fresh upgrade: it already left mainstream support in October 2026. You need new licences, a test environment, and someone who can tell whether the app still works after the upgrade. Risk: you inherit every other old component as-is.

2. Buy ESU and plan the move. Right when the app is critical and the migration cannot be done before January. Set an exit date before you sign, and get the per-core price in writing.

3. Move the application off the server. Put the app in a container, the database on a managed service, and the server out of the picture. This is what we do: we take over the code, audit it, and move it to hosting we run, where the operating system, patches and backups are our problem rather than yours. Our applications run on Google Cloud in containers, with no administration interface reachable from the internet, dependencies watched by Dependabot, and the infrastructure described in code. Details are on our security page.

It is more work than an upgrade the first time. After that there is no "2016 server" left to reach end of life, because nobody owns a server any more.

How to decide this week

  1. List what runs on each 2016 server. If the answer is "nobody is sure", that is the first finding.
  2. Check the edition. Essentials gets no ESU, so it has a hard deadline.
  3. Check what is reachable from the internet. An unpatched server behind a public portal is the urgent case.
  4. Check the versions under the application: .NET, SQL Server, PHP, the framework. SQL Server 2016 is already out of support; .NET 8 ends on 10 November 2026.
  5. Find who can change the code. If nobody can, an operating system upgrade is a gamble, and so is staying.
  6. Pick an option and a date. If that date is after 12 January 2027, get an ESU quote now: enrolling late is back-billed anyway.

If steps 4 and 5 have no answer, a short audit is the right start: you get the list of what runs, what is exposed and what is out of support, with an order of work.

Related: should your software agency host your app?, the supermarket fridge hack and admin interfaces on the internet, PHP2Shell explained for CEOs, and our security page.

Read next: AWS outages in 2025 and 2026, remote access security.

Also: .NET 8 end of life on 10 November 2026 and PostgreSQL 14 end of life on 12 November 2026.