Windows Server 2016 leaves extended support in January 2027, and SQL Server 2016 has already left it. Microsoft's Windows Server 2016 lifecycle page lists the extended end as 1/13/2027 6:59:59 AM, with times shown in Pacific Time. Plan as if 12 January 2027 is the last day you can count on a security update.
Eight weeks is enough to decide what happens to every machine. It is not enough to rebuild everything, so the aim is a decision and an owner for each server, with the quick wins done first.
What the dates say
Windows Server 2016 follows the Fixed Lifecycle Policy. Mainstream support ended on 1/12/2022, and extended support ends on 1/13/2027. The same page lists three Extended Security Updates (ESU) years after that, ending 1/11/2028, 1/9/2029 and 1/8/2030. Containers released with Windows Server 2016 follow the same dates.
ESU is not a plan, and Microsoft calls it a last resort. Per Microsoft's ESU overview, it covers security updates rated critical and important. It does not include new features or non-security hotfixes. When the ESU period ends, the updates stop.
That overview documents the terms for Windows Server 2012 and 2012 R2: free in Azure, purchasable elsewhere, with a product key installed on each applicable server. The 2016 lifecycle page gives the ESU periods but not the commercial terms. Confirm price and Azure conditions with your licensing partner before you budget around them.
Weeks 1-2: find every machine
Do not trust the CMDB alone. Pull OS versions from your management tooling, hypervisor inventory and Azure resource lists, then compare them with what a network scan finds. Include test servers, forgotten VMs, container hosts and anything a vendor installed for you.
Record five things per machine: role, owner, internet exposure, whether the application vendor supports a newer Windows Server, and whether it runs SQL Server. A rough severity score helps you sort the list, and our CVSS calculator is one way to get it.
Weeks 3-4: decide per machine
Microsoft's upgrade planning guide lists the methods. Use it to pick one for each server:
| Situation | Default action |
|---|---|
| Same hardware, roles support in-place upgrade | In-place upgrade from installation media |
| New hardware, or roles that don't support in-place upgrade | Clean install or migration to a new server |
| Failover cluster that must stay available | Cluster OS rolling upgrade, one version at a time |
| Workload already planned for the cloud | Move to an Azure VM, then upgrade |
| Vendor software cannot run on a newer version | ESU plus isolation, with a dated exit |
The last row is the only one that leaves you running 2016. Give each such machine an end date, an owner and a named reason, and review the list monthly.
In-place paths from Windows Server 2016 are supported to 2019, 2022 and 2025 when you use installation media. Windows Update as an upgrade route to 2025 is listed only for 2019 and 2022, so a 2016 server needs media. Each upgrade also needs its own licence, and Microsoft's guide notes this is unlike Windows client.
SQL Server 2016 is already past its date
The SQL Server 2016 lifecycle page gives the extended end as 7/15/2026. ESU Year 1 runs from 7/15/2026 to 7/13/2027, Year 2 to 7/18/2028 and Year 3 to 7/17/2029. Any SQL Server 2016 instance in your estate today is either covered by ESU or unpatched.
Treat the database and its host as one unit. A 2016 database server on an upgraded OS still has an unsupported or ESU-dependent engine, and the reverse is also true. Check which service pack each instance runs. Service Pack 3 is the last one listed.
The ESU overview adds that moving SQL Server to Azure VMs brings three more years of Windows Server critical security updates at no extra charge. That statement sits in the context of the 2012 generation, so verify it applies to your versions before relying on it.
Constraints that cost time
Most delays come from the restrictions in the upgrade guide, not from the upgrade itself:
- Disable NIC Teaming before an in-place upgrade and re-enable it afterwards.
- You cannot switch between Server Core and Server with Desktop Experience during an in-place upgrade.
- In-place upgrades of servers configured to boot from VHD are not supported.
- Domain controllers have their own upgrade guidance. Read it before touching one.
- Upgrades from one language to another are not supported.
- You can move from Standard to Datacenter during an upgrade, but you cannot downgrade.
Back up before every upgrade, and test the restore on at least one machine. For roles that do not upgrade in place, check Microsoft's role and feature migration matrix first.
Isolating what you cannot fix
For machines that stay on 2016, the guides give no specific hardening steps, so this is general advice. Remove internet access where you can and allow inbound connections only from the systems that need them. Put these servers in their own network segment, and watch them closely, since any new vulnerability will stay unpatched unless ESU covers it. If you lack the staff for that, our managed security service covers monitoring. Our consulting team can help build the inventory and the exit plan.
Where to start
- Export every OS version from your hypervisors, Azure and endpoint tooling, and merge the lists into one inventory this week.
- Mark each server with its role, owner, exposure and whether SQL Server 2016 runs on it.
- Assign one action per server from the table above, and book the in-place upgrades and clean installs that have no blockers.
- Ask your licensing partner for written ESU terms for Windows Server 2016 and SQL Server 2016, including Azure conditions.
- Isolate every machine that stays on 2016 and give it an exit date no later than the end of the ESU period it depends on.
