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. Microsoft now positions Azure Arc prominently as the preferred delivery model for Windows Server 2016 ESU and publishes public pricing for this route. 

 

Get ready for the count (down) 

One mistake I frequently see is organisations immediately focusing on pricing.

​

The first question should not be:

​

How many ESU licenses do we need?

​

The first question should be:

​

What actually is the scope of our Windows Server 2016 estate?

​

Only after identifying the remaining workloads does it make sense to discuss ESU.

​

A practical assessment should answer five simple questions:

​

• How many Windows Server 2016 workloads still exist?

• Which systems are genuinely still required?

• Which systems are critical and require ESU? 

• Which workloads can realistically be upgraded, migrated or retired before January 2027?

• What is the potential financial impact?

   

ESU is licensing, not a support contract 

A common misconception is that ESU is purchased "per server" or part of your support contract.

In reality, ESU follows the underlying Windows Server licensing position.

​

Things that matter include:

• Standard versus Datacenter;

• Physical versus virtual deployment;

• Core counts and licensing minimums;

• Existing Windows Server entitlements;

• 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.

​

This is one of the reasons why inventory quality matters so much.

 

Impact $ 

The financial impact of ESU can be significant.

​

Microsoft currently publishes Azure Arc ESU pricing for Windows Server 2016 at:

• Standard: USD 10.50 per core per month

• Datacenter: USD 60 per core per month

 

For a Windows Server 2016 Standard VM using the minimum 8-core requirement, this translates to:

• 8 cores × USD 10.50 = USD 84 per month

• Approximately USD 1,008 per year per workload

​

That may not sound dramatic for a single virtual machine. However, the objective of ESU is not to protect a single server. Most organisations are dealing with dozens, hundreds or even thousands of Windows Server 2016 workloads.

​

Now multiply that by:

• dozens of workloads;

• multiple years of ESU;

• larger virtual or physical machines;

• Datacenter deployments;

• enterprise-scale environments.

 

The result can quickly become a meaningful operational cost, and a significant addition to your running Windows Server licensing cost. Especially where additional Windows Server licenses, Software Assurance or equivalent subscription rights are required to establish ESU eligibility.

​

The value of an ESU assessment is therefore not simply determining how much ESU to purchase. The value is understanding:

• which workloads genuinely require ESU;

• which systems can be upgraded or retired before January 2027;

• whether the Windows Server current licensing position supports ESU eligibility;

• and whether alternative licensing approaches exist.

 

The objective of ESU planning is therefore not simply to calculate the bill.

The objective is to understand both the price and the scope.

 

One Interesting Change

One detail that caught my attention in Microsoft's latest guidance concerns development and test environments.

Microsoft's current Windows Server 2016 guidance appears to indicate that the Visual Studio subscription benefit for free Dev/Test ESU coverage is not available for Windows Server 2016 ESU. [click]

​

The information available today is still relatively limited, but it is an important point to validate.

Many organisations may have assumptions based on previous ESU programmes that do not necessarily apply to Windows Server 2016.

 

Azure Arc is Microsoft's Preferred Route

Compared to earlier ESU programmes, Microsoft is placing a strong emphasis on Azure Arc.

​

Azure Arc introduces:

• monthly billing;

• simplified enrollment;

• ESU visibility and reporting;

• easier management of changing server populations.

 

However, Azure Arc does not remove the underlying licensing requirements. Microsoft explicitly states that active Software Assurance or equivalent subscription rights remain important for Windows Server workloads connected through Azure Arc. Organisations also need to onboard their Windows Server 2016 workloads into Azure Arc in order to consume the service.

It is also interesting that Azure Arc pricing is readily available, while traditional on-premises ESU procurement often requires discussions with Microsoft account teams or licensing partners.

 

What's next?

January 2027 is right around the corner. Budget planning, inventory, migration projects, application testing and infrastructure changes almost always take longer than expected.

​

A practical Windows Server 2016 ESU Readiness Assessment should help answer:

• What does the Windows Server environment look like today?

• Which Windows Server 2016 workloads remain?

• Which workloads are genuine ESU candidates?

• What is the potential financial impact?

• Which systems should be upgraded, migrated or retired first?

 

The good news is that a mature SAM platform is not always required. Existing inventory sources and discovery reports are often sufficient to build a quick but meaningful first assessment.

​

The goal is not to purchase ESU for every Windows Server 2016 workload that appears in an inventory export. The goal is to understand the estate, identify the genuine candidates and make informed decisions before the deadline forces them.

​

If you are starting to evaluate your Windows Server 2016 position, now is the time to understand the scope.