Azure Hybrid Benefit is the Software Assurance-mediated bridge from on-prem Windows Server and SQL Server licences to the Azure estate. The Admodum read on the eligible workloads, the dual-use window, the apply-versus-PAYG arithmetic and the renewal disposition.
Azure Hybrid Benefit is a Software Assurance-mediated entitlement, not a discount programme. A buyer that holds a perpetual on-prem licence with active Software Assurance on Windows Server or SQL Server is entitled to apply that licence to an equivalent Azure workload and pay a reduced rate against the list PAYG Azure price.
The reduced rate strips out the embedded licence cost: the PAYG Windows Server VM line on Azure carries the underlying Windows Server licence in its rate, and the Hybrid Benefit replaces that embedded licence with the buyer's own SA-bearing on-prem entitlement. The buyer continues to pay for compute, storage, networking and the wider Azure fabric; the buyer stops paying for the operating-system licence twice.
The wider Software Assurance framework sits at the Software Assurance benefits overview; the wider EA framework sits at the Enterprise Agreement overview; the wider editorial sits in the Microsoft pillar.
On Windows Server the Hybrid Benefit applies on a per-core basis. A buyer with SA on Windows Server Standard or Datacenter holds an entitlement to apply the on-prem core licences to Azure VMs running Windows. The Standard SA bearer applies the licence to the on-prem workload or to the Azure workload; the Datacenter SA bearer applies the licence to the on-prem workload and to the Azure workload concurrently during the dual-use window.
The arithmetic against PAYG is meaningful but not extreme on Windows Server alone: the PAYG line on a typical Windows-VM SKU on Azure carries a markup against the equivalent Linux line that reflects the embedded Windows licence; the Hybrid Benefit applied strips that markup. The saving runs in the order of 30 to 40 percent against the PAYG Windows rate, before any reserved-instance overlay.
The wider Windows Server licensing surface sits at the Windows Server core licensing spoke; the wider Azure reserved-instance overlay sits at the Azure reserved instances spoke (forthcoming).
On SQL Server the Hybrid Benefit is the principal value driver. SQL Server SA covers application to Azure SQL Database (managed PaaS), Azure SQL Managed Instance and SQL Server on Azure VMs. The arithmetic against PAYG runs above 50 percent on most SKUs; on Enterprise Edition workloads the saving runs above 80 percent against the equivalent licence-included PAYG line on Managed Instance.
The Enterprise-to-Standard Step-Up entitlement under SA (one Enterprise Edition core licence covers up to eight Standard Edition cores on Azure) is the second order benefit; the buyer with surplus Enterprise SA on the on-prem estate after consolidation carries an outsized Hybrid Benefit pool to apply against the Azure workload.
The wider SQL Server licensing surface sits at the SQL Server licensing spoke; the wider SQL Server high-availability surface sits at the SQL Server AlwaysOn spoke (forthcoming).
The dual-use window allows the buyer to run the on-prem workload and the Azure target concurrently during a migration without separately licensing the Azure side. The window is typically 180 days on a per-licence basis, not on a per-tenant or per-subscription basis. After the window closes, the on-prem instance must be retired (or licensed separately) and the Azure instance carries the Hybrid Benefit applied.
The window is consequential for migration planning. A buyer moving SQL Server Enterprise from on-prem to Azure SQL Managed Instance within 180 days of cut-over carries no incremental licence cost on either side during the migration; the same migration stretched across 18 months without a per-licence dual-use plan carries a duplicate licence cost on the Azure side for the period that exceeds 180 days.
The buyer-side artefact to maintain is a per-licence migration ledger: every SA-bearing core, the on-prem instance, the Azure target, the cut-over date and the dual-use window expiry. Without the ledger the migration runs against a tenant-wide assumption that does not survive an audit.
The decision to apply the Hybrid Benefit or to run PAYG is workload-by-workload arithmetic. The Hybrid Benefit applied carries the SA renewal cost on the buyer-side (the SA line on the EA is paid whether the entitlement is applied or not); the PAYG line carries the embedded licence; reserved instances stack on top of either. A buyer with surplus SA carries near-zero marginal cost on the Hybrid Benefit application, where the SA renewal would happen regardless.
A buyer mid-rationalisation runs the inverse arithmetic: the SA on the on-prem residue is the question, not the Azure target. A buyer planning to drop SA on a portion of the on-prem estate, but to retain the Azure workload, runs the calculation against the SA renewal cost versus the PAYG embedded licence; in many SQL Server cases the SA renewal is cheaper than the PAYG embedded licence, even where the on-prem footprint is retired.
The reserved-instance overlay is the third axis. An Azure Reserved Instance with the Hybrid Benefit applied stacks the licence saving (Hybrid Benefit) on top of the compute saving (reserved instance); the combined discount against the on-demand line frequently exceeds 70 percent.
The buyer-side artefacts to hold against the Hybrid Benefit are: the SA-bearing on-prem inventory (every core, every product, every SA term-end), the Azure consumption baseline (every VM, every database, every managed instance), the per-licence migration ledger (every cut-over, every dual-use window expiry), the apply-versus-PAYG workload ledger (which workloads carry the Hybrid Benefit applied; which run PAYG), the renewal-time disposition (which SA is retained for Hybrid Benefit application; which is dropped).
The renewal-time conversation is then a negotiation against artefacts. The publisher's renewal proposal carries SA renewal across the on-prem portfolio; the Azure MACC carries the consumption commit; the buyer's decision integrates both surfaces, against the artefacts; the SA drops, the SA retentions, the MACC sizing and the reserved-instance plan are taken on shared arithmetic.
The MCA-E transition does not remove the Hybrid Benefit. A buyer with an SA-bearing on-prem residue retains the application against the Azure workload after migrating the cloud-subscription portfolio to MCA-E. A buyer with no SA, MCA-E or otherwise, carries no Hybrid Benefit entitlement and pays the PAYG embedded licence; the wider MCA-E framework sits at MCA-E versus EA. The wider engagement sits in the Microsoft practice; the aggregated reading list sits in the Microsoft knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The maintenance overlay that mediates the Hybrid Benefit entitlement.
The product against which the Hybrid Benefit delivers its largest single saving.
The consumption commit on which the Hybrid Benefit-applied workload burns.
A senior Admodum Microsoft advisor will read your SA-bearing on-prem inventory against your Azure consumption baseline and produce a per-licence application ledger on a private call. Active renewal moments route to the Renewal Programme.