Azure spend is built on three independent discount layers: the consumption commitment (MACC), the reservation layer (Reserved Instances and Savings Plans), and the BYOL layer (Azure Hybrid Benefit). The customers who optimise all three layers reduce Azure cost by 35–55% without touching a single workload. The customers who optimise only one — typically the commitment — leave 60–70% of the available savings on the table. Here is the playbook.
The MACC is a multi-year Azure consumption commitment in exchange for discount and credit. The standard structures are 1-year, 3-year and 5-year terms; the discount tier scales with both commitment volume and term length. Typical negotiated MACC pricing improves base consumption rates by 8–15% on the first commitment tier ($1M+ annual) and 15–30% on enterprise tiers ($10M+ annual). The MACC is the first negotiation; it sets the base price against which all other discount layers stack.
The MACC also enables credit application: a portion of the committed spend can be applied to non-Azure Microsoft products — typically GitHub Enterprise, certain Microsoft marketplace SaaS, or specific Azure marketplace listings. The credit flexibility is a meaningful negotiation point that customers frequently leave unaddressed. We have seen MACC structures negotiated to allow 30–50% of commitment volume to be applied to Marketplace and non-Azure SKUs.
The single largest MACC pitfall is over-commitment. Microsoft account teams have incentive to size MACCs at the high end of customer projections — the commitment scales the account's quota credit. Customers committing to 40% Azure growth over three years frequently find themselves with unspent commitment in year three, which converts to surrender (the commitment is consumed but the value is gone). Sound MACC sizing starts at 70–85% of base case projections, with growth headroom kept on-demand.
The commitment-sizing question is the single highest-leverage decision in the entire negotiation. We model it with you.
Azure Reservations apply to specific compute resources — VM SKUs, SQL Database vCores, Cosmos DB throughput — in exchange for a 1-year or 3-year usage commitment. Discount levels range from 30–55% versus on-demand pricing for 1-year reservations and 55–72% for 3-year reservations. The reservation applies automatically to matching usage; unused reservation hours are forfeit at month-end.
Azure Savings Plans for Compute are the more flexible variant — a 1-year or 3-year commitment to a specific hourly spend across compute services, with discount levels of 20–35% (1-year) and 35–60% (3-year). Savings Plans cover broader compute scope than Reservations but at a slightly lower discount level. The pattern most cost-effective for large estates is layered: Reservations on stable workloads with known SKUs, Savings Plans on variable workloads with changing SKUs.
Reservation utilisation is the leading reason reservation programs underperform. A 3-year reservation purchased at 55% discount delivers 55% savings only at 100% utilisation; at 60% utilisation the effective discount is 25%; at 40% utilisation, the reservation costs more than on-demand. The standard customer error is to over-purchase reservations to capture the discount, then under-utilise them in practice. Quarterly utilisation reviews and Reserved Instance exchange / cancellation should be a standard FinOps cadence.
The full MACC tiering benchmarks, reservation utilisation model, and the AHB optimisation workbook.
Azure Hybrid Benefit lets customers apply on-premises Windows Server and SQL Server licences with active Software Assurance to Azure compute, eliminating the Azure compute SKU component of the bill. AHB-eligible Windows Server licences typically reduce Azure VM cost by 40–50%. AHB-eligible SQL Server Enterprise Edition licences typically reduce SQL VM and SQL Managed Instance cost by 55–80%. The savings are large, immediate, and frequently un-claimed.
In our experience, 40–60% of enterprise Azure estates have meaningful AHB-eligible workloads that are running without AHB applied. The reasons are usually structural: the SAM team owns the Windows Server / SQL Server licences but does not engage with the cloud team; the cloud team builds Azure resources through automation that does not flag AHB-eligible options; nobody owns the cross-system reconciliation. The remediation is operational, not commercial — there is no negotiation required.
SQL Server with Software Assurance permits "dual-use" — the same licence can support an on-premises workload and an Azure workload during a 180-day migration window. Beyond 180 days, the licence must be assigned to one or the other. The dual-use window is the standard pattern for cloud migration; it is also frequently missed when migrations slip past the window.
The three-layer optimisation analysis takes two to three weeks and typically identifies 25 to 45 percent cost reduction without workload changes.
For Azure spend above $1M annually, independent advisory across the three discount layers typically captures cost reduction equal to five to fifteen times the advisory fee. Our license cost reduction practice models all three layers together before you sign the commitment.
We have run MACC negotiations from $500K to $200M annual commitment.
Weekly compliance intelligence for IT leaders.