A cloud commitment agreement is a contract in which an organization commits to spend a set amount with a public cloud provider over a fixed term, typically one to several years. The commitment covers eligible spend and may be paired with separately negotiated terms, such as discounts off list prices, credits, support or migration funding. A spend commitment does not by itself guarantee discounted pricing: what the buyer gets in return depends on what is negotiated. It is an agreement that sits on top of the provider’s standard terms. Large providers run their own branded programmes, such as the AWS Enterprise Discount Program (EDP) and the Microsoft Azure Consumption Commitment (MACC), and names and structures differ from one provider to the next.
At a glance
- You commit to eligible spend over a term; discounts, credits or funding are negotiated alongside it, not automatic.
- Falling short usually means a shortfall payment or losing the unused commitment, depending on the terms.
- What counts toward the commitment (services, marketplace purchases, support) is set by the agreement.
- It covers overall spend, unlike resource-level cloud commitment discounts.
- Accurate forecasting, usually from a FinOps practice, is what makes the commitment safe.
What problem it solves
Pay-as-you-go cloud pricing is flexible but rarely the lowest available price for a large, steady customer. A commitment agreement gives the provider predictable revenue, which gives the buyer leverage to negotiate a lower effective rate across the provider’s services. It can also be a vehicle for terms that are otherwise hard to get, such as migration credits, support arrangements, egress rates or marketplace flexibility.
For finance, it turns an unpredictable usage bill into a known minimum, which helps budgeting. The risk is that the commitment is fixed while usage may not be.
How it works
Sizing. The buyer and provider agree a total commitment, often expressed per year with a minimum each year, or as a total over the term. Larger and longer commitments typically give more room to negotiate pricing. Some agreements ramp, starting lower and rising each year.
Pricing and benefits. Any negotiated discount is set out in the agreement or a related pricing addendum; where one applies, it may cover many services, with some excluded or carrying different rates. Some commitment programmes carry no discount of their own. Agreements may also include credits for migration or proof-of-concept work, support terms, or training.
Eligible spend. The agreement defines what counts: usually most of the provider’s own services; sometimes eligible third-party marketplace purchases, often with a cap; and in some cases purchases made through a reseller. Taxes and some charges may not count.
Measurement and shortfall. Spend is tracked against the commitment. If you fall short, the agreement may require a payment for the difference, let the unused amount expire, or allow it to roll into an extension. Many buyers negotiate the shortfall terms as hard as the discount.
Interaction with other discounts. Resource-level commitment discounts may interact with contract pricing, and their purchases or usage may or may not count toward the committed spend. Verify the order in which discounts apply, what is excluded, and exactly how each kind of spend retires the commitment.
For buyers with spend across several clouds, or weighing whether to concentrate spend to reach a better tier, our public cloud solution page covers how commitments fit into provider selection.
When it matters for buyers
- Cloud spend becomes large and steady. Pay-as-you-go pricing usually leaves money on the table at scale.
- At renewal. Expiring agreements are the best moment to revisit size, term, discount, egress and exit terms.
- During a large migration. Providers often offer credits or funding tied to a commitment.
- A new CFO or budget review. Finance will want to know what is committed and how likely you are to meet it.
- Consolidating providers. Concentrating spend can reach a better tier, but increases dependence on one hyperscaler.
Questions to ask vendors
- Does the commitment come with any discount, to which services does it apply, and are any excluded?
- In what order do contract discounts and resource-level commitment discounts apply?
- What counts toward the commitment: marketplace purchases, support, reseller purchases? Is there a cap?
- What happens if we fall short in a year or over the term? Can a shortfall roll forward?
- Can the commitment ramp over the term, and can it be adjusted after a divestiture or downturn?
- What credits, support or migration funding come with it?
- Can egress pricing, data transfer and exit terms be included?
- How does the agreement interact with our existing commitment discounts?
How it differs from a minimum annual commitment
A minimum annual commitment is the general contract concept of promising to spend at least a set amount each year, common in telecom and many service contracts. A cloud commitment agreement is a specific kind of committed-spend contract offered by cloud providers, with its own rules for eligible and marketplace spend, often paired with negotiated pricing or credits, and often governed by its own addendum to the provider’s terms or a master services agreement (MSA). The core risk is the same: if usage falls, the commitment does not.