Azure Hybrid Benefit vs Buying New Server Licences for the Cloud

Fix it now

Azure Hybrid Benefit lets you run Windows Server and SQL Server in Azure on licences you already own, paying only the base compute rate. It requires core licences with active Software Assurance or qualifying subscription licences, a minimum of eight core licences per virtual machine, and somebody to keep the coverage current. Licence-included capacity costs more per hour and asks nothing of you.

1. Use the benefit for long-running, steady workloads where you already hold covered licences. That is where the saving compounds.
2. Use licence-included capacity for short projects, test environments and anything that starts and stops. The cost stops when the resource stops.
3. Count on eight core licences per virtual machine as the floor, on both Standard and Datacenter, even for a four-core instance. Larger instances need licences equal to the core count.
4. Convert processor licences at sixteen core licences each before you start the arithmetic.
5. Plan the dual-use window: Standard licences must be used on-premises or in Azure, not both, other than a one-time 180-day migration allowance. Datacenter licensed by virtual machine allows both indefinitely.
6. Take the free Extended Security Updates into account when moving an out-of-support server. In Azure they cost nothing extra and do not require Software Assurance, though the benefit itself still does.

Workloads using Azure Hybrid Benefit may run only during the Software Assurance or subscription term. When it approaches expiry you must renew, disable the benefit, or deprovision the workload.

If the workload is short-lived or you hold no covered licences, licence-included capacity is the answer and you can stop. Below is the conversion arithmetic, the dual-use rules by edition, and the SQL Server side.

Why it happens

Azure Hybrid Benefit is a substantial discount with an eligibility condition and a tracking obligation. The condition is coverage: you need on-premises Windows Server core licences with active Software Assurance, or qualifying subscription licences, available through certain commercial licensing agreements. The obligation is that the entitlement is only good while that coverage lasts. Microsoft states it plainly – workloads using Azure Hybrid Benefit can run only during the Software Assurance or subscription licence term, and as expiry approaches you must renew, disable the benefit, or deprovision the workload.

The conversion arithmetic is simple once you know the floors. Each processor licence converts to sixteen core licences. In Azure, the minimum is eight core licences per virtual machine on both Standard and Datacenter, even for a four-core instance, and larger instances need licences equal to the instance’s core count – a twelve-core instance needs twelve. Microsoft’s own summary of the Standard case is that a set of eight-core licences entitles you to run an instance of up to eight cores.

Where the two editions genuinely diverge is dual use. Windows Server Standard licences must be used either on-premises or in Azure, not simultaneously, with a one-time 180-day exception for migrating the same workloads. Windows Server Datacenter is different: licensed by virtual machine it permits indefinite simultaneous use on-premises and in Azure, and allocated to an Azure dedicated host it permits simultaneous use for 180 days from the allocation date. Datacenter also carries the unlimited virtualisation right in Azure – any number of Windows Server virtual machines on an Azure dedicated host, provided you allocate covered Datacenter licences for all the available physical cores on that server.

Full reference

The two routes, on what they actually demand

Doing the sum on your own estate

Work in core licences, not processors, and start from the floors. Convert every processor licence to sixteen core licences. For each Azure virtual machine you intend to run, take the greater of eight and the instance’s core count – that is the number of core licences it consumes. Add those up and compare against what you hold with active coverage. The shortfall, if there is one, is either licences to buy or virtual machines to run at the licence-included rate.

Two mistakes recur. The first is assuming a four-core virtual machine consumes four core licences; it consumes eight, because eight is the published minimum on both editions. The second is forgetting that Standard cannot be used in both places at once. Estates that plan a phased migration on Standard licences have exactly one 180-day migration allowance to work with, and it applies to migrating the same workloads rather than to running two permanent environments.

Datacenter is the edition that behaves differently in Azure

If a substantial part of the estate is heading to Azure while the rest stays put, Datacenter is worth pricing on the dual-use rules alone. Licensed by virtual machine it permits indefinite simultaneous use on-premises and in Azure, which removes the migration-window pressure entirely. Allocated to an Azure dedicated host it permits simultaneous use for 180 days from allocation, and it carries the unlimited virtualisation right – any number of Windows Server virtual machines on that host, provided you allocate covered Datacenter licences for all its available physical cores. Standard has no unlimited virtualisation right in Azure at all.

SQL Server, which has its own arithmetic

SQL Server Enterprise and Standard core licences with active Software Assurance or qualifying subscription licences are eligible for Azure Hybrid Benefit across the vCore-based Azure SQL Database, Azure SQL Managed Instance and SQL Server on Azure Virtual Machines. The conversion ratios differ by edition and by service tier, so treat the SQL side as a separate calculation rather than an extension of the Windows one, and check the current ratios for the specific service you are deploying into. As with Windows Server, the benefit lasts only as long as the coverage: when Software Assurance or the subscription lapses, so does the entitlement.

Licence Mobility through Software Assurance is the related but distinct mechanism for SQL Server, and it matters if the destination is a hosting partner rather than Azure. It permits deployment in an Authorised Mobility Partner’s data centre, requires active Software Assurance, and requires the deployment to be registered with Microsoft using the licence verification form within ten days. Windows Server is not eligible for Licence Mobility, which is precisely why Azure Hybrid Benefit exists for it.

Extended Security Updates change the business case more than the discount does

For an estate carrying end-of-support servers, the largest number in the migration case is often not the compute discount. Extended Security Updates are free for qualifying Azure workloads – Azure Virtual Machines, Azure Dedicated Host, Azure VMware Solution, Nutanix Cloud Clusters on Azure and the Azure Stack portfolio including Hub, Edge and HCI – and, unlike Azure Hybrid Benefit, they do not require Software Assurance. On-premises, Extended Security Updates enabled by Azure Arc are a paid option billed per virtual core with an eight-core minimum per virtual machine, or per physical core with a sixteen-core minimum per server, and can alternatively be bought as licences through Commercial Licensing programmes.

Read that as an argument about sequencing rather than about clouds. If a server has to be moved anyway and it is out of support, moving it before the ESU bill arrives is worth more than the compute discount that follows. If it is fully supported and staying put for three more years, the ESU point does not apply and the comparison is the ordinary one.

Questions people ask about this