The Microsoft Azure Consumption Commitment is the largest single number on most Microsoft EA order forms. The commit is leverage in both directions. This guide is the buyer side playbook for structure, discount bands, overage rules, and the exit options that survive renewal.
The Microsoft Azure Consumption Commitment, MACC, is a contractually committed multi year Azure spend tied to the Enterprise Agreement. The deal carries a discount band on commit size, an overage rule above commit, and a shortfall rule at term end.
The buyer side discipline is to size the commit honestly, capture the discount, and write the exit terms upfront.
Pair this guide with the MACC commit to consume reference, the Azure FinOps framework, the Azure cost playbook, the EA renewal playbook, and the Microsoft hub.
MACC stands for Microsoft Azure Consumption Commitment. It is a contractually committed Azure spend, signed under the Enterprise Agreement, tracked against monthly Azure invoices.
The Microsoft Enterprise Agreement carries three commit shapes. Server and Cloud Enrollment for software, Enterprise Subscription Enrollment for M365 and Office, and the Azure prepayment plus MACC for Azure.
MACC replaced the older monetary commitment structure in 2019. The headline change was the move to a contractual commit instead of a prepaid balance. The new model gives Microsoft revenue assurance and gives the customer a discount band tied to commit size.
Azure list rates apply equally across all customers. The discount lives in the EA price sheet, applied as a percentage off the list price for each service. The percentage is set by the MACC tier.
| Tier | Annual commit | Typical discount | Negotiation room |
|---|---|---|---|
| Entry | $250K to $1M | 5 to 10 percent | Limited |
| Mid | $1M to $3M | 10 to 15 percent | Moderate |
| Large | $3M to $10M | 15 to 22 percent | Strong |
| Strategic | $10M to $25M | 20 to 28 percent | Strong, with executive sponsor |
| Premier | $25M plus | 25 to 35 percent | Full custom price sheet |
The MACC commit is bidirectional. Spend above the annual commit prices at Azure rate card with the EA discount applied. Spend below the annual commit creates a shortfall at term end.
If the cumulative Azure consumption at the end of the MACC term falls below the cumulative commit, Microsoft has the contractual right to invoice the difference as a single line at the EA settlement. The settlement amount is the shortfall multiplied by the EA discount price sheet. Negotiate a written carry forward or a forgiveness clause when sizing the commit.
Not every Azure dollar reduces the MACC balance. Eligibility is set in the Product Terms. The eligibility rules drift over time and need a year on year refresh.
| Category | Counts | Notes |
|---|---|---|
| Compute, storage, networking | Yes | Pay as you go and reserved capacity |
| Azure database services | Yes | SQL Database, Cosmos DB, MySQL, Postgres |
| Azure AI and ML | Yes | Includes Azure OpenAI Service |
| Reserved Instances | Yes | Burndown at the commit date, not the consumption date |
| Marketplace third party | Conditional | Subset of marketplace approved for MACC eligibility |
| Power Platform | Selective | Some SKUs eligible, most are not |
| Microsoft 365 | No | EA Subscription Enrollment, not MACC |
| Dynamics 365 | No | Separate enrollment |
The MACC term ends at the EA renewal. Three exit shapes apply. Renew, transition, or wind down. Each shape has a specific contract structure and a specific risk profile.
The Azure MACC negotiation playbook runs in five moves. The moves apply equally to a new MACC and to a renewal. Sequence matters.
The renewal team modeled the next MACC against actual Azure consumption, not against last cycle’s plan. The commit dropped by twenty percent and the discount band stayed. Microsoft signed because the alternative was a true MCA E switch.
The seven step checklist below stands a real Azure MACC negotiation up in twelve weeks.
Yes. The Microsoft Customer Agreement for Enterprise, MCA E, carries a MACC equivalent. The mechanics are similar but the order form structure changes. The EA MACC and the MCA E MACC are not interchangeable mid term. The decision to switch happens at the EA renewal.
Yes. Azure OpenAI Service consumption is eligible Azure spend under the standard MACC terms. The burndown applies at the standard service rate card. Some enterprises pre allocate part of the MACC explicitly to Azure OpenAI to anchor the budget and the visibility, although the commit itself remains pooled.
Unused annual commit rolls forward within the MACC term by default. At term end the cumulative shortfall converts to a back billed invoice unless the order form carries a forgiveness or carry forward clause. The buyer side discipline is to write the term end behavior into the contract before signature, not after the shortfall is visible.
MACC is a contractual commit on total Azure spend over a multi year window with a discount band tied to size. A Reserved Instance is a specific compute or database capacity reservation with a deeper discount applied to that specific resource. RIs stack on top of MACC. The two work together rather than substituting for each other.
Redress runs the consumption history pull, the run rate model, the commit right sizing, the discount band benchmark, the shortfall clause draft, the RI overlay model, and the renewal anchor. Engagements run as a focused twelve week sprint before the EA renewal or as part of the wider Microsoft vendor management program. Independent buyer side throughout.
Rarely. Microsoft treats the MACC as a fixed contractual commitment for the term. Mid term renegotiation happens only under documented M and A, divestiture, or material business event clauses that have to be written into the original order form. The right time to renegotiate is at the renewal eighteen months out, not mid term.
Redress runs Azure MACC negotiations as part of the Microsoft advisory practice. The work covers the consumption pull, the run rate model, the commit right sizing, the discount band benchmark, the shortfall and carry forward clauses, and the RI overlay. Programs run as a focused twelve week sprint or as part of the wider Vendor Shield subscription.
Read the related Renewal Program, Benchmark Program, Software Spend Assessment, Benchmarking framework, about us, management team, locations, and contact pages.
A buyer side reference on the Microsoft Enterprise Agreement renewal cycle. Eighteen month preparation timeline, MACC sizing, discount band benchmarks, Copilot guardrails, and the negotiation moves that hold across hundreds of EA renewals.
Independent. Buyer side. Built for CFOs, CIOs, and procurement leaders carrying Microsoft EA renewals. No Microsoft influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The renewal team modeled the next MACC against actual Azure consumption, not against last cycle's plan. The commit dropped by twenty percent and the discount band stayed. Microsoft signed because the alternative was a true MCA E switch.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
EA renewal patterns, Azure MACC benchmarks, Copilot guardrails, MCA E transition lessons, and the wider Microsoft commercial leverage signals across every program we run.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
