Azure MACC True Up and Reconciliation

Azure MACC true up and reconciliation is the machinery that decides how much of your commitment you actually keep. A Microsoft Azure Consumption Commitment is a fixed dollar amount of qualifying Azure consumption over the term, and reconciliation is how Microsoft compares what you consumed against what you promised. Because unused commitment is generally lost rather than refunded, as of June 2026, the timing and the rules of the true up matter as much as the headline number you sign.

How Azure MACC true up and reconciliation works

Reconciliation is the periodic measurement of your qualifying consumption against the committed amount. The two questions that decide your exposure are when the measurement happens and what counts. A MACC measured only at the very end of a multi year term behaves very differently from one measured year by year, because a single annual window forces you to land the number inside twelve months with no help from later quarters.

The true up is the moment any gap becomes real. If your qualifying consumption falls short of the committed amount for the period, the shortfall is generally owed to Microsoft, and there is usually no rollover of the unused portion, as of June 2026. The discount you negotiated does not soften this. A shortfall is paid at the committed value, so an aggressive commitment that looked cheap on the rate can become expensive on the true up.

What counts toward the number is the other half of reconciliation. Qualifying first party Azure consumption clearly applies. Azure Marketplace eligible spend can apply, but the definition is negotiable and can be narrowed. Confirm in writing which services and which Marketplace purchases the reconciliation will recognize, because a narrow definition shrinks your effective coverage and pushes you toward a shortfall.

Measurement windows change everything

Picture two buyers with the same commitment and the same total consumption across three years. One signed an agreement measured annually. The other signed one measured across the full term. The first buyer can forfeit money in a weak year even though the three year total clears the commitment. The second buyer lets strong periods offset weak ones inside one window. Same spend, very different outcome.

If your Azure consumption is seasonal, lumpy, or still ramping, push for a longer measurement window or a term level reconciliation rather than a strict annual cut. Where Microsoft insists on annual measurement, pair it with a ramp so the early year commitment is lower and reachable. The goal is to align the window with how your spend actually arrives, not with how the seller would like to recognize it.

Ask precisely how partial periods, credits, and adjustments flow through the calculation. Migration credits, Azure consumption discounts, and savings instruments can interact with the reconciliation in ways that are not obvious. Get the formula in plain language and model it against your own forecast before you agree.

Shortfall math and how to limit it

A shortfall is the difference between your committed amount and your qualifying consumption for the period, and it is generally payable, as of June 2026. The cleanest protection is to size the commitment conservatively in the first place. We cover sizing in detail in our guide to sizing an Azure MACC to avoid overcommitment. A right sized number rarely triggers a true up at all.

Beyond sizing, negotiate the relief levers. A back loaded ramp reduces early exposure. A longer measurement window lets good quarters rescue bad ones. Carry forward language, where you can win it, lets an underused period offset a later one. Relief for genuine business disruption protects you if demand collapses for reasons outside your control. None of these are standard. You ask for them, and you get them in the contract.

Treat the true up as a forecasting discipline, not a year end surprise. Track qualifying consumption against the commitment every month. If a shortfall is forming, you usually have time to pull eligible spend forward, shift qualifying workloads onto Azure, or apply Marketplace purchases that count, rather than discovering the gap when the true up lands.

Negotiate reconciliation terms before you sign, not after

The reconciliation rules are easiest to change before signature and nearly impossible to change after. Once the Microsoft Customer Agreement is executed, the measurement window, the eligible spend definition, and the shortfall treatment are fixed for the term. This is why a buyer side review belongs in the hour before signing, when every term is still open.

Bring leverage. A credible plan to hold Azure spend flat, slow growth, or move a workload changes how Microsoft responds on measurement and relief. Use quarter end and year end timing, when sales pressure peaks. And separate the people. Your finance team should own the forecast, your cloud team should own the consumption data, and your counsel should own the contract language. The reconciliation terms sit at the intersection of all three.

Above all, get it in writing. An account team that promises a generous read of the true up will not be the team that runs it three years later. If a reconciliation concession matters, it belongs in the agreement, reviewed by your own legal counsel, not in a friendly email.

Worked example: how the window changes the outcome

Consider a buyer with a three year commitment whose Azure consumption is steady overall but dips in the second year during a platform migration. Under an annual measurement window, that second year dip can fall below the committed amount and create a shortfall, even though the buyer more than clears the commitment across the full three years.

Under a term level window, the strong first and third years offset the soft second year inside a single measurement period, and no shortfall arises. Same total spend, same discount, but a very different cash outcome driven entirely by one clause. This is why the measurement window deserves as much attention as the headline number.

The practical move is to model your own forecast under both window options before you sign. If your consumption is steady, the window matters less. If it is seasonal, lumpy, or interrupted by a migration, push hard for the longer window or pair an annual window with a back loaded ramp. The modeling takes an afternoon. The exposure it removes can run to seven figures.

Sources, method, and as of date

The program mechanics and ranges on this page reflect publicly available provider documentation and our buyer side negotiation experience, as of June 2026. AWS, Microsoft, and Google revise their programs frequently, so treat every figure as a point in time reference and confirm the current terms directly with the provider before you act.

This page is commercial negotiation advisory, not legal, tax, or accounting advice. We are independent and buyer side, with no reseller margin and no hyperscaler incentive, and we are paid only by the buyer. For interpretation of any commitment contract or program term, engage your own legal counsel.

Understand the reconciliation math before you commit.

A CONFIDENTIAL COMMITMENT REVIEW BEFORE YOU SIGN