Spoke / Azure MACC
Microsoft Azure MACC sizing guide.
Microsoft will size the MACC for you. The number will be too high or too low. This guide sets out how to size it from the buyer side with a three percent variance target.
Microsoft will size the MACC for you. The number will be too high or too low. This guide sets out how to size it from the buyer side with a three percent variance target.
A bottom up MACC sizing model with a three percent variance target. The same methodology we run in paid engagements, written for buyers to use directly.
The MACC is a forward commitment against Azure consumption. The number on the contract becomes a fixed cost. Variance against actual burn becomes margin one way or the other.
Microsoft will model the commit using top down logic, an annual growth multiplier, and a discount tier reference. The number will rarely be the right number.
This guide sets out the bottom up methodology. Twelve months of baseline data, three growth tracks, a counting confirmation, three scenarios, and a variance target.
Start with twelve months of clean consumption data from Azure Cost Management.
Azure Cost Management at the subscription level. Strip out one off events, decommissioned workloads, and any spend that will not continue into the new term.
Five categories. Compute, storage, networking, PaaS, and AI. Marketplace and reserved capacity are special cases tracked separately.
Convert all spend to monthly run rate. Smooth across the last three months for the most recent baseline. This is the launchpad for the growth model.
Three growth tracks. Each has a different curve and a different confidence band.
The natural growth in the existing workloads. Five to twelve percent annual is normal for mature estates. Modeled as a straight line.
New workloads landing inside the term. Modeled at the project level with go live dates and ramp curves. Discount the wishlist heavily.
Azure OpenAI, custom models, and Copilot platform usage. The most volatile track in 2026. Three scenarios from flat to four times current.
Variance bands and the buyer side response.
| Variance vs Commit | Posture | Action | Microsoft Conversation |
|---|---|---|---|
| +/- 3% | On plan | Track quarterly | None required |
| +/- 5% | Drift | Review forecast | Internal only |
| +/- 10% | Material drift | Update model | Information call |
| +/- 15% | Risk | Build re sign case | Formal review |
| >= +20% | Overrun | Trigger re negotiation | Open with leverage file |
Not every Azure dollar counts toward MACC. Confirm the rules before sizing.
All first party Azure services count toward MACC. Compute, storage, PaaS, AI.
Eligible third party marketplace spend counts up to a percentage cap defined in the MACC. The cap and the eligibility list are negotiable.
Azure spend billed through a CSP partner is counted differently. Confirm with the agreement and the partner.
Take the baseline, apply the growth tracks, and stress test across three scenarios.
Conservative, base, and stretched. Each produces a year by year commit number and a total term commit.
A single Excel sheet with one row per year, one column per category, and one summary line per scenario. Variance against baseline is the headline metric.
Flex growth rates by category. AI is the highest leverage variable in 2026. Compute and storage flex less.
A MACC is a forecast contract. Treat the sizing like a forecast, not like a negotiation, and the negotiation almost solves itself.
Run the model against four shocks before signing.
Cut project growth to zero. Cut AI growth to flat. Hold organic. Does the conservative case still land above the commit?
Remove the largest workload from the model. Many MACCs include re sign rights triggered by divestiture above a threshold.
Move twenty percent of compute to a competitor cloud or back on premises. Hypothetical, but useful as a downside guard.
Apply the four times AI track. Does the stretched case clear the commit by year three?
The target is plus or minus three percent across the term.
Plus three percent or minus three percent. Inside that band the discount is captured and overrun is contained.
Quarterly burn review. Plus or minus five percent triggers a review. Plus or minus ten percent triggers a Microsoft conversation.
Sustained plus or minus fifteen percent over two quarters triggers a mid term re negotiation conversation.
It is the minimum. Twenty four months is better. Less than twelve and variance assumptions widen materially.
Model them inside the project growth track with explicit go live dates and ramp curves. Discount the wishlist.
Use the three AI scenarios. Flat, double, and four times. Size against the base case and protect with mid term re sign rights.
Yes, in most engagements. Conservative leaves discount on the table. Stretched creates overrun risk that re negotiation cannot fully fix.
Yes when the model is well built. The bottom up evidence carries weight, and the alternative is Microsoft top down sizing the customer is forced to defend.
Quarterly during the first year. Semi annually thereafter unless the burn rate drifts past the five percent band.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Sizing a MACC is not a negotiation move. It is a forecasting move. Get the forecast right and the negotiation almost runs itself.
500+ enterprise clients. 11 vendor practices. Gartner recognized. One conversation can change what you pay for the next three years.
Monthly briefings on Microsoft EA, MACC, Copilot, and the buyer side benchmarks across the Microsoft estate.
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.
