A MACC is a multi year agreement to spend an agreed amount on Azure in return for a discount tier and other concessions, and its defining feature for a buyer is the shortfall clause: whatever portion of the commitment you have not consumed by the end of the term is generally still payable. That single clause flips the sizing logic. An oversized MACC is not a harmless ambition, it is a contractual obligation to pay for capacity you may never use. The safe size is the amount of eligible spend you can defend with a forecast, with margin held back for uncertainty, and with every category of qualifying consumption mapped so your realistic drawdown is as high as it genuinely is. Sized that way, the MACC earns its discount without exposing you to a year end shortfall bill.
Here is how the commitment works, what counts toward it, and the forecast discipline that keeps you safe.
What is a MACC and how does it work?
The Microsoft Azure Consumption Commitment is the enterprise level pledge that sits on top of your day to day Azure spend. You agree to consume an agreed total over a multi year term, and in exchange Microsoft offers a discount tier and other commercial concessions that scale with the size of the commitment. Eligible Azure consumption draws the commitment down month by month. The structure rewards customers who can credibly forecast large, steady spend, because the bigger and more certain the commitment, the better the terms on offer. But the same structure punishes optimism, because the commitment is a floor you have promised to reach, not a ceiling you are allowed to approach.
What happens if you do not meet a MACC?
The shortfall clause is the part every buyer must price in before signing. If you reach the end of the term having consumed less than you committed, the unspent balance is generally still owed. In practice that means an aggressive MACC, signed on a hockey stick growth assumption that did not materialise, converts directly into a payment for Azure you never used. The discount you negotiated up front is dwarfed by the shortfall you pay at the end. This is the asymmetry that should govern sizing: undershooting your true spend with a conservative MACC costs you a slightly smaller discount, while overshooting it costs you the full gap. Given that asymmetry, the rational move is to size below your central forecast, not at or above it.
What spend counts toward MACC drawdown?
Drawdown is wider than many buyers assume, and underusing it is a common, expensive mistake. Most first party Azure consumption counts toward the commitment, but so does a broad set of eligible Azure Marketplace purchases, third party software and services bought through the Marketplace that qualify to draw down the MACC. Teams that route eligible procurement through the Marketplace can lift their realistic drawdown rate materially, which both protects against shortfall and makes a given commitment size safer to sign. The work before signing is to map every category of eligible spend, first party and Marketplace, against your forecast, so the commitment is sized against true qualifying consumption rather than a narrow slice of it.
A European SaaS company was offered a MACC sized on an ambitious three year growth plan, with a discount tier that improved at the larger commitment. Modelling the forecast against the shortfall clause showed the proposed size assumed growth the company could not yet defend, exposing it to a sizable year end shortfall if expansion slipped. Two changes fixed it. The commitment was sized to a conservative, defensible forecast with margin held back, accepting a slightly lower discount tier in exchange for removing the shortfall risk. And eligible Azure Marketplace procurement was mapped into the drawdown, lifting the realistic consumption rate. The result was a MACC the company was confident it would meet, with the negotiated discount kept and no exposure to paying for unused commitment. The figures are verified against billing data and anonymised.
How do you build a forecast you can defend?
A MACC is only as safe as the forecast under it. Build the forecast bottom up from current Azure consumption, segmented by workload and business unit, then layer growth that is committed rather than hoped for: signed customers, funded projects, and migrations with dates. Treat speculative expansion as upside that could lift drawdown, never as base case that must be met. Stress the forecast against a downside where growth stalls, and size the commitment so that even in that downside you consume the full MACC. Then use the discount tiers as a negotiation input, not a target: if a larger tier needs spend you cannot defend, the better discount is not worth the shortfall exposure. The forecast is also your leverage, because a credible, well evidenced number is what lets you push on terms from a position of strength.
Where does the MACC sit against reservations and savings plans?
The MACC is the outer layer; Azure Reservations and the Azure Savings Plan sit inside it. The enterprise commitment sets your discount tier and the spend floor, while reservations and the savings plan discount specific compute against on demand rates and themselves count toward drawdown. The two work together: a well sized MACC gives you the commercial tier, and disciplined reservation and savings plan coverage on the workloads underneath both cut unit cost and help you reach the commitment. Size them in that order, MACC to the defensible forecast first, then reservation and savings plan coverage to the steady workloads within it, so each layer reinforces rather than compounds your commitment risk.
Frequently asked questions
What is a MACC and how does it work?
What happens if you do not meet a MACC?
What spend counts toward MACC drawdown?
Size your MACC with us on your side
We model Azure consumption, map eligible drawdown including the Marketplace, and size a MACC to a forecast you can defend, so you keep the discount without the shortfall risk. We sit on your side of the table, take zero provider commissions, and answer only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on either a Fixed Fee or a no risk Gainshare basis. Book a strategy call to scope it, and follow more in The Cloud Spend Navigator.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.