The Microsoft Azure Consumption Commitment (MACC) is a contractual commitment by a customer to spend a fixed dollar amount on Azure consumption over a defined term — typically the three-year length of an Enterprise Agreement. In exchange, the customer gets favoured commercial treatment including Reserved Instance and Savings Plan eligibility, discount eligibility on consumption-based SKUs, and qualification for marketplace credit programmes. MACC is not the same as a flat discount. It is a commitment that unlocks the discount surface, where the actual discount comes from a combination of RIs, Savings Plans, EA-level negotiated discounts on specific service families, and marketplace pricing. In 2026, Microsoft is pushing MACC harder than ever because the company's compensation is increasingly weighted toward consumption commits over Office licence count. That pressure cuts both ways: Microsoft wants the commit, which means there is room to negotiate the surrounding terms harder than most buyers realise.
What MACC actually is (and isn't)
MACC is a multi-year contractual spend commitment, expressed as a dollar amount over a term (most commonly three years, matching the EA). It sits inside the Enterprise Agreement as a separate enrolment or addendum and obligates the customer to consume that dollar amount of qualifying Azure services over the term. If the customer consumes less, the unconsumed amount is owed at term-end. If the customer consumes more, the overage is billed at the prevailing rate (subject to whatever discount terms apply).
What MACC is not:
- Not a flat discount. MACC by itself does not deliver a fixed percentage off Azure pricing. It is the commitment that qualifies the customer for the discount instruments (RIs, Savings Plans, negotiated EA-level discounts on consumption-based services).
- Not a refund mechanism. Unspent MACC at term-end is typically owed, not forgiven. Some negotiations include "true-down" clauses, but they are exception cases, not the default.
- Not the same as MCA-E consumption commit. MACC is the EA-specific instrument. Microsoft Customer Agreement — Enterprise (MCA-E) has a parallel instrument with similar mechanics but different contractual surface.
- Not bound to specific services. MACC counts against most consumption-based Azure spend across IaaS, PaaS, AI services, and many marketplace transactions — with specific exclusions.
What counts against MACC (and what doesn't)
The list of qualifying spend is broad and changing. As of 2026, in scope:
- Standard Azure consumption (VMs, storage, networking, databases, AI services, etc.).
- Reserved Instance purchases (the upfront RI charge counts against MACC).
- Savings Plans for Compute (the committed dollar rate counts).
- Most Azure Marketplace transactions purchased through Microsoft (subject to the partner's MACC eligibility certification).
- Power Platform consumption when billed through Azure.
- GitHub Enterprise (recent expansion — verify the in-scope list at signing).
Out of scope:
- Microsoft 365 licensing.
- Dynamics 365 licensing.
- Windows Server licensing (the licence; the Azure compute consumption counts).
- Some marketplace transactions where the partner has opted out of MACC.
- Support charges (Unified Support is separately billed and does not count).
The "marketplace counts" expansion is the most procurement-relevant change in 2026. Marketplace purchases through the Azure portal can now be applied against MACC, which means third-party software bought through Microsoft can effectively be paid for by your MACC budget — a substantial workflow change for procurement teams that historically treated marketplace spend as separate.
The marketplace eligibility means MACC can be partially fulfilled by software purchases your business is already making. Mature procurement teams shift third-party software through the Azure Marketplace specifically to consume MACC dollars they would otherwise owe at term-end. This is a legitimate, Microsoft-supported move — not a workaround.
Sizing a MACC commitment properly
The single most common MACC mistake is overcommitting. Microsoft's sales motion will push for a MACC at the top of your projected three-year spend; the right size is at the floor.
The sizing discipline:
- Build a three-year Azure spend forecast. Not an aspirational one — a workload-based bottom-up forecast accounting for known migrations and known retirements.
- Identify the floor. What is the level of Azure spend you are confident will materialise even under the most pessimistic migration scenario?
- Subtract a 10–15% buffer. MACC underrun is owed; do not commit to the floor itself, commit to 85–90% of the floor.
- Stack the MACC with marketplace dollars. If you have $1M/year of third-party software purchases that can move through Azure Marketplace, build that into the MACC sizing.
- Negotiate the overrun terms. Overage above MACC should still get RI/Savings Plan rates. Many MACC contracts default to pay-as-you-go above the commit unless the overage terms are negotiated explicitly.
The asymmetry is important: overcommitting MACC creates a real liability owed at term-end; undercommitting MACC leaves money on the table only on the marginal discount surface above the commit, which is small. Bias toward undercommitting.
What MACC actually buys you
Beyond the commercial qualification, MACC unlocks several discrete benefits:
- Reserved Instance and Savings Plan eligibility on EA-level discount tiers that are not available to non-MACC customers.
- Marketplace dollar consumption against the commit, which is a meaningful budget optimisation lever for organisations with substantial third-party software spend.
- Negotiated discount stacks on consumption-based service families that Microsoft is willing to discount at the EA level (typically AI services, networking, and analytics families).
- Funding for migration credits. Microsoft will often release migration funding (FastTrack-equivalent or partner-delivered) against MACC commits.
- Co-sell motion priority. MACC customers are inside Microsoft's commercial motion in ways non-MACC customers are not, with implications for support priority and roadmap influence.
None of these benefits is automatic. Each is part of the MACC negotiation surface and should be specified explicitly in the agreement. The default contract gives you the qualification surface but not the discount depth — you have to negotiate that into the document.
MACC risk: the overrun and the underrun
Two failure modes:
Underrun: you committed $20M over three years and only consumed $14M. The $6M shortfall is owed at term-end. Some agreements include partial true-down clauses (e.g., 80% of unspent forgiven) but the default contract has no forgiveness. The right defence is conservative sizing on the front end, not negotiation on the back end.
Overrun: you committed $20M and consumed $32M. The $12M overage is billed — ideally at MACC-eligible discount rates but only if the overage terms were specified. Default contracts often push overage to pay-as-you-go, which can be 30–50% more expensive than the equivalent committed rate. Negotiate the overage rate at signing or you will discover the gap when the bill arrives.
MACC negotiation positions that work in 2026
Three positions to take into the negotiation:
1. Conservative size with annual true-up review. Commit to 85–90% of the forecast floor and propose an annual review point where the commit can be increased (not decreased) if usage tracks ahead of plan. Microsoft will accept this because the annual-up clause increases their forecast confidence.
2. Marketplace eligibility certification. Specify in the contract that all marketplace transactions through the customer's Azure Marketplace will count toward MACC, subject to partner eligibility. This pre-empts the partner-by-partner verification that otherwise blocks the marketplace-MACC integration.
3. Overrun pricing at RI/Savings Plan rates. Specify that compute spend above MACC continues to receive Reserved Instance or Savings Plan discount rates where applicable. This closes the overrun trap.
All three are negotiable in 2026. Microsoft's compensation motion on MACC means there is real flexibility on the surrounding terms — use it.
Anonymised case study: $14M MACC, manufacturing client
A 23,000-employee manufacturing client had a 2023 MACC of $18M over three years that they had underconsumed by $4.8M with six months remaining. Our intervention: model the realistic burn-down to identify $1.6M of marketplace transactions (third-party CAD, PLM, security tools) that could be moved through the Azure Marketplace and would qualify against MACC; accelerate the migration of an on-premises analytics workload by 90 days; and negotiate a partial true-down clause for the residual. Net outcome: $3.1M of the original $4.8M shortfall absorbed via marketplace and accelerated consumption, with $1.7M negotiated as a 50% true-down credit applied against the renewal MACC. Total recovered value: $2.6M.
MACC negotiation checklist
- Build a bottom-up three-year Azure spend forecast.
- Identify the floor and commit at 85–90% of it.
- Specify marketplace eligibility certification in the contract.
- Negotiate overrun pricing at RI/Savings Plan rates.
- Negotiate a partial true-down clause for end-of-term unconsumed amounts (10–30% forgiveness is achievable).
- Co-term MACC dates with EA renewal for stack-able negotiation.
- Time the MACC close to the Ignite 2026 window for the widest discount surface.
- Layer Savings Plans and RIs against the MACC commit, not separately.
MACC is the lever Microsoft cares about most in 2026. Treat it as the most important negotiation in your Azure stack — not as a procedural commitment.