Azure MACC Negotiation: Size the Commit, Keep the Flex
Microsoft sized MACC proposals over ran real consumption by 22 to 38 percent across the commitments we benchmarked in 2024 to 2025. On the $48M proposal worked in this paper, the oversize is worth $14.2M in cash.
Prepared by Redress Compliance · June 2026 · Representative Azure estate scenario (benchmark scenario, not a quote)
Executive Summary
Since Microsoft removed programmatic Azure discounting from the Enterprise Agreement, the MACC is the only vehicle that earns an Azure discount. The commit number you sign now defines your renewal economics, because the Azure Commitment Discount, the flexibility rights, and the Marketplace rules all hang off it.
Microsoft's sizing is not your sizing. Across 2024 to 2025 engagements, Microsoft proposed commits 22 to 38 percent above the trailing consumption path. In the scenario worked here, the $48M proposal costs $48.0M in cash at realistic consumption. The right sized $30M commit costs $33.8M. The difference is $14.2M.
The headline discount is the least decisive part of the deal. The structure decides the outcome: true down rights, carryover, transferability across tenants, and Marketplace decrement. One Fortune 500 healthcare client moved from 14 to 18 percent ACD with a 25 percent annual flex down by negotiating structure before price.
Five questions decide the outcome and structure this paper: why the MACC defines EA renewal economics from 2024 onward, how true down rights convert the commit from risk into opportunity, the discount tiers Microsoft applies at MACC scale points, the transferability provisions across subscriptions and tenants, and how the Marketplace rules, Microsoft's EDP equivalent, decrement the commit.
Why the MACC Defines EA Renewal Economics from 2024 Onward
The Enterprise Agreement no longer carries programmatic Azure price levels. Azure discount now arrives only through a negotiated Azure Commitment Discount attached to a consumption commitment. No commit, no discount, whatever your seat count or tenure.
The agreement vehicle underneath is moving too. Since November 1, 2025, Microsoft has been moving sub 2,400 seat direct EA customers onto MCA-E at renewal. A MACC can sit on either an EA enrollment or an MCA billing account, but the remaining commit does not migrate by itself. The transition is a negotiation window, not paperwork.
The instrument itself is simple. A MACC is a contractual pledge to consume an agreed dollar amount of eligible Azure and Marketplace services over the term. Consume less and Microsoft invoices the difference at term end.
Not all spend works the commitment down. The decrement map below is where most tracking errors start:
| Spend category | Decrements the MACC? | Note |
|---|---|---|
| Eligible Azure services consumption | Yes | Counted at billed value, after the ACD is applied |
| Reservation and savings plan purchases | Yes | Upfront purchases decrement at transaction time |
| Azure benefit eligible Marketplace offers | Yes, at 100 percent | Eligibility flag is visible per offer in the portal |
| Non eligible Marketplace offers | No | ISV has not met the IP co sell requirements |
| Unified support, M365, Dynamics seats | No | Seat based products never touch the MACC |
| Azure spend transacted through CSP | No | Only direct EA or MCA billing scope spend counts |
Size the Commit on Trailing Draw, Not Microsoft's Forecast
Microsoft sizes the commit from its own growth model: your stated migrations, its AI consumption assumptions, and the seller's quota. Across the MACC files we benchmarked in 2024 to 2025, that model over ran the trailing consumption path by 22 to 38 percent.
The worked scenario: an estate consuming $12.0M of Azure at list over the trailing twelve months, growing about 6 percent organically. Realistic list consumption runs $12.0M, $12.8M, and $13.6M over the next three years, $38.4M in total. Microsoft proposes a $48M three year MACC at 14 percent ACD. The evidence supports $30M at 12 percent.
| Measure, 36 month term | $48M proposal at 14% ACD | $30M right sized at 12% ACD |
|---|---|---|
| Realistic list consumption | $38.4M | $38.4M |
| Billed after ACD | $33.0M | $33.8M |
| Commit decremented at term end | $33.0M of $48.0M | $30.0M of $30.0M, covered by month 33 |
| Shortfall invoiced at term end | $15.0M | $0 |
| Total cash out | $48.0M | $33.8M |
Benchmark scenario, not a quote. Billed figures: $38.4M list at 86 and 88 cents on the dollar respectively.
The proposal's extra two ACD points are worth about $0.8M on billed consumption over the term. The shortfall they ride in on is worth $15.0M. Never buy discount with commit you cannot burn.
The Discount Tiers Microsoft Applies at MACC Scale Points
Microsoft publishes no ACD price list. The tiers are real but unwritten, and the opening offer almost always sits below the band your commit size already qualifies for. These are the ranges from our engagement file:
| Three year commit | Observed ACD range | Typical first offer |
|---|---|---|
| Under $5M | 0 to 5% | 0 to 2% |
| $5M to $15M | 5 to 9% | 3 to 5% |
| $15M to $35M | 8 to 13% | 6 to 9% |
| $35M to $75M | 12 to 18% | 9 to 13% |
| Over $75M | 16 to 24% | 13 to 18% |
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025.
Two tier mechanics matter more than the opening number. ACD can step up mid term when consumption crosses an agreed threshold, applied to the remaining term. The clause costs Microsoft little and is rarely volunteered: ask for the step schedule in writing.
Term length is the other tier lever. A five year term typically buys 2 to 4 additional points. Price those points against the flexibility you surrender.
Oversize in Microsoft proposed commits.
Across the MACC files we benchmarked in 2024 to 2025, Microsoft's proposed commit exceeded the estate's trailing consumption path by 22 to 38 percent, before any negotiation.
ACD gained on renegotiated paper.
Commitments renegotiated in 2025 to 2026 landed 3 to 7 percentage points more ACD than 2023 to 2024 paper at equivalent commit levels, when sizing evidence and competitive tension were on the table.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025.
True Down Rights Turn the Commit from Risk into Opportunity
A standard MACC has no true down. Every flexibility provision is negotiated paper, and all of it must land before signature. After signature the options narrow to consuming harder or paying the shortfall.
The ask list, in priority order:
- Annual true down: the right to reduce the remaining annual commit. A 20 to 25 percent annual flex down is achievable at signature when consumption evidence is on the table.
- Ramp schedule: a lower year one commit that follows the migration plan instead of averaging it across the term.
- Carryover: overconsumption in one contract year credits the next year's commit instead of vanishing.
- Shortfall rollover: unconsumed commit converts to prepayment credit or rolls into the renewal MACC, without requiring a new oversized commitment as the price of relief.
- Divestiture relief: the commit reduces pro rata when a divested business unit leaves the billing scope.
The structure is worth more than the rate. One Fortune 500 healthcare client was proposed a $4M three year MACC at 14 percent. Reframing the negotiation around true down and transferability landed 18 percent with a 25 percent annual flex down. The flex down was never exercised. Its existence changed Microsoft's sizing behavior.
Transferability Across Subscriptions, Tenants, and Affiliates
A MACC attaches to a billing scope, an EA enrollment or an MCA billing profile. Every subscription under that scope decrements automatically. The trap sits at the edges: multiple enrollments, multiple tenants, acquisitions, and the EA to MCA-E migration itself.
| Provision | Default behavior | What to negotiate |
|---|---|---|
| Multiple EA enrollments | Commits do not pool across enrollments | Consolidate billing scopes, or written cross enrollment decrement |
| Multiple tenants on MCA | Tenants can associate to one billing account and share MACC and ACD | Confirm association rights for every affiliate in the agreement text |
| Acquisitions | Acquired spend counts only once moved under the billing scope | Affiliate language admitting acquired entities without Microsoft consent |
| Divestitures | The commit survives intact at full size | Pro rata reduction, or transfer of a share to the divested entity |
| EA to MCA-E migration | Remaining commit does not move automatically | Novation of the remaining commit and the ACD onto the new paper |
The Marketplace Rules: Microsoft's EDP Equivalent, Done Better
AWS caps Marketplace decrement against an EDP at 25 percent of the commitment. Microsoft counts Azure benefit eligible Marketplace purchases at 100 percent. It is the most underused lever in MACC management.
- Eligibility is per offer, not per vendor: only offers flagged Azure benefit eligible decrement, which requires the ISV to meet Microsoft's IP co sell requirements. The flag is visible in the portal before you transact.
- Private offers count in full: pricing negotiated directly with the ISV decrements at 100 percent when transacted through the Marketplace.
- CSP routed Marketplace spend does not count: only purchases on your own EA or MCA billing scope decrement your MACC.
In the worked scenario, routing $1.2M per year of existing ISV renewals through eligible private offers adds $3.6M of decrement over the term:
| Decrement source, 36 months | Against the $48M proposal |
|---|---|
| Azure services billed, after 14% ACD | $33.0M |
| Marketplace eligible ISV spend routed | $3.6M |
| Total decrement | $36.6M |
| Residual shortfall | $11.4M |
Read the chart the way a CFO will. Marketplace routing is a mitigation, not a cure. Size the commit first, then route eligible third party spend to build headroom, not to rescue a number you should never have signed.
The Negotiation Sequence
MACC outcomes are decided by sequencing. The buyer who arrives with a consumption baseline before Microsoft presents a forecast controls the sizing conversation for the rest of the deal.
Build the baseline
Pull trailing 24 month consumption, strip one time migration spikes, and map which ISV contracts are Marketplace eligible. The output is one defensible commit number with evidence behind it.
Structure before price
Benchmark the ACD band for your tier, then table the structural asks in writing: true down, ramp, carryover, transfer and novation language, and the mid term step schedule. Only then discuss the rate.
Sequence and close
Tie the MACC to the EA or MCA-E renewal so concessions trade across both. Force deal desk review, watch the stacking rule on signature dates, and never sign Microsoft's forecast.
Our Recommendations
Build the consumption baseline before Microsoft does
Trailing 24 months, one time spikes stripped, growth stated on your plan. The first credible number on the table anchors the sizing conversation.
Commit at the evidence floor
Size to what consumption history defends, not the forecast. Take a written mid term ACD step up for the growth case instead of carrying it as commit risk.
Negotiate structure before rate
True down, ramp, carryover, shortfall rollover, and transfer language move real money. The last ACD point rarely does.
Route eligible ISV spend through the Marketplace
At 100 percent decrement, redirected third party renewals build commit headroom that costs nothing. Verify the eligibility flag per offer before counting it.
Sequence the MACC with the agreement renewal
The EA to MCA-E transition is the leverage moment: novate the remaining commit and the ACD onto the new paper, and mind the stacking rule on signature dates.
Treat the MACC as the renewal, not a side letter. The commit number, the ACD, the flex rights, and the Marketplace rules are one negotiation, and Microsoft negotiates them as one. The buyer side counter is evidence: a trailing consumption baseline, the tier benchmark for your scale point, and structural asks tabled in writing before price.
- Fastest leverage: the sizing evidence. A commit cut from $48M to $30M at realistic consumption is worth $14.2M, more than any discount point on the table.
- Largest single protection: a written annual true down of 20 to 25 percent. It rarely gets exercised; it always changes Microsoft's sizing behavior.
Redress Compliance is 100 percent buyer side, with 500+ enterprise clients and $2B+ under advisory. We are glad to tie a meaningful part of the fee to delivered value.
