Skip to content
Cloud Efficiency Hub

Azure Hybrid Benefit Not Enabled on Virtual Machines

The short version

Many organizations purchase Software Assurance or subscription-based Windows and SQL Server licenses that entitle them to use Azure Hybrid Benefit.

Aaran Bhambra

FinOps Engineer / DevOps Engineer @ WTW

Category
Compute
Reference
CER-0240
Type
Suboptimal Pricing Model

Explanation

Why the waste happens and who it affects.

However, if the setting is not applied on eligible resources, Azure continues charging pay-as-you-go rates that already include Microsoft licensing costs. This oversight results in paying twice-once for the on-premises license and once for the built-in Azure license. The inefficiency often goes unnoticed because licensing configurations are not centrally validated or enforced. Actual savings from enabling AHB depend on VM size, region, and whether it is combined with reservations; the Azure pricing calculator can estimate them for a given configuration.

Billing model

The pricing dimensions that drive this cost.

Azure bills Windows and SQL-based VMs either as license-inclusive (pay-as-you-go) or license-excluded (when Azure Hybrid Benefit is applied). Without AHB enabled, workloads that already own valid licenses are billed at the higher license-inclusive rate, resulting in duplicated spend.

How to detect

4 checks to find it in your estate.

  • Review all Windows and SQL Server virtual machines to determine if Azure Hybrid Benefit is enabled in their configuration
  • Correlate VM licensing status with internal Software Assurance or Microsoft volume license records to confirm eligibility
  • Evaluate the proportion of eligible VMs still billed at license-inclusive (pay-as-you-go) rates
  • Check whether governance policies exist to enforce AHB application during provisioning

How to fix

4 ways to remove the waste.

  • Enable Azure Hybrid Benefit for all eligible Windows and SQL-based VMs to apply owned licenses and reduce compute costs; for SQL Server on Azure VMs, the SQL Server license type is set separately on the SQL virtual machine resource (which requires the SQL IaaS Agent extension), independent of the Windows Server license type
  • Implement Azure Policy rules that audit or enforce the license type setting so AHB is applied to future deployments where eligibility applies
  • Maintain an up-to-date inventory of licensed assets and ensure license entitlements align with deployed resources
  • Regularly review licensing configuration compliance across subscriptions to prevent recurrence

Documentation

Vendor references for pricing and configuration.