Commercial Structure Overview
AWS, Microsoft Azure, and Google Cloud all offer enterprise commitment agreements — but the structures differ in ways that materially affect discount levels, financial risk, and negotiating flexibility. Understanding these structural differences is not merely academic: a buyer who mistakes Azure MACC mechanics for AWS EDP mechanics, or who doesn't understand how Google Cloud's CUD interacts with private pricing agreements, will make systematically worse commercial decisions.
This comparison is written by practitioners who have been on the selling side of all three platforms and now negotiate exclusively on behalf of enterprise buyers. The commercial intelligence in this guide reflects the current state of enterprise cloud commercial frameworks as of early 2026. See our complete cloud contract guide for the broader strategic framework.
AWS Enterprise Discount Program (EDP): Commercial Profile
AWS's enterprise commercial vehicle is the Enterprise Discount Program — a committed spend agreement with a single, clean structure: commit to a minimum annual spend, receive a discount percentage on qualifying consumption. The EDP is clean to understand but complex to negotiate well.
AWS Structural Strengths
The AWS EDP's simplicity is a genuine commercial advantage for buyers. The discount is applied as a flat percentage across a broad range of services, making it relatively easy to model the financial impact of the commitment. AWS's Reserved Instance and Savings Plan programmes can be stacked on top of the EDP discount in some configurations, creating additive savings for compute-intensive workloads.
AWS's service breadth is also the largest of the three hyperscalers. An EDP discount covering AWS's 200+ service catalogue provides more opportunity to generate qualified consumption against the commitment than Azure MACC or GCP CUC — reducing shortfall risk for organisations with diverse cloud workloads.
AWS Structural Weaknesses
The EDP's simplicity becomes a weakness in situations requiring commercial flexibility. AWS has historically been the least flexible of the three hyperscalers on mid-term ramp adjustments and shortfall provisions. Microsoft and Google Cloud have both introduced more buyer-friendly commitment adjustment mechanisms in recent years; AWS's EDP remains comparatively rigid once signed.
AWS also embeds less flexibility in service exclusions — marketplace purchases, support, and professional services are routinely excluded from both the discount and the commitment calculation, meaning organisations with high Marketplace spend need to model the effective commitment carefully. See our detailed AWS EDP negotiation guide for the full picture.
Microsoft Azure MACC and Enterprise Agreement: Commercial Profile
Microsoft's enterprise cloud commercial structure is the most complex of the three hyperscalers — because Azure is not a standalone product. It sits within a Microsoft commercial ecosystem that includes Microsoft 365, Dynamics 365, Power Platform, GitHub, Security products, and Copilot. Azure spend is governed either by a standalone Azure Consumption Commitment (MACC) or — more commonly for large enterprises — by an Azure commitment embedded within a Microsoft Enterprise Agreement (EA).
The Microsoft Commercial Ecosystem Advantage
Microsoft's bundled commercial ecosystem is its most powerful leverage mechanism — and its most significant buyer risk. Organisations that consolidate Microsoft 365, Dynamics, Power Platform, and Azure spend within a single Microsoft EA can achieve total commercial discounts of 20–35%+ on the overall Microsoft relationship. The discount is applied across the portfolio rather than on Azure in isolation.
This bundling creates genuine commercial value for buyers with large Microsoft software estates. It also creates significant commercial risk: Microsoft uses the breadth of the relationship to increase stickiness, introduce new products at subsidised rates, and conduct renewal negotiations across the entire portfolio simultaneously — making it difficult to isolate Azure pricing from the broader Microsoft commercial dynamic.
Azure MACC Mechanics
A standalone Azure MACC requires the buyer to commit to a minimum Azure consumption amount over the commitment term. MACC commitments count as Azure spend for the purposes of Microsoft's internal commercial metrics and unlock Azure-specific incentives and credits. For organisations whose primary cloud is Azure and whose Microsoft relationship is primarily software-centric, a MACC can provide better Azure-specific pricing than embedding Azure in a broader EA negotiation.
The MACC structure is generally more flexible than the AWS EDP on mid-term review rights. Microsoft has introduced explicit ramp adjustment mechanisms for large MACC commitments, allowing buyers to reduce minimum consumption targets at defined review points if consumption falls below agreed thresholds.
Azure Structural Weaknesses
The complexity of the Microsoft commercial ecosystem cuts both ways. While it enables total relationship discounts, it makes Azure pricing opaque — it is genuinely difficult to determine the true unit cost of Azure services when discounts are embedded in a Microsoft EA alongside M365 and Dynamics. Buyers negotiating Azure in isolation (without the broader Microsoft relationship) often find that Azure's standalone pricing is less competitive than AWS or GCP for equivalent compute workloads.
Google Cloud Committed Use and Private Agreements: Commercial Profile
Google Cloud's enterprise commercial structure has two tiers: self-service Committed Use Discounts (CUDs), available to any customer for specific resource types; and Private Agreements — custom commercial arrangements for large enterprise customers that function similarly to AWS EDP but with different structural characteristics.
CUD Structure
Google Cloud's self-service CUDs provide 20% discount for 1-year commitments and 57% discount for 3-year commitments on specific compute resource types (vCPUs and memory). These are the most generous automated self-service discounts in the hyperscaler market — significantly better than AWS Reserved Instances or Azure Reserved VM Instances for equivalent commitment terms. CUDs are not negotiated; they are simply selected by the buyer.
The limitation of CUDs is their resource-specificity. Unlike AWS Savings Plans (which are flexible across instance types) or Azure Reserved VM Instances (which cover a broad VM family), Google CUDs are committed to specific resource configurations. For organisations with predictable, stable compute workloads, CUDs are extremely cost-effective. For organisations with variable or evolving workloads, the rigidity creates utilisation risk.
Google Cloud Private Agreements
Above the CUD tier, Google Cloud offers private pricing agreements for large enterprise customers — negotiated commercial structures that provide broader discounts across the Google Cloud service catalogue, similar in concept to an AWS EDP. Google Cloud's private agreement discounts are typically the most aggressive of the three hyperscalers — Google has historically used commercial pricing as a competitive weapon to displace AWS and Azure workloads.
In competitive situations where Google Cloud is displacing workloads from another provider, private agreement discounts of 25–40% are achievable. Google Cloud's commercial team has explicit internal authorisation to price aggressively for strategic wins. The quid pro quo is typically a multi-year commitment and a defined migration plan with measurable milestones. See our Google Cloud CUD optimization guide for detailed structuring guidance.
Google Cloud Structural Weaknesses
Google Cloud's commercial strength is discounted by two structural realities. First, its enterprise service catalogue — while expanding rapidly — remains narrower than AWS's for many specialised workload types. Second, Google Cloud's enterprise commercial organisation is smaller and less mature than AWS's or Microsoft's, meaning deal approval processes can be slower and less predictable.
Side-by-Side Comparison Table
| Dimension | AWS EDP | Azure MACC / EA | GCP Private Agreement |
|---|---|---|---|
| Commitment structure | Annual minimum spend commitment | Azure consumption commitment or EA-embedded | Annual or multi-year spend commitment |
| Discount range (enterprise) | 10–25%+ (30%+ for strategic deals) | 10–30%+ (including M365/Dynamics bundle) | 15–40%+ (most aggressive for competitive wins) |
| Service coverage breadth | Broadest (200+ services) | Broad with M365/Dynamics bundle options | Growing, narrower than AWS for specialised services |
| Ramp flexibility | Limited mid-term adjustment | Explicit ramp review mechanisms available | Negotiable milestone-based adjustments |
| Shortfall provisions | Cash payment; less buyer-friendly | Tier reduction; more flexible options | Negotiable; varies by deal |
| Credit availability | Migration, training, Marketplace, ProServ | Azure credits, M365 trials, co-sell incentives | Migration, PS, training credits; highly negotiable |
| Commercial complexity | Moderate (clean structure) | High (bundled ecosystem) | Moderate to high (deal-specific) |
| Competitive aggressiveness | Moderate; confident in market position | Moderate; uses ecosystem as defence | High; willing to price aggressively for wins |
Flexibility and Exit Rights Compared
Cloud commitment contracts are not the same as software licences — the workloads they govern are live production systems, not shelf-ware. This makes exit rights and mid-term flexibility provisions materially more important in cloud contracts than in traditional software licensing.
AWS EDP Flexibility
AWS EDP agreements are generally the least flexible once signed. Mid-term ramp adjustments require escalation to AWS's global commercial approval process and are typically granted only in documented extraordinary circumstances — major divestiture, regulatory prohibition, or force majeure events. Buyers who sign front-loaded ramps without appropriate protections often find they have limited practical recourse when migrations run late.
Azure MACC Flexibility
Microsoft Azure has introduced explicit mid-term review mechanisms for large MACC commitments, reflecting competitive pressure from AWS and GCP. These review mechanisms allow commitment adjustments at defined intervals (typically annually for multi-year MACCs) based on documented consumption performance. Microsoft's commercial team is generally more willing than AWS to engage on ramp structure modifications — particularly when the broader Microsoft relationship is not under threat.
GCP Private Agreement Flexibility
Google Cloud's private agreements are the most structurally flexible of the three in negotiation — in part because Google Cloud's commercial team has more deal-level authority and less rigidly standardised documentation than AWS or Microsoft. Milestone-based ramps, consumption-linked adjustment rights, and credit carry-forward provisions are all more readily negotiable in GCP private agreements. The trade-off is that the deal structure itself is more bespoke and requires more careful drafting.
"In the three-way cloud comparison negotiations we run for clients, Google Cloud consistently tables the most commercially aggressive proposal — but AWS's deal is often the most commercially certain, and Microsoft's deal is the most strategically complex. The right choice depends on your workload profile, your existing Microsoft relationship, and how much commercial risk you are prepared to carry."
Using All Three as Negotiating Leverage
The most powerful commercial position in cloud negotiation is having all three hyperscalers simultaneously competing for your commitment. This requires genuine technical credibility — the ability to demonstrate that your target workloads are portable and that your technical teams have evaluated each platform's capabilities. Providers with deep technical intelligence on your workloads can quickly identify whether a competitive evaluation is real or performative.
The multi-provider competitive process should be structured as follows:
- Technical scoping: Define the workloads under consideration with sufficient specificity that each provider can price them credibly. Avoid requests for generic discount percentages without workload context.
- Simultaneous RFP: Issue commercial proposals to all three providers simultaneously with a defined response deadline. Do not negotiate sequentially — sequential negotiation signals that one provider is preferred, eliminating competitive tension for the others.
- Cross-disclosure: Share relevant competitive commercial terms (not provider identity) with each provider at defined stages. "We have received a proposal in the X% range for this commitment level" is more effective leverage than an unsubstantiated claim.
- Best and Final: After an initial round of proposals and counter-offers, conduct a formal best-and-final round with a defined deadline. This creates urgency and drives each provider to their most competitive position.
- Selection and close: Select the preferred provider and use the selection decision to finalise the commitment structure and credit stack — the period immediately post-selection is when the awarded provider is most motivated to add incremental value.
This process consistently delivers outcomes 15–30% better than bilateral negotiations with a single preferred provider. Our cloud contract negotiation service runs managed multi-provider competitive processes for enterprises across all commitment tiers. The Cloud Contract Framework white paper contains the full commercial playbook.