Azure MACC: how to size and negotiate your Microsoft Azure Consumption Commitment.
A Microsoft Azure Consumption Commitment (MACC) trades a firm, multi-year spend pledge for 8–20% off retail. Size it wrong and you forfeit committed dollars at year-end. This note sets out what counts toward the commitment, how the drawdown and shortfall math actually works, and the levers — Marketplace decrement and joint EA negotiation chief among them — that decide whether MACC pays off.
MACC rewards spend you were going to make anyway — it does not reward optimism. Size the commitment to the consumption you can defend with data, not the number Microsoft's account team floats. Then widen what decrements it: routing Azure Marketplace spend through the commitment and negotiating the MACC jointly with your EA renewal are the two moves that most reliably convert a risky pledge into a discount you actually capture.
01 Key findings
MACC is a drawdown, not a reserve. Commit $10M in a year and consume $8M, and the $2M is forfeited — it does not roll forward by default. The single largest source of MACC loss is over-sizing against an optimistic ramp.
Discount scales with commitment size, from roughly 8% to 20%. Floors run ~8–10% at $10–25M and reach 15–20% above $100M, but the depth is negotiable only at scale and only against a credible alternative.
Marketplace decrement is the most under-used lever. Eligible Azure Marketplace and many ISV purchases can decrement the MACC. Buyers who route third-party software through the commitment hit their number without inflating first-party Azure spend.
The discount applies to retail, beneath other benefits. MACC sits on list price — before Azure Hybrid Benefit, reservations and Savings Plans. Enterprises that skip Hybrid Benefit leave 8–12% of additional discount on the table.
Ramp timing decides year-one waste. A commitment is binding from month one regardless of deployment. A firm that signs in April and reaches full utilisation in October can forfeit several million against minimal early consumption.
Negotiate the MACC with the EA, not after it. Microsoft prefers separate software and cloud conversations. Insisting on one joint commercial negotiation is the highest-value process choice a Microsoft-heavy buyer can make.
02 What counts toward MACC
The value of a MACC depends less on the headline discount than on what decrements it. The wider the set of eligible spend, the easier the commitment is to hit — and the smaller the shortfall risk. Map every line before you size.
| Spend category | Counts toward MACC? | Notes for sizing |
|---|---|---|
| First-party Azure consumption | Yes | Compute, storage, database, networking billed at PAYG or negotiated rates — the core of the drawdown. |
| Azure reservations & Savings Plans | Yes | Reserved and Savings Plan purchases decrement the commitment; discount stacks beneath, not on top of, the MACC. |
| Eligible Azure Marketplace / ISV | Often (MACC-eligible SKUs) | Marketplace and many transactable ISV offers decrement the MACC — the key lever for reaching the number. |
| Non-eligible Marketplace listings | No | Not every listing carries the MACC-eligible flag; verify per SKU before you count on it. |
| Microsoft 365 & Dynamics seats | No | SaaS licensing sits outside the Azure consumption commitment; negotiate it in the EA, not the MACC. |
| Support plans & premium SLAs | Typically no | Often excluded or a-la-carte; confirm and, where material, negotiate inclusion. |
03 Discount by commitment size
Discount floors climb with the annual commitment. These are indicative starting points; the depth above the floor is what negotiation buys, and only strategic accounts with a credible multi-cloud alternative reach the top of the range.
Crossing a tier boundary shifts both bargaining power and exposure. A $10M commitment might open at 8% with room to 9–10% for a strategic account; a $100M+ commitment can reach the high teens, but only with extensive commercial negotiation and often non-standard flexibility or exclusion terms. The floor is the promise; everything above it is earned at the table.
04 Drawdown & shortfall risk
Unlike a reservation you hold in reserve, MACC operates on annual drawdown. Under-consume and the gap is forfeited; the commitment resets to full the next year. Two variables drive the risk: how fast you ramp, and whether escalation is flat or stepped.
| Sizing input | Conservative structure | Aggressive structure |
|---|---|---|
| Year-one commitment | Set to ~70–80% of forecast to absorb ramp lag | Set at full forecast from month one |
| Escalation | Stepped, paused if consumption <85% in any year | Fixed annual step (e.g. $10M → $12M → $15M) |
| Shortfall treatment | Carry-forward or credit against next-year obligation | Forfeited at year-end |
| Overage rate | List minus 50% of MACC rate, up to ~115% of commitment | Full list price on every dollar over |
| Exit / migration | Wind-down credit if >50% of workload moves off Azure | Commitment terminates; unspent balance lost |
A MACC is binding from month one whether or not workloads are deployed. Sign a $10M commitment in April, spend six to nine months designing and migrating, and you can burn half the year at minimal consumption — forfeiting $3–4M before you ever reach steady state. Model the ramp curve, not the run-rate, and size year one to it.
05 The Marketplace decrement lever
Two levers do more than any discount-floor haggling to make a MACC safe: widening what decrements it, and negotiating it inside the EA rather than beside it.
Route eligible third-party software through the commitment. Many Azure Marketplace and transactable ISV purchases — security tooling, data platforms, analytics accelerators — carry a MACC-eligible flag and decrement the commitment dollar-for-dollar. Buyers running 30–50% of workloads on Marketplace partners can reach their MACC number without inflating first-party Azure spend, turning a shortfall risk into a procurement routing decision. Confirm eligibility per SKU and negotiate carve-ins for your top ISVs before signing.
Force one commercial conversation, not two. Microsoft's account teams prefer to negotiate the Enterprise Agreement and the Azure commitment separately, which fragments your leverage. Enterprises renewing Microsoft 365 or an EA achieve materially better combined terms by putting the MACC on the same table — trading committed cloud growth for concessions on price, support tier, ramp flexibility and Marketplace inclusion. For Microsoft-heavy estates this single insistence is often the highest-value move in the deal.
06 Sizing framework
Four inputs determine the right commitment number. Weight them to your situation before you name a figure to Microsoft.
Defensible consumption forecast
Model 3–5 years from current bills, Azure Advisor and migration timelines. Commit only to spend you can defend with line-of-sight confidence — anything speculative is forfeiture risk.
Eligible decrement base
Add reservations, Savings Plans and eligible Marketplace/ISV spend to first-party Azure. The wider the eligible base, the larger a commitment you can safely carry.
Ramp and escalation shape
Match year-one to the deployment curve and prefer stepped escalation with a pause trigger. Front-loaded flat commitments are where ramp waste concentrates.
Trajectory & exit risk
M&A-active or migration-prone organisations should size conservatively and negotiate wind-down credits; stable estates can size up for deeper discount.
07 Size up or size down
You have a firm, multi-year cloud strategy, a broad eligible decrement base including Marketplace, and high-confidence consumption data. Push into a higher tier to capture 13–20% — the discount rewards spend you were committing anyway.
Your run-rate is predictable but growth is measured. Size to ~80–90% of forecast, negotiate carry-forward and a 115%-of-commitment overage rate, and let Marketplace decrement absorb the variance.
You are mid-migration, M&A-active, or your workload mix is uncertain. Set year-one low with stepped escalation and a pause trigger, and secure an exit/wind-down clause before you commit a dollar.
08 Renewal levers
At renewal the choice is process, not just price. Bringing the MACC into the EA conversation generates the leverage; splitting them forfeits it.
Joint & forecast-led Recommended
Negotiate the MACC inside the EA renewal, sized to a defensible forecast, with Marketplace decrement, carry-forward, a pause-on-underuse trigger and a wind-down exit clause on the table together.
Split & optimism-led Weaker
Sign the MACC separately at the number the account team proposes. Leverage fragments, ramp waste is unhedged, and a business change can strand millions in unspent commitment.
Size and negotiate your MACC before you sign
Our Cloud & FinOps practice models the commitment against real consumption and negotiates the drawdown, decrement and exit terms.
The Licensing Edge
Weekly cloud and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.