Plenty of businesses still keep key apps and files on older servers. For those running Windows Server 2016, the clock is close to running out: Microsoft's Azure Arc billing page lists January 12, 2027, as the end-of-support date.
After that date, regular security fixes stop unless a business takes action. Microsoft's lifecycle page shows mainstream support for the product has already ended, with extended support ending in January. Microsoft lists several paths forward, and each takes time to plan.
Key facts
- Microsoft lists January 12, 2027, as the end-of-support date for Windows Server 2016.
- The dates apply to the Datacenter, Essentials, MultiPoint Premium and Standard editions, plus containers released with the product.
- Extended Security Updates, or ESUs, can supply Critical and/or Important security fixes for up to three years after extended support ends.
- Virtual machines hosted in Azure get ESUs at no charge if they are set up to receive updates.
- Microsoft names two on-premises options: build new servers on a supported version and migrate, or upgrade in place.
Background
Windows Server 2016 falls under Microsoft's Fixed Lifecycle Policy, according to its lifecycle page. Microsoft says Windows Server LTSC releases get at least 10 years of support, split into five years of mainstream support and five years of extended support.
Mainstream support for this version is already over. Extended support is now in its final months and ends in January, Microsoft's lifecycle page shows. The same dates cover every edition, from Standard and Datacenter to Essentials and MultiPoint Premium. Containers that shipped with the product follow that schedule too.
When a product leaves extended support, Microsoft stops shipping routine security updates for it. Servers keep running, but new flaws found after that point are no longer fixed for most customers. That is why the end date matters for any business that still relies on these systems.
For organizations that cannot move in time, Microsoft offers a paid safety net. The company calls Extended Security Updates a temporary bridge that can deliver Critical and/or Important security updates for up to three years after the end of extended support. ESUs do not extend a product's lifecycle, and they do not add technical support beyond the original timeline.
What it means for you
If your business still runs this server version, you have a decision to make soon. The choice usually comes down to cost, risk and how much change your team can absorb in a short time.
Staying on an unsupported server without ESUs means running software that will not get new security fixes. For a server that holds customer records, payroll data or shared files, that can raise risk quickly. Our cybersecurity services can help you weigh that risk and close gaps while you plan a move.
Paying for ESUs buys time at a cost. For on-premises and hosted environments, Microsoft's ESU FAQ says each year of coverage costs 100% of the full license price. That makes ESUs a short bridge, not a long-term plan.
Azure changes the math. Microsoft says VMs hosted in Azure are automatically enabled for ESUs when they are configured to receive updates, and those updates come free of charge. For some workloads, moving to the cloud can buy time while a full upgrade is planned. Our team can help you review cloud and infrastructure options for each workload.
Servers that stay on-premises but connect to Azure Arc follow a different billing model. ESU billing through Azure Arc is monthly and depends on the number of cores, the edition (Standard or Datacenter) and any discounts. Billing for Windows Server 2016 ESUs through Azure Arc starts January 13, 2027. Licenses set up after that date are back-billed to January 12, 2027. Microsoft also says moving from Volume Licensing is not supported for Windows Server 2016 ESUs enabled by Azure Arc.
Practical steps
Start with an inventory. List every server, what it runs, who owns it and which edition it uses. A simple checklist like our guide to IT documentation for small businesses can make this step faster.
Next, pick a path for each server:
- Build new and migrate. Microsoft lists setting up new servers on a supported version and moving workloads over as one on-premises path.
- Upgrade in place. Microsoft lists an in-place upgrade as the second on-premises path. Starting with Windows Server 2025, nonclustered in-place upgrades can jump as many as four versions at once.
- Move to Azure. Azure-hosted VMs that are configured for updates receive ESUs at no charge.
- Buy ESUs as a bridge. On-premises and hosted ESUs cost the full license price for each year, and ESUs enabled by Azure Arc are billed monthly based on cores, edition and discounts.
Then set a timeline. Work backward from the end date, leaving room for testing, app checks and a fallback plan. If new hardware or licenses are part of the plan, our IT procurement help can line up what you need. For ongoing patching and monitoring after the move, our managed IT services can take that work off your plate.
Waiting until a server fails or an audit flags it tends to cost more. Our post on why waiting for something to break is the wrong IT strategy explains how planning ahead lowers that risk.
What happens next
Regular support for Windows Server 2016 ends January 12, 2027, according to Microsoft. The next day, January 13, 2027, is when Azure Arc ESU billing for the product begins.
Microsoft's ESU FAQ describes coverage of up to three years after extended support ends for eligible products, but ESUs remain a stopgap. Planning a real upgrade or migration now is the safer course.
