Azure MACC vs CTP: the enterprise spend decision.
MACC is the published Azure consumption commitment — $1M to $50M+ annual spend for a 7–15% tier discount. CTP is the bespoke discount sleeve negotiated for strategic accounts, typically at $10M+ spend, delivering 15–32% off list with custom services and exit terms. This note sets out which wrapper wins at each spend level, and where the shortfall true-up trap sits.
Below $10M annual Azure spend, MACC is the right wrapper — a standard 7–15% tier discount with Marketplace burn-down flexibility. At $10M+ with a strategic-account posture, CTP wins whenever it clears a 15% blended discount, adding bespoke service pricing, services credits and exit terms MACC cannot. The trap in both is the shortfall true-up: over-commit and you pay for spend you never consumed.
01 Key findings
MACC is published; CTP is not. MACC tiers are documented and benchmark reliably from $1M to $50M+ annual commit. CTP is negotiated case by case for strategic accounts — there is no published eligibility floor to anchor against.
The discount gap is real. MACC delivers 7–15% against pay-as-you-go list. CTP customers typically see 15–32% on a defined service portfolio — but only in exchange for a longer, ratcheting commitment.
CTP buys terms, not just price. Beyond deeper discount, CTP arrangements bundle $1M–$5M of services credits and can include termination-for-convenience clauses that MACC omits entirely.
Marketplace changed MACC economics. Since 2024, eligible Azure Marketplace purchases count 100% toward MACC burn-down — third-party software you were buying anyway can now satisfy the commitment and defuse underconsumption risk.
The commitment level is the decisive lever. Size the commit at 85–95% of the 95th-percentile forecast. Over-commit and the shortfall true-up erases the discount; under-commit and you miss the tier entirely.
02 MACC vs CTP scorecard
Relative commercial strength across the dimensions that decide the Azure wrapper. Five dots = strongest; scoring reflects commercial posture at a given spend level, not technical capability.
03 Discount structures
MACC tier discounts are published and scale with annual commitment. Above roughly $50M the arrangement typically transitions to CTP, where the discount table is negotiated per service rather than applied as a single blanket tier.
| MACC annual commitment | Typical tier discount | 3-year minimum commit |
|---|---|---|
| $1M to $2M | 5 to 8 percent | $3M to $6M |
| $2M to $5M | 7 to 10 percent | $6M to $15M |
| $5M to $10M | 9 to 12 percent | $15M to $30M |
| $10M to $25M | 10 to 14 percent | $30M to $75M |
| $25M to $50M | 12 to 15 percent | $75M to $150M |
| $50M+ | 13 to 16 percent, typically transitions to CTP | $150M+ |
CTP customers typically receive 15 to 32 percent off list on a defined portfolio (compute, storage, networking, SQL, Cosmos, AI Foundry, OpenAI), with the per-service discount negotiated rather than tiered.
04 Wrapper profiles
- Published tiers — benchmarks reliably against peers
- $1M entry threshold; broad eligible-service coverage
- Marketplace purchases burn down 100% of commitment
- Discount caps around 15% even at scale
- No partial-year exit; shortfall triggers true-up
- No bespoke service pricing or services credits
- 15–32% off list on a negotiated service portfolio
- $1M–$5M services credits and FastTrack support
- Custom exit and termination-for-convenience terms
- Unpublished — no external benchmark to anchor on
- 3 to 5 year term with upward-ratcheting spend floors
- Underspend triggers a true-up to Microsoft
Both wrappers punish over-commitment. MACC has no partial-year exit — underconsumption at term-end triggers a true-up equal to the unmet commitment, regardless of what you actually used. CTP layers annual spend floors that ratchet upward year over year on top of the same true-up. Size the commit at 85 to 95 percent of the 95th-percentile forecast, and use Marketplace burn-down as the release valve.
05 Marketplace inclusion
Azure Marketplace transactions count 100 percent toward MACC burn-down — the single most consequential 2024 policy change in the Azure commercial frame. The Marketplace product is billed through Azure, the customer pays the vendor through Azure, and the eligible charge satisfies the commitment.
The qualifying catalogue is broad: Databricks, Snowflake, MongoDB Atlas, Confluent Cloud, GitLab Ultimate, JFrog Artifactory, HashiCorp Terraform Cloud, Datadog, New Relic, Palo Alto Prisma, Wiz and Lacework are all available with private-offer pricing.
A customer with $4M actual consumption on a $5M MACC can purchase $1M of Datadog through Marketplace — satisfying the commitment, capturing the negotiated Datadog discount, and avoiding the underconsumption true-up. The play works for any third-party software the customer was going to buy anyway.
06 Exit & true-up
Exit terms are where MACC and CTP diverge most sharply, and where portability leverage pays off.
| Dimension | MACC | CTP |
|---|---|---|
| Term length | EA / MCA-E term, typically 3 years | Bespoke, typically 3 to 5 years |
| Underconsumption | True-up on full unmet commitment | Annual spend-floor true-up, ratchets up |
| Partial-year exit | None; pay the gap regardless | Termination-for-convenience, 6–18 mo notice possible |
| Renewal upside | 1 to 3 percent extra tier if consumption grew | Bespoke; strongest with credible multi-cloud threat |
07 Decision matrix by spend
Match the wrapper to annual Azure spend before opening the negotiation. The MACC-to-CTP crossover sits around $10M, where the bespoke discount first clears the published tier.
| Annual Azure spend | Recommended wrapper | Key consideration |
|---|---|---|
| Under $500K | PAYG + Reservations + Savings Plans | No commitment vehicle available; optimise per-workload only |
| $500K to $1M | PAYG + commitment vehicles, or small EA enrolment | Below typical MACC floor; EA sometimes opens MACC lower |
| $1M to $5M | MACC | Standard tier discount path; CTP unlikely at this scale |
| $5M to $10M | MACC with Marketplace strategy | Burn down MACC via Marketplace; evaluate CTP at upper end |
| $10M to $25M | CTP candidate | Negotiate CTP against MACC fallback; CTP wins at 15%+ discount |
| $25M to $100M | CTP standard | Negotiate bespoke discount table, services credits, exit terms |
| $100M+ | CTP with custom frame | Multi-year custom contract; co-engineering, co-marketing |
08 Our recommendation
You run a predictable $1M to $10M Azure estate and value a published, benchmarkable tier discount. Size the commit at 85–95% of forecast, present a Marketplace burn-down plan to control shortfall risk, and hold CTP in reserve for the upper end.
You commit $10M+ with a multi-year horizon and strategic-account standing, and can model economics net of ratcheting floors. Negotiate the per-service discount table, services credits and explicit exit terms — and keep MACC as the credible fallback that shifts Microsoft's posture.
09 Negotiation levers
Four levers materially move realised cost on either wrapper:
Commitment vs consumption
Microsoft pushes for a higher commit than history supports. Anchor on 85 to 95 percent of the 95th-percentile forecast — over-commitment locks in unused spend, under-commitment misses the tier.
Marketplace integration
Present a clear Marketplace burn-down plan and you can carry a higher commitment tier than direct Azure consumption warrants, while controlling underconsumption risk.
CTP fallback modelling
Approaching $10M, model CTP in parallel with the MACC tier. The threat of accepting MACC instead of CTP shifts Microsoft's commercial posture during the negotiation.
True-up & exit terms
Standard exit terms favour Microsoft. Credible workload portability earns explicit exit clauses, transition support, and partial-credit recovery on remaining commitment.
Move to the right Azure wrapper
Our Cloud & FinOps practice identifies the MACC-to-CTP threshold and structures the migration — typically 5 to 12 percent of total Azure spend.
The Licensing Edge
Weekly cloud and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.