The Microsoft Azure Consumption Commitment, or MACC, is the contract vehicle through which enterprises commit a defined Azure spend across the EA term in exchange for tier based discounts and program eligibility. Microsoft positions the MACC as a discount instrument. Across our 89 Azure engagements, the discount is the smallest variable in the MACC conversation. The eligibility burn rules, the marketplace burn rules, the rollover treatment, and the funding programs the MACC unlocks all carry more dollar weight than the headline discount tier.
The MACC functions as three distinct instruments at once. A minimum spend floor that protects Microsoft revenue across the term. An eligibility lever that unlocks Azure migration funding, marketplace burn, and specific incentive programs. A discount mechanism that prices first party Azure consumption against a tier table. The buyer side negotiation strategy is shaped by the fact that the three roles are bundled into one contract clause. Concessions on one role can be traded against another.
The MACC is more than a discount instrument. The buyer side negotiates against the full set of benefits the commit enrollment unlocks.
The commit also creates three structural risks. Underconsumption leaving the commit unspent at term end. Stranded capacity if a workload migrates off Azure mid term. Marketplace shopping restricted to approved sellers. Each risk has a contract clause that can mitigate it. None of those clauses are in the default Microsoft template.
The MACC negotiation is structurally a five clause exercise. Each clause has standard Microsoft defaults and a meaningful buyer side counter position. The clauses interact. A strong rollover plus true down combination is worth more than a marginally higher discount tier.
The burndown eligibility clause defines which Azure consumption counts toward the MACC. Defaults are restrictive. First party Azure infrastructure and platform services only. Buyer side teams negotiate broader eligibility including approved Azure Marketplace partners, Azure OpenAI Service, and selected first party SaaS products that run on Azure infrastructure. Each addition to eligibility is essentially a free discount on those line items.
Marketplace burn is conceded at most Fortune 1000 renewals once requested. The defensible buyer side position is unlimited marketplace burn against the commit. The typical landing is full burn for Microsoft preferred ISV partners, with a percentage cap (commonly twenty five percent of commit) for other marketplace transactions. The cap is the variable. The principle is conceded.
Rollover is the highest dollar protection in the commit. Without rollover, year one underconsumption is forfeited at anniversary. The defensible buyer side position is full rollover. The typical landing is twenty to thirty percent capped rollover or one time rollover with downstream restriction. Even a capped rollover materially changes the risk profile of the commit.
The true down right allows the buyer side to reduce the commit at each anniversary if documented consumption is below commit. Microsoft account teams resist true down because it undermines the revenue floor function of the MACC. The buyer side counter is a capped true down right (commonly ten to fifteen percent per anniversary) conditioned on documented workload changes, M&A activity, or platform migration.
The exit clause defines what happens if the buyer side terminates Azure consumption mid term. The default is forfeiture of unspent commit. The defensible position is partial refund or offsetting against alternative Microsoft products in the event of documented M&A divestiture, regulatory mandate, or Microsoft service discontinuation. Exit clauses are the hardest concessions to land but the most consequential when they are needed.
The commit discount is the line Microsoft will negotiate publicly. The five protective clauses are where the dollar weight actually sits.Practice principle · MACC engagements
MACC discount tiers are negotiated against commit size and term length. The table below summarizes the discount bands we observe across our active engagements. Concession behavior varies by sector, fiscal quarter, and Microsoft account team incentive.
| Annual commit band | Discount range | Marketplace burn | Migration funding |
|---|---|---|---|
| Below $1M | 0 to 5 percent | Limited | None |
| $1M to $5M | 5 to 10 percent | Preferred ISV only | Up to 25 percent of commit |
| $5M to $25M | 10 to 18 percent | Capped at 25 percent | Up to 50 percent of commit |
| $25M to $100M | 15 to 25 percent | Capped at 35 percent | Up to 75 percent of commit |
| Above $100M | 20 to 30 percent | Approaching uncapped | Custom funding band |
Across the 89 Azure engagements in our practice, the dollar value of the structural protections (rollover, true down, marketplace burn, exit) consistently exceeds the dollar value of an additional discount point on the headline tier. This is counterintuitive to most buyer side teams entering an Azure negotiation. The intuition is that the discount is the primary variable. The math is that the discount is applied to consumption that is going to be spent anyway. The protections govern what happens when the commit deviates from plan. Every commit deviates. The question is whether the deviation produces stranded spend or whether it is contractually managed. Our recommendation in every MACC engagement is to negotiate the protections first, accept the standard discount tier for that commit size, and walk away from upper tier discount offers that require forfeiting structural protections. The buyer side teams that follow this pattern consistently produce stronger five year outcomes than the teams that optimize for the headline discount.
Three observations from MACC negotiations across the practice. Each shapes how the buyer side approaches the commit.
Microsoft account teams open the MACC conversation on the discount tier because it is the variable they have the most authority to move. The buyer side teams that follow Microsoft into the discount conversation typically extract one or two extra percentage points off the standard band, which translates to a meaningful but bounded dollar value. The teams that redirect the conversation to the structural protections (rollover, true down, marketplace burn) consistently extract multiples of the discount delta in protection value. The tactical lesson is to acknowledge the discount conversation early, take the standard band for the commit size, and pivot the negotiation hours to the protections.
The Azure Migration and Modernization Program funding tied to MACC enrollment is materially larger than most buyer side teams expect. The funding scales with commit size and is routinely conceded at twenty five to seventy five percent of commit value for migration projects that have documented business cases. The buyer side teams that arrive at the MACC negotiation with a portfolio of documented migration projects (data center exit, SAP on Azure, SQL modernization, OpenAI workloads) consistently extract more funding than the teams that come to the negotiation without a project portfolio in writing.
The MACC burndown eligibility clause defines which Azure consumption counts toward the commit. The default eligibility is restrictive. Each item added to the eligible list (selected marketplace partners, Azure OpenAI, first party SaaS running on Azure) is effectively a free discount on those line items because the spend would otherwise sit outside the commit. The buyer side teams that prepare a list of preferred eligibility expansions and negotiate them as part of the MACC conversation routinely extract three to five percent of additional value at no cost to the headline discount tier.
The MACC value is realized across the entire five year horizon, not at the signature event. The discount tier and the migration funding produce value in year one. The structural protections produce value across years two through five when the Azure consumption pattern deviates from the original commit plan. The buyer side teams that prepare the negotiation around the full five year value horizon consistently produce stronger outcomes than the teams that optimize for year one signature value. The mechanical pattern is to structure the negotiation conversation around three distinct value pillars. Discount and funding in year one. Eligibility expansion across all years. Structural protections in years two through five. Each pillar has its own negotiation lever and its own concession band. The buyer side teams that bundle all three pillars into a single multi clause MACC amendment land the strongest outcomes. The teams that negotiate the discount in isolation produce the weakest outcomes despite often extracting the highest headline discount.
Each lever on the renewal interacts with every other lever. The related notes below cover the adjacent posture work.
Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is on your renewal, and whether we are the right firm for this engagement. Buyer side only. Never affiliated with Microsoft.