Run the methodology with a senior advisor.
A senior Admodum advisor will walk the methodology through with your CIO, CFO, sourcing or FinOps team on a private call. Engagements run as fixed fee, contingency or annual retainer.
Twenty-two pages on the eligible-service catalogue, the three-year ramp curve, Marketplace pull-through, the true-up window protocol, the unspent-commitment problem and the renewal posture at end of term.
The Microsoft Azure Consumption Commitment is the principal commercial container in which Microsoft sells Azure to enterprise customers. A MACC is a multi-year (typically three-year) underwritten commitment to a defined quantum of eligible Azure consumption, in exchange for a tiered discount taper against the Azure on-demand list.
The publisher's commercial logic behind the MACC is straightforward. Microsoft prefers the commitment over pay-as-you-go because the commitment anchors a multi-year revenue position, supports the sales motion inside the Cloud Solution Provider channel and qualifies the customer for incentive programmes (Marketplace pull-through, AI Co-pilot bundles, FastTrack engagements) that depend on a committed Azure footprint.
The buyer's commercial logic for the MACC is the discount taper. The taper ranges from a low single-digit percentage at the smallest commits to a low double-digit percentage at the largest commits. The taper is set against the on-demand list, not against the buyer's previously negotiated rate, with the consequence that the headline saving inside the MACC contract is not always the saving on the buyer's actual consumption.
The Admodum reading of the MACC posture is that the commitment is the operating envelope inside which Azure is consumed for the term, and the discount is the price the buyer pays to fix the envelope. Sizing the envelope correctly is the central commercial work of the MACC. The remaining sections of this paper set out the methodology Admodum applies to that sizing across the eighteen-month preparation cycle.
Not every line on the Azure bill counts toward MACC drawdown. The eligible-service catalogue is a moving boundary, defined by Microsoft, that determines which consumption reduces the commit and which consumption falls outside it.
The eligible categories include first-party Azure PaaS, IaaS and most first-party SaaS services, with the exception of a small set of third-party-billed services and a small set of reserved-capacity products that are billed outside the MACC. The list is published by Microsoft and revised periodically, with the consequence that the buyer cannot rely on a snapshot taken at signature to remain accurate across the term.
A subset of Microsoft commercial Marketplace transactions count toward MACC drawdown under the published Marketplace pull-through programme. The eligibility list is curated by Microsoft and is narrower than the full Marketplace catalogue. The buyer's Marketplace plan must reconcile against the eligibility list at the time of transaction; an ISV that is eligible at signature is not necessarily eligible at the moment a private offer is executed.
Standard exclusions include Marketplace SaaS transactions that fall outside the pull-through programme, third-party reserved capacity, certain hardware components inside Azure Stack and Azure VMware Solution, and a range of telephony and communication usage charges that route through different commercial constructs. The buyer's MACC sizing must net the excluded lines out of the historical consumption baseline before the ramp is designed.
The MACC ramp curve is the operational architecture of the commitment. The buyer who designs it from year one upward is anchoring the negotiation on current consumption. The buyer who designs it from year three backward is anchoring it on the migration plan. The two postures produce different commits.
The Admodum ramp design protocol starts at the year-three peak. The year-three peak is the highest credible MACC-eligible consumption position the buyer can defend, expressed in current pricing and against the published eligible-service catalogue. The position is calibrated against the application portfolio decommission record, the data-centre exit timeline, the AI workload plan and the FinOps consumption telemetry from the trailing twelve months.
The year-two step is sized so the curve passes through the application portfolio's migration milestones. The year-one floor is sized so the buyer does not over-commit on entry. The taper across the three years is then negotiated against the published discount table and the buyer's broader Microsoft commercial relationship.
Most MACC ramps assume material new consumption inside the term. The most common source of new consumption is workload migration off on-premises data centres, off VMware estates and off third-party clouds. The migration assumption must be modelled in detail, with named workloads, target landing zones, expected unit costs and a calibration band wide enough to absorb migration slippage.
Where the migration assumption is thinly evidenced (no named workloads, no architectural commitment, no procurement budget) the buyer's posture is a conservative commit at the year-one floor with an explicit option to true up to a higher commit at anniversary. Microsoft will accept this posture where the alternative is no MACC at all.
The Microsoft commercial Marketplace, since the introduction of MACC pull-through, has become a meaningful component of MACC drawdown for buyers who consume significant ISV spend in categories where eligible ISVs operate.
The pull-through mechanism converts eligible Marketplace spend into MACC drawdown at one hundred percent of the transaction value. The buyer's procurement budget that previously flowed to an ISV under a direct contract flows instead through the Microsoft Marketplace under a private-offer transactable contract, with the consequence that the eligible Marketplace spend reduces the MACC commit pound-for-pound.
The pull-through is not free leverage. The ISV's pricing inside a Marketplace private offer is sometimes different from the ISV's pricing in a direct contract; the contract terms inside the Marketplace transactable framework are sometimes different from the ISV's standard MSA; and the buyer's commercial relationship with the ISV is sometimes weakened by the routing of the transaction through Microsoft. The pull-through is leverage when each of those three points is verified.
A Marketplace private offer is a price the ISV has agreed with the buyer that is exposed only inside the Microsoft Marketplace. The transactable contract is the legal instrument that records the transaction. The MACC drawdown is recognised at the moment the transactable contract is executed inside the Marketplace, which is also the moment the ISV invoices Microsoft and Microsoft invoices the buyer against the MACC.
The MACC contract anchors the commitment at the agreed annual amount, with anniversary reconciliation at the end of each contract year. Consumption above the annual amount is invoiced at the negotiated taper rate for the duration of the term; consumption below the annual amount is held against the future periods.
The over-consumption rate inside a well-negotiated MACC is the same taper rate as the committed-consumption rate. Where the buyer has accepted a step-up in the taper for over-consumption (a posture Microsoft will sometimes propose) the implicit cost of consumption above the commit can rise materially. The buyer's MACC contract should be examined at this point in the negotiation and the step-up should usually be resisted.
Most MACCs include limited roll-forward of unused commit between contract years. The mechanic ranges from a hard cliff (no roll-forward) to a soft roll-forward (the surplus is held against the following year) to a strict reconciliation (the shortfall is invoiced at the end of the term, regardless of whether the prior year was over-committed). The Admodum posture is to negotiate a soft roll-forward inside the term with a defined treatment of any residual shortfall at end of term.
The unspent commitment is the buyer's most material MACC risk. Most MACCs are signed at the forecast number. Most forecasts are optimistic. The probability that the buyer will arrive at end of term with the commitment fully drawn is below one hundred percent and, in many engagements Admodum closes, below seventy-five percent.
When the buyer cannot consume the commit, four options exist. The first is to accelerate Marketplace pull-through inside the eligibility list, converting line-of-business ISV spend into MACC drawdown. The second is to advance AI consumption (Azure OpenAI, AI Foundry) where the AI roadmap supports the spend. The third is to negotiate carry-forward of the residual against a new MACC at renewal, with the residual treated as a credit on the new commit. The fourth, the worst, is to pay the residual as a shortfall invoice at end of term.
The signal that the commitment will go unspent typically appears in Quarter Two of the contract year. The Admodum protocol monitors the consumption-to-commit ratio quarterly across the term, and where the ratio at Quarter Two indicates a year-end shortfall, the four options are evaluated at Quarter Three with a published runway that lands the spend inside the commit. The forecast error is corrected operationally rather than financially.
The MACC renewal posture is the most consequential negotiation moment in the Microsoft commercial relationship outside of the EA renewal itself. The choice of posture at renewal sets the commercial envelope for the next three years.
Three principal postures exist. The first is renewal at a higher commit, with a tighter taper, where the buyer's Azure trajectory is on a clear upward path and the migration plan supports a larger ramp. The second is renewal at a flat or stepped-down commit, with the same or a similar taper, where the Azure trajectory has plateaued and the next term is a containment exercise. The third is non-renewal, with the buyer dropping to pay-as-you-go pricing, where the Azure trajectory has begun to decline or where the buyer is considering a multi-cloud rebalancing.
The Admodum posture protocol benchmarks the renewal terms against the Microsoft commercial position the buyer holds, the FinOps consumption telemetry across the closing term, the migration plan for the next three years and the AI workload roadmap. The protocol produces a recommended renewal posture and the procurement playbook to execute it.
The Azure MACC paper sits inside a four-paper Microsoft reading list. The companion papers extend the methodology to adjacent commercial mechanics:
The methodology in this paper is the methodology Admodum has applied across more than thirty MACC commitments inside the firm's engagement history. Each engagement is structured as fixed fee, contingency / gainshare or annual retainer, depending on the buyer's posture at the commitment window.
A senior Admodum advisor will walk the methodology through with your CIO, CFO, sourcing or FinOps team on a private call. Engagements run as fixed fee, contingency or annual retainer.