Azure Commit-to-Consume vs MACC: How to Negotiate Your Drawdown

What Is Azure MACC and How Does Commit to Consume Work

Microsoft Azure Consumption Commitment (MACC) is a contractual agreement where your organisation commits to consuming a fixed dollar amount of Azure services over a defined period, typically one to three years. In return, Microsoft offers discounts, credits, or other commercial concessions. The newer commit-to-consume (CtC) model operates similarly but with more flexible terms around which services count toward drawdown.

The fundamental challenge is that Azure cost optimisation becomes significantly harder once you have signed a MACC. You have committed to spend whether you consume or not. Microsoft structures these agreements to lock in revenue, not to give you flexibility. Understanding the difference between MACC and CtC structures is essential before you sign anything.

MACC agreements typically apply to first-party Azure consumption (compute, storage, networking) and an expanding list of third-party Marketplace purchases. Microsoft has steadily expanded Marketplace eligibility to make MACC commitments easier to fulfil, which sounds helpful until you realise it also reduces your incentive to negotiate lower unit prices. If you are going to hit your commitment anyway through Marketplace purchases you would have made regardless, the discount you received for committing is worth less than it appears.

MACC vs CtC: The Key Structural Differences

Azure MACC and commit-to-consume are often used interchangeably, but there are important distinctions. A traditional MACC is a straightforward spend commitment: you agree to consume a specific dollar amount over the term. A CtC arrangement can include more nuanced terms around acceleration, true-up mechanisms, and service-specific consumption floors.

Under a MACC, if you underconsume, Microsoft may require a true-up payment at the end of the term for the shortfall. This is the key risk. We have seen enterprises commit to $10M over three years, only to realise 18 months in that their actual consumption trajectory puts them at $7M. The $3M gap becomes a painful budget conversation. Before signing, run your Azure reserved instances and savings plans analysis to understand your real consumption baseline.

The CtC model sometimes offers a "consumption ramp" where the commitment increases each year, giving you time to grow into the spend. This can be valuable for organisations migrating workloads to Azure over time. However, Microsoft will typically front-load the discount value, meaning you get less benefit in later years when your spend is higher. The leverage dynamic shifts once you are 18 months into a three-year CtC and have already consumed the best discounts.

Which Services Count Toward MACC Drawdown

Not everything on your Azure bill counts toward MACC drawdown, and the rules have changed multiple times. As of 2026, eligible consumption generally includes first-party Azure services (compute, storage, databases, AI services, networking), Azure Marketplace purchases from ISVs that have opted into MACC eligibility, and Microsoft 365 and Copilot consumption in some enterprise agreements.

What typically does not count: support contracts, training, consulting services, and some legacy on-premises licence purchases. If your Microsoft account team tells you "everything counts," get it in writing with specific SKU-level detail. We have seen post-signature disputes where enterprise customers assumed certain spend would count toward drawdown, only to discover it did not.

How to Negotiate a Better MACC Agreement

The negotiation starts well before you engage your Microsoft account team. You need a clear picture of your current Azure consumption, projected growth, and alternative cloud strategy. Without this, you are negotiating blind and Microsoft knows it.

First, establish your baseline consumption with at least 12 months of historical data. If your Azure spend has been $300K per month, a $15M three-year MACC implies 38 percent growth, which may or may not be realistic. Microsoft will push you to commit higher because their compensation structure rewards larger commitments. Your job is to commit to what you will actually consume, plus a modest buffer, not what Microsoft wants you to consume.

Second, negotiate the discount structure. Microsoft typically offers a percentage discount on list prices in exchange for the commitment. Push for the discount to apply retroactively to consumption from the start of the term, not just after you hit certain milestones. Also negotiate for the discount to apply to Reserved Instances and Savings Plans purchases, not just pay-as-you-go consumption.

Protecting Against Underconsumption Risk

The biggest financial risk in any MACC is underconsumption. If your cloud migration stalls, if a business unit pulls workloads back on-premises, or if your FinOps governance team does its job too well and reduces waste, you could end up below your commitment threshold.

Negotiate these protections before signing. Request a consumption true-up that allows you to accelerate Marketplace purchases in the final six months of the term to close any gap. Negotiate for the ability to apply licence purchases (such as Microsoft 365 or Dynamics 365) toward the commitment if you fall short on infrastructure consumption. Push for a "carry forward" clause that rolls unused commitment into a renewal term rather than requiring a lump-sum payment.

Some enterprises have successfully negotiated "soft floors" where the true-up payment for underconsumption is prorated rather than binary. Instead of paying the full shortfall, you might pay 50 percent of the delta between actual consumption and the commitment. This requires negotiation leverage, but it is achievable, especially for larger commitments.

MACC Renewal Strategy: What Changes at Year Three

The renewal is where most enterprises either lock in better terms or get trapped into a worse deal. Microsoft's renewal playbook is predictable: they will point to your consumption growth as evidence that you should commit to an even larger MACC, and they will use the threat of losing your existing discount as leverage.

Start your renewal planning at least nine months before the current term expires. Conduct a full Azure cost optimisation review to understand which consumption is essential and which is waste. Evaluate whether a MACC renewal is even the right structure, or whether a mix of Savings Plans and Reserved Instances without a MACC commitment would give you better economics with more flexibility.

Consider running a competitive evaluation with AWS or Google Cloud before your renewal. Even if you have no intention of migrating, a credible alternative creates negotiation leverage that a MACC renewal discussion alone does not. Microsoft's pricing flexibility increases dramatically when they believe there is a real risk of workload migration to a competitor.

Common MACC Negotiation Mistakes

The most common mistake is over-commitment. Enterprises commit to more than they will consume because Microsoft's discount structure incentivises it, and because internal stakeholders project aggressive cloud adoption that does not materialise. Always commit to 80 to 90 percent of your realistic consumption forecast, not 100 percent or more.

The second mistake is ignoring the EA true-up implications. Your MACC and your Enterprise Agreement are separate but related contracts. Changes to your EA (adding or removing licences, changing subscription levels) can affect which Azure consumption counts toward your MACC. Make sure your licensing team and your cloud team are coordinating.

The third mistake is not reading the service-level consumption rules. Microsoft can change which services are MACC-eligible during the term. While they typically grandfather existing eligibility, new services may or may not count. Get explicit contractual language that protects your drawdown eligibility for the full term.

When to Walk Away from a MACC

Not every organisation needs a MACC. If your Azure consumption is below $1M per year, the discounts available through a MACC are unlikely to justify the commitment risk. You are better off using Savings Plans and Reserved Instances for predictable workloads and paying list prices for variable consumption.

Similarly, if your organisation is in a period of significant change (mergers, divestitures, strategic pivots), a multi-year consumption commitment is risky. The flexibility cost of a MACC during uncertain times often exceeds the discount benefit. Consider a shorter term (12 months) or a smaller commitment with the ability to increase mid-term if consumption warrants it.

If you need help evaluating whether a MACC is the right structure for your Azure strategy, or if you want independent analysis of a proposed MACC agreement before you sign, talk to our Microsoft advisory team. We review dozens of MACC agreements every quarter and can benchmark your proposed terms against what other enterprises are getting.