AHB — Azure Hybrid Benefit
Category: cloud
Last reviewed by the MSLicenseHub Licensing Desk.
Azure Hybrid Benefit (AHB) is a cost-saving program that allows organizations to apply their existing on-premises software licenses—specifically those with active Software Assurance (SA) or qualifying subscriptions—to workloads running in Microsoft Azure. By utilizing licenses the organization already owns, the Azure service fee is reduced to a "base compute" rate, effectively removing the bundled cost of the Windows Server or SQL Server software from the hourly cloud bill.
Technical and Licensing Mechanics
Azure Hybrid Benefit applies to several core Microsoft products, each with specific conversion rules:
- Windows Server: Organizations can apply Windows Server Standard or Datacenter licenses to Azure Virtual Machines. Each 16-core license (or set of 8-core licenses) can cover up to 16 cores of Azure VMs. A unique feature of the Datacenter edition is that it allows for simultaneous usage on-premises and in Azure, whereas the Standard edition generally requires a transition.
- SQL Server: This applies to Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VMs. The exchange ratio depends on the product version: for example, one core of SQL Server Enterprise edition typically translates to four vCores of Azure SQL General Purpose.
- Linux Subscriptions: AHB also extends to specific Linux distributions, such as Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES), allowing customers to bring their own software subscriptions to Azure.
Migration and Dual-Use Rights
To facilitate a smooth transition to the cloud, Microsoft provides "Dual Use Rights" for a period of up to 180 days. This allows the software to run on the physical local server and the Azure VM simultaneously while data and workloads are being migrated. Once the 180-day window closes, the on-premises instance must be decommissioned if the licenses are to remain allocated to Azure.
Common Misunderstandings
A frequent misconception is that any license can be used for AHB. In reality, licenses must have active Software Assurance (SA) or be purchased as a specific Software Subscription through a program like CSP (Cloud Solution Provider). Perpetual licenses without SA do not qualify. Furthermore, while Azure VM prices may drop by approximately 40% to 50% when the software fee is removed, the customer remains responsible for the underlying infrastructure costs (compute, storage, and networking).
Terminology and Related Concepts
| Term | Relationship to AHB |
|---|---|
| Software Assurance (SA) | The prerequisite maintenance program that enables AHB rights. |
| License Mobility | A separate benefit for products like SharePoint or Exchange; unlike AHB, it does not apply to the Windows Server OS layer. |
| Base Compute Rate | The price charged for an Azure VM when AHB is applied, equivalent to the price of a Linux VM. |
| Reserved Instances (RI) | A commitment to a specific VM size for 1-3 years; can be stacked with AHB for maximum savings. |
Practical Guidance for Procurement
When reviewing a Microsoft Customer Agreement (MCA) or Enterprise Agreement (EA) quote, Azure Hybrid Benefit is rarely listed as a line item with a price, as it is a usage right rather than a product. Instead, it appears as a configuration toggle within the Azure Portal or a "Bring Your Own License" (BYOL) designation in cost estimates. Procurement teams should audit their current Volume Licensing (VL) records to ensure they have enough core licenses with active SA before checking the AHB box in Azure, as an under-licensed state can lead to significant compliance findings during a vendor audit. Note that OEM licenses, which are pre-installed by hardware manufacturers on specific devices, are tied to that hardware and are not eligible for transfer to Azure via AHB.
Need this in a quote?
Our team translates glossary concepts into concrete licenses, part numbers and price lists.
Request a quote