Cloud commitments · June 2026

PPA vs MACC: how committed cloud spend actually gets drawn down.

If your company signed a multi-year cloud agreement, you’re sitting on committed spend. Third-party software can draw it down, and the fine print decides whether it counts.

4 min read

An AWS Private Pricing Agreement (PPA) and a Microsoft Azure Consumption Commitment (MACC) work the same way at a high level. You commit to a dollar amount of cloud consumption over a term and get better pricing in return. The commitment is real, though: spend left unconsumed at the end of the term is money left on the table, and renegotiating from under-consumption is a weak position.

AWS

Private Pricing Agreement

A committed-spend agreement with AWS. Software procured through AWS Marketplace can count toward it, with treatment set by the terms of your agreement.

Microsoft Azure

Azure Consumption Commitment

A committed-consumption agreement with Microsoft. MACC-eligible offers on Azure Marketplace count toward it, and eligibility is set listing by listing.

Third-party software counts

Your software renewals can draw it down

Most teams underestimate that the commitment doesn’t have to be consumed by infrastructure alone. Software procured through AWS Marketplace can count toward a PPA, and MACC-eligible offers on Azure Marketplace count toward a MACC. In many agreements the credit applies at the full value of the software contract, though the exact treatment depends on what you negotiated.

The security platform, observability suite and backup contract you were renewing anyway can do a second job: drawing down a commitment you already owe.

The mechanics

How a renewal actually routes

The vendor publishes a private offer on the marketplace with your negotiated pricing and terms. Your team accepts it inside your existing cloud account, the charge lands on your cloud bill, and the eligible value is applied against your commitment. There’s no new vendor onboarding or separate payment terms, and security and legal review largely rides on paper your team has already accepted.

How a marketplace renewal draws down committed spend. Diagram by Ghost.

On AWS, a reseller takes part through a Channel Partner Private Offer (CPPO), which lets an authorized partner extend the vendor’s product with its own pricing. On Azure, partners use multiparty private offers. Either way the experience is the same for you: the purchase lands on the cloud bill and draws down the commitment.

Eligibility

The fine print that matters

Not every offer counts. On Azure only offers marked Azure benefit eligible apply, at their full pretax amount, and the purchase has to go through the Azure portal on a subscription tied to your agreement. On AWS, treatment can vary with the terms of your agreement. Before routing a large renewal, confirm three things:

  • The product is listed on the marketplace whose commitment you’re drawing down.
  • The listing qualifies under your specific agreement.
  • The private offer is structured so the full value applies.

This is the detail a marketplace-native partner should handle for you.

What changes

Why this changes who you work with

Legacy resellers were built around purchase orders and distribution tiers. The marketplace model removes that machinery, along with the cost and delay that came with it. If your renewals can draw down spend you’ve already committed, every renewal deserves a check on whether it can route through the marketplace, and more of them can every year.

Where Ghost sits

We map what routes where

Ghost works through AWS Marketplace, Azure Marketplace and Carahsoft for the public sector. Send us your renewal calendar and committed-spend position, and we’ll show which renewals can route through which marketplace, confirm eligibility listing by listing and structure the private offers.

See what your commitments could be doing. Talk to Ghost.

Send us your renewal calendar and committed-spend position, and we’ll map what routes where.

Talk to Ghost info@ghosttech.co