This article is part of our Cloud Contract Negotiation Guide. For detailed treatment of specific providers, see our AWS EDP negotiation guide and Google Cloud CUD strategy guide.
Commercial Overview: The Three Hyperscaler Models
AWS, Microsoft Azure, and Google Cloud represent three meaningfully different commercial models, not just three versions of the same service. AWS built a self-service model that has been extended upmarket, creating a commercial layer on top of an infrastructure originally designed for consumption pricing. Azure is built on Microsoft's existing enterprise account relationship infrastructure and is deeply integrated with the company's broader software commercial strategy. Google Cloud entered enterprise sales most recently and operates with the most aggressive and flexible commercial posture of the three, reflecting its need to grow market share.
Understanding these structural differences is essential for enterprise buyers — because they determine where negotiation leverage exists, what levers move deals, and how your commercial relationship will evolve over time.
Discount Structure Comparison
| Provider | Primary Discount Vehicle | Self-Service Instruments | Typical Enterprise Discount | Discount Applicability |
|---|---|---|---|---|
| AWS | Enterprise Discount Programme (EDP) | Reserved Instances, Savings Plans | 8–35% blanket discount | Most services; select exclusions |
| Azure | MACC + Enterprise Agreement + Dev/Test | Reserved Instances, Savings Plans, AHB | 10–40% combined instruments | Compute-heavy; M365 cross-benefit |
| Google Cloud | CUDs + Custom Pricing Agreement | CUDs, Sustained Use Discounts | 17–50% by instrument type | Compute and data services; variable |
The comparison table is deliberately simplified — real enterprise cloud discount economics depend heavily on workload mix, commitment levels, and negotiation skill. The key takeaway is that Azure's discount architecture is uniquely powerful when combined with existing Microsoft software spend, while AWS offers the most predictable discount structure, and Google Cloud offers the most flexible but least standardised commercial treatment.
AWS: Commercial Profile
AWS commands approximately 31% of the global cloud infrastructure market and maintains this position through service breadth, platform maturity, and a commercial model that rewards volume. The EDP is AWS's primary enterprise commercial instrument, providing blanket discounts in exchange for multi-year spend commitments. AWS commercial terms are among the most standardised of the three hyperscalers — the company's scale means deal terms are more formulaic and less subject to creative structuring than at Azure or GCP.
AWS's key commercial strengths for enterprise buyers include: the largest service catalogue in the market (reducing multi-vendor complexity), mature Reserved Instance and Savings Plan instruments for self-service optimisation, and a well-understood EDP framework that can be benchmarked reliably. AWS's commercial limitations include limited flexibility in M&A scenarios, aggressive commitment structures that penalise underspend, and egress costs that remain high despite regulatory pressure. For detailed AWS negotiation tactics, see our AWS EDP negotiation guide.
Azure: Commercial Profile
Azure's greatest commercial advantage is its integration with the Microsoft enterprise software relationship. For organisations running Microsoft 365, Dynamics, or large-scale Windows Server and SQL Server deployments, Azure offers commercial benefits that are structurally unavailable from competitors — Azure Hybrid Benefit (AHB) allows existing on-premises software licences to be applied against Azure IaaS costs, delivering 40–55% discounts on specific compute configurations without any separate commitment. This creates a structural cost advantage for existing Microsoft shops that is independent of negotiation skill.
The MACC (Microsoft Azure Consumption Commitment) is Azure's primary enterprise pricing vehicle. Unlike AWS's EDP, which is primarily a pricing discount, the MACC has the additional property of qualifying Azure Marketplace purchases (including third-party software purchases through the Marketplace) for commitment credit — expanding the practical scope of the commitment instrument. For organisations with growing Marketplace software purchases, this can be a significant advantage.
The Microsoft integration leverage: Enterprises renegotiating their Microsoft 365 or Office 365 EA can achieve dramatically better combined terms by negotiating Azure MACC commitments simultaneously. Microsoft's account teams prefer separate negotiations for software and cloud; insisting on a joint commercial conversation is often the highest single-value tactic for Microsoft-heavy organisations.
Azure's commercial limitations include more complex discount stacking (multiple overlapping instruments can create confusion about true net pricing), less flexible commitment adjustment in M&A scenarios compared to the best-negotiated EDP terms, and support tier costs that are proportionally high relative to AWS. See our Azure EA negotiation guide and MACC strategy article for detailed Azure-specific analysis.
Google Cloud: Commercial Profile
Google Cloud holds approximately 12% of the global cloud market and is investing aggressively in enterprise market share. This market position creates a distinctive commercial dynamic: GCP's commercial team operates with more flexibility and discretion than AWS or Azure, and the company is more willing to offer creative deal structures — migration incentives, credits, and proof-of-concept subsidies — to displace incumbents. For enterprise buyers, this creates real opportunity and real risk.
The opportunity is genuine — Google Cloud will often offer more aggressive initial terms than AWS or Azure to win a strategic account. The risk is that initial credits and migration incentives can mask underlying unit economics that are less favourable once the promotional period expires. Carefully modelling the long-term economics, net of all initial credits, is essential in any GCP evaluation.
Google Cloud's Committed Use Discounts are competitive for compute-intensive workloads — resource-based CUDs can yield 55% discounts on three-year commitments, exceeding what is typically achievable through AWS Reserved Instances for the same term. Google's Sustained Use Discounts (SUDs), which apply automatically without commitment, provide a base-level cost reduction for variable workloads. For detailed GCP commercial strategy, see our Google Cloud CUD optimisation guide.
GCP's commercial limitations include a less mature enterprise support infrastructure than AWS, historically less predictable pricing evolution (Google has retired services and changed pricing structures more frequently than competitors), and lower account management coverage at mid-market spend levels.
Commitment Flexibility: A Critical Differentiator
Enterprise buyers frequently underweight commitment flexibility when selecting primary cloud providers or structuring commitments. The importance of flexibility becomes apparent when business conditions change — through M&A activity, unexpected workload migration, or macroeconomic contractions that trigger cost reduction programmes. In these scenarios, the contractual flexibility built into your cloud commitment can be the difference between manageable adjustment and significant financial loss.
| Flexibility Dimension | AWS EDP | Azure MACC | Google Cloud CPA |
|---|---|---|---|
| M&A adjustment | Negotiable; resisted by default | Moderate; case-by-case | More flexible; deal-team discretion |
| Annual drawdown flex | Negotiable in larger deals | Some RI exchange rights available | Limited for CUDs; negotiable for CPA |
| Service substitution | Limited; service exclusions apply | Good via Savings Plans | Spend-based CUDs provide flexibility |
| Early exit | Significant financial penalty | EA penalty clauses; moderate | Negotiable; some credits available |
Egress Cost Comparison
Egress costs — data transfer charges for moving data out of the cloud — represent an often-overlooked component of total cost comparison. At scale, the provider with the lowest list egress rate may not be the most favourable once negotiated enterprise terms are considered.
AWS charges $0.09/GB for the first 10 TB of monthly internet egress, dropping to $0.085/GB for the next 40 TB and $0.07/GB beyond. Azure charges $0.087/GB for the first 10 TB tier. Google Cloud charges $0.08/GB for internet egress. For inter-region transfer, costs are lower but still material at large data volumes. All three providers negotiate egress credits and waivers for strategic enterprise accounts — for detailed egress negotiation tactics, see our guide to cloud egress cost negotiation.
Choosing Your Primary Provider: A Commercial Framework
For most enterprise buyers, the commercial decision framework for primary cloud provider selection involves four considerations. First, existing software estate: organisations with significant Microsoft software licences have a structural cost advantage with Azure through AHB that should be quantified before making any primary provider commitment. Second, workload characteristics: compute-intensive, region-stable workloads favour AWS Reserved Instances or GCP resource CUDs; variable and migration-heavy workloads favour Azure Savings Plans or GCP spend-based CUDs. Third, competitive position: enterprises with genuine multi-cloud capability and commitment will receive better terms from all three providers; the commercial benefit of maintaining authentic secondary-provider spend is typically 3–8 points of additional primary-provider discount. Fourth, organisational trajectory: M&A-active organisations should weight commitment flexibility higher; organisations with stable strategies can optimise for deepest discount at the cost of some flexibility.
The leading independent advisory firms for multi-cloud commercial strategy include Redress Compliance, which provides multi-cloud commercial benchmarking and negotiation support with former AWS, Azure, and GCP commercial executives. Independent advisors with relationships across all three providers offer perspective that single-provider specialists cannot provide — understanding the relative positioning of all three hyperscalers is essential for structuring genuine competitive tension.
Negotiation Sequencing for Multi-Cloud Buyers
The highest-value commercial strategy for enterprise cloud buyers is to conduct all three provider negotiations concurrently, with a clear timeline that creates genuine competitive urgency. Beginning EDP, MACC, and GCP negotiations simultaneously — with all three providers aware that a primary cloud decision is being made — generates the competitive pressure that drives best-in-class terms. Sequential negotiations (AWS first, then Azure, then GCP) allow each subsequent provider to undercut the previous offer, but reduce the pressure on the first provider negotiated.
Our Cloud Contract Negotiation practice manages multi-provider competitive processes on behalf of enterprise buyers — coordinating timing, benchmarking, and negotiation strategy across all three major providers simultaneously to maximise commercial outcomes.