Windows Server 2016 End of Support: Licensing and Readiness Assessment

Windows Server 2016 End of Support

Microsoft's Fixed Lifecycle Policy provides 10 years of support for Windows Server:

• 5 years of Mainstream Support
• 5 years of Extended Support

For Windows Server 2016, that support ends on January 12, 2027. After that date, organisations will no longer receive regular security updates for Windows Server 2016. Running unsupported servers can introduce security, operational and compliance risks. For systems that cannot be upgraded, migrated or retired in time, Microsoft offers Extended Security Updates (ESU) at an additional cost.

Where to start?

The first question should not be:

The first question should be:

Only those remaining workloads should become candidates for ESU coverage.

• How many Windows Server 2016 workloads do we still have?
• Which workloads are genuine ESU candidates?
• Which systems can be retired or upgraded?
• What is the potential financial impact?

Why this is harder than it sounds

At first glance, ESU looks fairly straightforward. Identify your Windows Server 2016 systems, calculate the required cores and purchase the required ESU coverage. In reality, it is often more complicated. The actual cost of Windows Server 2016 ESU depends on:

• Standard versus Datacenter;
• Physical versus virtual deployment;
• Core counts and licensing minimums;
• Existing Windows Server licenses;
• Active Software Assurance or equivalent subscriptions;
• Host and cluster relationships.

A handful of Windows Server 2016 virtual machines may require a completely different approach than a dense VMware cluster running dozens of workloads. In addition, many organisations simply do not have a complete and up-to-date picture of their Windows Server estate. Missing host relationships, incomplete inventory data, retired systems and unknown licensing positions are common findings during an assessment.

One important change

One detail that caught my attention in Microsoft's latest guidance concerns development and test environments. Microsoft's current guidance appears to suggest that the Visual Studio subscription benefit for free Dev/Test ESU coverage is not available for Windows Server 2016 ESU. This is a notable difference compared to assumptions many organisations may have based on previous ESU programmes.

License provisioning guidelines for Extended Security Updates for Windows Server — Azure Arc

Microsoft Learn

Azure Arc first?

One thing that stands out compared to previous ESU programmes is Microsoft's clear focus on Azure Arc as the preferred ESU delivery and management model. Azure Arc introduces a more flexible operational model, including monthly billing. At the same time, Azure Arc does not remove the underlying licensing requirements. Active Software Assurance or equivalent subscriptions remain important for Windows Server 2016 ESU.

Interestingly, Azure Arc pricing is currently much easier to find than traditional on-premises ESU pricing. While Microsoft publicly publishes Azure Arc pricing, many customers still discuss alternative traditional annual SKU purchasing options through their Microsoft account team.

What now?

January 2027 is right around the corner, but inventory, budgeting and migration projects usually take longer than expected. Organisations that start early generally have more options. A practical Windows Server 2016 ESU Readiness Assessment should help answer four simple questions:

• How many Windows Server 2016 workloads do we still have?
• Which workloads are genuine ESU candidates?
• Which systems can be upgraded, migrated or retired?
• What is the potential financial impact?

You do not need a mature SAM platform to answer those questions. Existing discovery sources and inventory exports are often sufficient to produce meaningful results.