Does Marketplace Spend Count Toward a Cloud Commit?

Marketplace spend counts toward a cloud commit only when that commit's rules say the listing is eligible, and only at the rate those rules name. The three hyperscalers do not use one rate.

Azure#

The MACC page states the rule in one line: eligible Azure Marketplace offerings count at 100 percent toward a Microsoft Azure Consumption Commitment. A buyer can retire commit with third-party software and buy no additional first-party Azure to do it. The same page puts MACC discounts in a 9 to 18 percent band below pay-as-you-go, on commits that start around $1 million a year.

That 100 percent is eligibility, and eligibility is a catalog. A product that is not in the Azure consumption set does not retire the commit, whatever the order form calls it.

AWS#

The AWS EDP page splits the burn. AWS-managed Marketplace listings, where AWS bills and contracts the seller, burn at 100 percent. Self-serve listings burn at 50 percent under the rules that page dates to 2024. The same page puts EDP discounts in a 5 to 15 percent band below pay-as-you-go.

The listing type is the sourcing decision. A private offer on a managed listing and a private offer on a self-serve listing do not retire the same fraction of the commit. The AWS private offer page is the offer mechanic. Procurement models for managed cross-cloud databases applies it to MongoDB Atlas, Snowflake, Databricks, and Confluent Cloud.

Google Cloud#

A committed use discount is a compute commit. The CUD page separates spend-based CUDs (a flat 25 to 28 percent on flexible compute) from resource-based CUDs (higher, on named machine types, up to 70 percent on the longest prepaid term it describes). It also names a broader marketplace committed-spend program that opens marketplace burn-down, and it does not publish one burn percent the way the AWS and Azure pages do. Treat a CUD and a marketplace purchase as the same commit only after that page says they stack.

Price and burn are different#

A private offer can discount the software and also choose a listing type that burns a commit. Those are two concessions. Score them separately, then read commitment structures and the cloud infrastructure benchmark for the commit itself.