In short
Windows Server 2016 reaches end of extended support on January 12, 2027. After that date, normal security updates stop unless the server is covered by an eligible Extended Security Updates path. Microsoft offers Windows Server 2016 ESU for up to three additional years, through 2030.
For most production workloads, ESU should be migration runway rather than the long-term plan. Raff supports Windows Server 2019, 2022, and 2025, so teams can build a separate destination, validate the workload, and cut over before the Server 2016 deadline.
Windows Server 2016 support ends January 12, 2027
Windows Server 2016 follows Microsoft's Fixed Lifecycle Policy.
| Milestone | Date | Meaning |
|---|---|---|
| Release | October 15, 2016 | Windows Server 2016 entered general availability |
| Mainstream support ended | January 2022 | Feature and non-security servicing became more limited |
| Extended support ends | January 12, 2027 | Normal security updates and support end |
| ESU period | Up to three years after end of support | Critical and Important security updates for eligible systems |
Microsoft's February 2026 end-of-support announcement and its Windows Server 2016 ESU billing documentation both use January 12, 2027 as the end-of-support date. Microsoft's product Lifecycle page currently shows an adjacent calendar date because that page states its dates are displayed in Pacific Time. For migration planning, use the Microsoft EOS and ESU documentation together and record which date convention your compliance documentation cites.
The lifecycle applies to Windows Server 2016 Standard, Datacenter, Essentials, and MultiPoint Premium. There is no separate "Windows Server 2016 R2" release.
What happens after Windows Server 2016 end of support
Windows Server 2016 does not stop booting after the support date. Existing applications and services can continue to run.
The change is supportability:
- normal Windows Server 2016 security updates stop;
- newly discovered vulnerabilities can remain unpatched unless the server is covered by ESU;
- software and security vendors may narrow or end support for products running on Server 2016;
- unsupported operating systems can create additional compliance, audit, and insurance requirements;
- troubleshooting becomes harder when Microsoft or an application vendor requires a supported OS before investigating a problem.
If the server is internet-facing, identity-related, or runs business-critical software, waiting until January 2027 to begin compatibility testing increases migration risk.
SQL Server 2016 is already out of extended support
Do not assume the Windows Server lifecycle also covers the database running on it.
SQL Server 2016 reached the end of extended support on July 14, 2026. A Windows Server 2016 machine can therefore still have a supported operating system in late 2026 while running a SQL Server version that has already left normal extended support.
If both products are installed on the same machine, plan the SQL Server upgrade or migration separately from the Windows Server move.
Windows Server 2016 ESU provides a temporary bridge through 2030
Microsoft announced Extended Security Updates for Windows Server 2016 in February 2026.
For eligible Windows Server 2016 Standard and Datacenter systems, ESU can provide Critical and Important security updates for up to three years after end of support, through 2030.
ESU does not return Windows Server 2016 to normal mainstream or extended support. Microsoft states that ESU does not include:
- new features;
- customer-requested non-security hotfixes;
- design changes.
Windows Server 2016 ESU through Azure Arc became configurable in the Azure portal on August 3, 2026. Billing for Windows Server 2016 ESU enabled through Azure Arc begins January 13, 2027. Microsoft also states that licenses provisioned after EOS are subject to back-billing to the Windows Server 2016 end-of-support date.
Windows Server 2016 ESU pricing is not one flat per-server number
There is no reliable universal dollar figure that applies to every Windows Server 2016 machine. Microsoft documents ESU licensing in terms of factors including:
- Standard vs Datacenter edition;
- physical or virtual core licensing;
- the number of covered cores;
- the purchasing route;
- eligible licensing agreements and discounts.
Azure Arc-enabled ESU provides monthly subscription billing. Commercial Licensing is another route for eligible customers.
Microsoft's current ESU eligibility guidance says hosted or on-premises workloads can qualify through routes such as active Software Assurance, qualifying subscription licenses, or license-included service from an SPLA partner, subject to the applicable licensing requirements.
For budgeting, use Microsoft's current ESU licensing guidance or an official Microsoft licensing quote for the exact environment. Do not budget from a generic fixed per-server number copied from another configuration.
Your three realistic options are ESU, in-place upgrade, or migration
| Option | Best fit | Main trade-off |
|---|---|---|
| Extended Security Updates | A real dependency prevents migration before January 2027 | Buys time but keeps the old OS |
| In-place upgrade | The existing server and every installed role support the upgrade path | Faster move but retains the existing server state |
| Clean migration to Windows Server 2025 | You want an isolated test target and clearer rollback path | Requires migration planning and cutover |
Option 1 - Use ESU when a real blocker prevents migration
ESU is appropriate when an application vendor, hardware dependency, or regulated change process makes migration before the deadline unrealistic.
Treat it as a bridge with an exit date. Document:
- why the workload cannot move now;
- the exact ESU licensing route;
- who owns the migration project;
- the target Windows Server version;
- the planned retirement date for Server 2016.
Azure Arc-enabled ESU is useful for organizations that need monthly subscription billing. Microsoft notes that late enrollment can create back-billing to the Windows Server 2016 end-of-support date.
Option 2 - Windows Server 2016 can upgrade directly to Windows Server 2025 in supported scenarios
Microsoft's current upgrade matrix supports a direct Windows Server 2016 to Windows Server 2025 in-place upgrade using installation media for eligible nonclustered systems. Starting with Server 2025, Microsoft allows supported nonclustered systems to jump up to four Windows Server versions in one upgrade path.
That does not mean every Server 2016 machine should be upgraded in place.
Before using the direct path, verify:
- the edition and installation option are supported;
- the machine meets Windows Server 2025 requirements;
- every installed role supports in-place upgrade;
- application and driver vendors support Windows Server 2025;
- backups and rollback have been tested;
- the target Windows Server license and activation method are ready.
For hosted VMs, also verify what the provider supports. A clean side-by-side migration may be safer when the workload is important enough that you want the original Server 2016 machine intact during validation.
Option 3 - Migrate to a new Windows Server 2025 VM
A clean migration creates a separate destination instead of replacing the current OS in place. This can make testing and rollback easier because the Server 2016 system remains unchanged until the new workload is verified.
Common candidates include:
- Active Directory domain controllers;
- IIS applications;
- file servers;
- SQL Server workloads;
- accounting and ERP applications;
- RDS workloads.
For Raff customers, current Windows VM examples are:
| Windows VM | Compute | Windows Server Standard SPLA | Monthly total |
|---|---|---|---|
| 1 vCPU / 2 GB / 50 GB | $13.99 | $15 | $28.99 |
| 2 vCPU / 4 GB / 80 GB | $22.99 | $15 | $37.99 |
| 4 vCPU / 8 GB / 120 GB | $40.99 | $15 | $55.99 |
The Windows Server Standard SPLA charge is $15 per instance per month. Optional RDS User SALs, extra storage, backups, and application or database licensing are separate where applicable. Raff Windows VMs include unmetered bandwidth and are available in the us-east region.
Current plan details are on the Windows VM page and pricing page.
BYOL is not automatic when moving Windows Server to a hosted VPS
Do not assume an existing Windows Server license can be moved to any hosted VM.
For eligible Microsoft customers, hosted Windows Server BYOL depends on the applicable outsourcing rights and Flexible Virtualization Benefit requirements. Windows Server BYOL is not the same as Microsoft's License Mobility through Software Assurance program used for eligible server applications such as SQL Server.
If the required BYOL rights do not apply, use the provider's Windows Server licensing model. Raff offers Windows Server Standard licensing through SPLA at $15 per instance per month.
For a deeper licensing explanation, see Windows Server Licensing: SPLA, BYOL, CALs & RDS.
Which path fits your Server 2016 workload
- Legacy application certified only for Server 2016: use ESU if eligible, isolate the workload appropriately, and create a dated vendor migration plan.
- Simple standalone server with supported apps: evaluate the direct Windows Server 2016 to 2025 in-place path.
- Domain controller: build a newer DC, replicate, transfer roles, validate, and retire the old DC rather than treating the domain controller as a generic in-place upgrade.
- File server: a side-by-side migration can provide a cleaner rollback path and lets you test permissions before cutover.
- SQL Server 2016 host: plan the database lifecycle separately because SQL Server 2016 already reached end of extended support in July 2026.
- MSP-managed client fleet: use ESU for systems with genuine blockers and prioritize internet-facing, identity, and compliance-sensitive workloads for migration.
A practical migration sequence reduces risk
For mixed-role Server 2016 systems, separate the workload into migration units instead of treating the machine as one indivisible box.
A typical sequence is:
- inventory installed roles, applications, certificates, scheduled tasks, shares, ports, service accounts, and dependencies;
- identify unsupported application and database versions;
- build the Server 2025 destination;
- migrate and test data and application components;
- validate authentication, backups, monitoring, and firewall rules;
- schedule the cutover;
- keep a rollback path until the new system is proven;
- retire or isolate the Server 2016 machine after validation.
Our detailed Windows Server 2016 to 2025 migration guide covers the technical path in more depth.
Start the project before the January 2027 deadline
The January 12, 2027 deadline is approaching. Do not assume an existing production server can be migrated safely in a fixed number of weeks: start inventory and vendor-compatibility checks immediately.
A practical sequence for a small environment is:
- Start now: inventory Server 2016 roles, applications, data, users, licensing, and migration blockers;
- Before scheduling a cutover: build a supported Server 2025 destination and validate applications, access, backups, and rollback;
- After testing, before January 12, 2027: migrate supported workloads and verify production behavior;
- If a blocker prevents migration by the deadline: confirm ESU eligibility, licensing, costs, and security controls for that specific environment.
A complex RDS, AD DS, or database migration may need more lead time than a simple member server.
The exact schedule depends on application complexity, change-control requirements, data volume, and vendor support. Avoid treating a generic migration-duration estimate as a guarantee.
How Raff fits into the migration
Raff provides Windows VMs with Windows Server licensing available through Microsoft SPLA, plus BYOL support for customers whose licensing rights permit hosted deployment. For a migration project, the practical use is to create the new Server 2025 destination first, validate the workload, and move production only after the application, authentication, firewall, and backup checks pass.
Raff supports 3,000+ customers and 15,000+ VMs, with a 99.9% SLA. If you want a second set of eyes on sizing or the migration path, the Windows engineering contact option is available from this page.