Windows Server 2016 leaves support on 12 January 2027. Everyone repeats that. What almost nobody has read is the Azure Arc billing page, where Microsoft writes that licences provisioned after that date are back-billed to 12 January, and then adds: "In principle, there are no cases in which back-billing is waived after reactivation or recreation, and there are no conditions under which it can be avoided."
Translated into the December board meeting: "let us wait and see how January goes" no longer defers the spend, only the decision. The meter starts on 12 January whether you buy that day or in June, and what you gain by waiting is uncertainty, not money. That matters, because it is the opposite of how the classic Volume Licensing ESU worked, where you bought a whole year and your invoice set the clock.
How that meter works
The Azure Arc documentation spells it out. Billing for Windows Server 2016 ESUs starts on 13 January 2027 and is monthly. If you provision the licence later, you pay for the elapsed period since 12 January as a one-off back-billing charge, which also shows up as a separate line on the invoice. And there is no back door: deactivate and reactivate, and you are billed for the window it was off; delete the licence and recreate it, and back-billing still applies; add cores to an existing licence, and those new cores are also back-billed from end of support.
There is logic behind it and Microsoft explains it: whoever enrols late still gets every critical patch published up to that point, and the back-billing charge reflects the value of those patches. Fair enough. But it changes the budget conversation completely, because the cost of deferring stops being zero and becomes exactly the same cost, accumulated.
Before the price comes eligibility, and that is where many are left out
Almost every guide on this end of support argues about how much the ESU will cost. Few mention that for a good share of the Spanish estate the question never arises, because the entry requirement is not met. The licence provisioning documentation is explicit for 2016: you need Software Assurance or an equivalent Server Subscription for on-premises workloads, and the purchase goes through an Enterprise Agreement, Enterprise Subscription Agreement, Server & Cloud Enrollment or Enrollment for Education Solutions.
And the three side doors that existed with Windows Server 2012 are shut for 2016. The documentation says so itself:
- →SPLA is not available for Windows Server 2016 ESUs. With 2012 it was, and it was the route many hosting providers used.
- →Nor is the Visual Studio subscription benefit for dev/test scenarios. Your 2016 test machines pay like production ones.
- →Transitioning from Volume Licensing is not supported for 2016 ESUs enabled by Azure Arc. With 2012 you could jump from the key-based model to Arc between year one and year two; not here.
The thirty-person company with two servers bought under OEM licensing and no Software Assurance does not have a price problem: it has no product. Its plan B is not expensive, it simply does not exist. And that reorders the questions, because choosing between upgrading and paying for ESU only makes sense if you can buy the ESU.
The product exists; a public list price does not
It is worth being precise here, because some articles still repeat that "nothing is known". Quite a lot is known: Windows Server 2016 ESUs can be configured in the Azure portal since 3 August 2026 and have been generally available through Azure Arc since 6 August. What still does not exist is a public list price: back in February, when Microsoft announced the timeline, The Register put it plainly — "the absence of official pricing for Windows Server 2016 is frustrating for administrators unwilling or unable to move their workloads" — and today the public price table still has no figure. The practical consequence is not to wait: it is that the number has to be requested from your CSP rather than looked up on a web page.
When asking for that quote it helps to know something that is published on Microsoft's licensing site: since 1 April 2026, new ESU offerings for Windows products and SQL Server carry the same list price regardless of where you deploy and of the channel you buy through, and that rule does not touch existing offerings — Windows Server 2012, Windows 10 22H2 and SQL Server 2014 are expressly excluded. So the question for the vendor is a concrete one: does this price depend on where the machine runs or on the channel I buy through? For a new offering, the answer should be no.
Where the bill is actually decided: in how you count cores
Microsoft says three things drive the bill: the number of cores provisioned, the licence edition —Standard or Datacenter— and any applicable discounts. The first is the one you can move, and it is not a matter of negotiating: it is a matter of picking the right licence type. On physical cores, the minimum is 16 per machine. On virtual cores, the minimum is 8 per virtual machine, it cannot be used on physical servers, and you always pick Standard edition even if the operating system is Datacenter. Only three combinations are valid: Standard virtual, Standard physical and Datacenter physical.
The good news is that you do not have to take our word for it: the example is in the documentation itself. A customer with a 16-node VMware cluster and 1,024 physical cores, of which only 44 virtual machines run Windows Server 2016, can license the whole cluster with 1,024 Datacenter physical cores, or license each VM for a total of 506 Standard virtual cores —summing, per VM, the greater of 8 and the cores actually assigned to it. Microsoft concludes the second option is cheaper. That decision, taken without looking, is a difference of roughly double on the same infrastructure on the same day.
This is the same slippery ground we wrote about a few days ago: moving hypervisor does not touch your Windows licences, but it does change how you count cores once failover is in play. The trap here is its twin: the number you pay is not set by your workload, it is set by the count somebody attested to.
The option that is not on the slide
Upgrading to Windows Server 2025, moving the workload to Azure or paying for ESU all share an assumption nobody states: that the server has to keep existing. Across part of the estate we see, it does not. The typical Windows Server 2016 in a mid-sized company holds three things —a file share, a print queue and a line-of-business application— and of those three, the first two rarely need a Windows Server in 2027. The application is what decides, and whoever decides whether it can move is not you: it is the vendor who certifies it.
At everyWAN we sell migrations, managed infrastructure and consultancy, and we are not Microsoft resellers nor do we take commission on licences. This last option earns us less than the other three: if two of your three servers disappear, there is less to maintain. We say it anyway, because ESU is paid per attested core whether there is a workload on it or not.
What to check this week
None of this requires buying anything or waiting for a price. The first item comes off the machine itself in two minutes; the last is a phone call that takes weeks to be returned, so start there.
- ✓Whether you hold Software Assurance or an equivalent Server Subscription, and on exactly which machines. If the answer is no, on-premises ESU is not an option and the rest of the conversation changes.
- ✓Edition, version and physical cores of each machine, because Standard and Datacenter are not priced alike:
Get-CimInstance Win32_OperatingSystem | Select-Object Caption, VersionandGet-CimInstance Win32_Processor | Select-Object Name, NumberOfCores. - ✓Whether it is physical or virtual, and how many virtual cores it has assigned. That decides whether physical or virtual core licensing suits you, and the choice cannot be changed afterwards: licence type is not a mutable property.
- ✓Which roles are actually installed:
Get-WindowsFeature | Where-Object Installed. This is where you find out the "application server" is also running the office DHCP. - ✓Which version your software vendor certifies up to, in writing and dated. It is the only fact not on the machine and it overrules all the others.
If the pattern sounds familiar, it is because we lived through it on the desktop this year: the Windows 10 ESU and the toll that doubles. That one launched with a published price. This one did not, and it comes with the meter built in.
What we are not claiming
- ✗We do not know what it will cost. We give no figure because there is no public list price, and other products' ladders are no basis for an estimate: Windows Server 2012 ESU was charged at 100% of the licence price in year one, and SQL Server 2016's starts at 75%. Two products, two models.
- ✗The back-billing we describe is that of ESU enabled by Azure Arc, as documented by Microsoft. If you buy through Volume Licensing the billing mechanism is different; what does not change is the date from which you are unpatched.
- ✗Nothing switches off on 12 January. Your server will boot on the 13th exactly as on the 12th. What stops arriving are the security updates, and the problem is not that day: it is the months after it.
Sources (verified on 30 September 2026): the 12 January 2027 end-of-support date and Microsoft's recommended paths — Microsoft, "Planning ahead for Windows Server 2016 end of support", 25 February 2026; billing starting on 13 January 2027, back-billing to 12 January, the sentence about there being no conditions under which it can be avoided, the charge for added cores, billing after deactivation or deletion, and Volume Licensing transition not being supported — Microsoft Learn, "Billing service for Extended Security Updates for Windows Server through Azure Arc"; the Software Assurance or equivalent Server Subscription requirement, SPLA and the Visual Studio benefit not being available for Windows Server 2016, the 16 physical and 8 virtual core minimums, the three valid licence combinations and the 1,024-core versus 506-virtual-core cluster example — Microsoft Learn, "License provisioning guidelines for Extended Security Updates for Windows Server"; the absence of official pricing and the Windows Server 2012 and SQL Server 2016 ladders — The Register, 24 February 2026; the single-price rule for new offerings from 1 April 2026 and its exclusions — Microsoft Licensing, "Services: Pricing Consistency Update"; portal configuration from 3 August and general availability through Azure Arc from 6 August 2026 — Schneider IT Management.
Do you know whether you can buy the ESU before arguing about its price?
We check whether you hold Software Assurance on those machines, count the cores that will actually be attested, and tell you which roles can leave that server before January. If the conclusion is that ESU suits you, we help you request the quote with the right numbers. It is consultancy and, if something has to move, infrastructure: we do not sell anybody's licences.
Talk to everyWAN
Microsoft 365
ES 
CAT 
EN