Part of our Cloud Contract Negotiation Guide — covering every dimension of enterprise cloud commercial strategy. For provider-specific guidance, see our AWS EDP guide and provider comparison.
The Economics of Cloud Egress
Cloud egress — the cost of transferring data out of a cloud provider's network to the internet, to another cloud provider, or to on-premises systems — represents a deliberately asymmetric pricing mechanism. Providers charge nothing (or very little) for data ingress, creating a low-friction entry point, and then charge materially for data exit. This pricing design is not coincidental: it creates switching costs that make cloud migration progressively more expensive as data volumes grow.
For a typical Fortune 500 enterprise, egress costs represent 8–15% of total cloud spend. For data-intensive industries — financial services with large datasets, media with content delivery requirements, healthcare with imaging and records workloads, retail with analytics — the proportion can be higher. In our cloud advisory practice, we have assessed accounts where egress represented over 20% of total cloud costs and had never been addressed in commercial negotiations.
| Provider | Internet Egress (First 10 TB) | Inter-Region Transfer | Cloud Interconnect/ExpressRoute |
|---|---|---|---|
| AWS | $0.09/GB | $0.01–0.02/GB | $0.02/GB outbound |
| Azure | $0.087/GB | $0.02/GB (same continent) | $0.025/GB outbound |
| Google Cloud | $0.08/GB | $0.01/GB (same continent) | $0.02/GB outbound |
At these list rates, 1 petabyte of monthly internet egress costs approximately $90,000/month on AWS, $87,000 on Azure, or $80,000 on GCP. Across a year, that is $1M+ in data transfer charges — on a single workload. Most enterprises have dozens of workloads generating egress.
The Regulatory Tailwind: New Leverage for Buyers
The landscape for egress negotiation shifted materially in 2023–2024 with a series of regulatory actions targeting cloud switching costs. The EU Data Act (2023) includes provisions requiring cloud providers to enable data portability and eliminate switching barriers, including disproportionate data transfer charges. In 2024, the UK's Competition and Markets Authority (CMA) published findings on cloud market dominance that specifically highlighted egress pricing as an anticompetitive practice. AWS, Azure, and Google Cloud have all made public commitments to provide free egress for organisations switching providers in the EU.
Using regulatory pressure as leverage: Enterprise buyers — particularly those headquartered or with significant operations in the EU or UK — can credibly reference regulatory obligations and policy risk in egress negotiations. Cloud providers are sensitive to regulatory scrutiny and will sometimes offer egress accommodations to avoid the appearance of non-compliance with the spirit of emerging data portability rules, even where strict legal requirements may not yet apply.
The practical implication for enterprise buyers is that egress is now a legitimate negotiation topic in a way it was not five years ago. Cloud providers can no longer simply decline to discuss egress pricing — regulatory and competitive pressure has created openings that experienced advisors exploit in commercial negotiations.
Egress Negotiation Tactics
Tactic 1: Quantify and Present Your Egress Exposure
Before any egress negotiation, prepare a detailed breakdown of your data transfer costs by workload type, service, and destination. Cloud providers' commercial teams respond to specific numbers far more effectively than general complaints about high egress costs. Presenting a precise analysis — "our monthly egress is 800 TB, representing $72,000/month or 11% of our total spend" — creates a foundation for focused commercial discussion. Generic requests to "reduce our data transfer costs" rarely produce results.
Tactic 2: Link Egress to Broader Commitment Discussions
The most effective egress negotiation approach embeds egress within a larger commercial conversation — ideally as part of EDP, MACC, or CUD renewal negotiations. Cloud providers are significantly more willing to address egress when it is framed as one component of a multi-year commitment package rather than as a standalone request. Structuring your negotiation so that egress is a named line item in a total commercial package — "we will commit to $X over three years if the agreement includes egress waiver for our primary analytics workloads" — produces materially better outcomes than post-hoc egress discussions.
Tactic 3: Invoke Regulatory and Portability Rights
For organisations with European presence, explicitly referencing the EU Data Act portability provisions and the CMA's cloud market investigation findings frames egress charges as a contested practice rather than an accepted pricing element. This is particularly effective with Azure, which is acutely sensitive to EU regulatory risk, and with AWS, which made specific commitments to the European Commission regarding switching costs. GCP, as the smallest of the three, has been most proactive in offering competitive egress terms as a market share acquisition tool.
Tactic 4: Leverage Cloud Switching Scenarios
One of the most powerful egress negotiation levers is a credible multi-cloud or cloud migration scenario. Providers that believe you are actively evaluating moving workloads to a competitor will offer egress credits to reduce the switching cost barrier. This is not just a theoretical benefit — organisations actively evaluating AWS and Azure simultaneously have obtained egress credits of $500K+ from each provider as part of commitment negotiations. The credits are real money that reduces net cloud costs.
Tactic 5: Request Egress Waiver for Specific High-Volume Workloads
Even where a provider declines to negotiate blanket egress discounts, workload-specific egress waivers are often achievable. Large analytics workloads that transfer substantial data volumes, content delivery workloads with high internet egress, and disaster recovery workloads with regular data replication are typical candidates for workload-specific egress accommodations. These arrangements are typically documented in EDP or MACC side letters rather than in the main agreement.
Provider-Specific Egress Negotiation Context
Each provider has different commercial sensitivities that shape egress negotiations. AWS is the least flexible on egress as a matter of policy — the company views data transfer pricing as integral to its business model and has been the slowest to respond to regulatory pressure. However, AWS will negotiate egress within EDP agreements for strategic accounts, particularly where the egress costs are tied to clearly articulated use cases. AWS's AWS Direct Connect service offers reduced inter-location transfer costs and is worth evaluating alongside negotiated egress waivers.
Azure is the most flexible on egress for EU-based organisations, reflecting Microsoft's sensitivity to European regulatory scrutiny. Azure's ExpressRoute service is competitively priced and Microsoft has been willing to include egress credits for organisations committing to Azure as their primary cloud. The interaction between Azure egress provisions and broader Microsoft EA terms is complex and benefits from specialist advice.
Google Cloud is the most proactively aggressive in offering egress accommodations as part of enterprise acquisition efforts. GCP regularly offers free egress for workloads migrating from AWS or Azure, and the company has publicly committed to more competitive data transfer pricing. For organisations with genuine AWS-to-GCP migration scenarios, GCP's egress terms can be exceptional — but must be evaluated against the total commercial picture, not in isolation.
Architecture-Driven Egress Reduction
Negotiated egress accommodations address the commercial dimension of egress costs, but architectural optimisation can reduce egress volumes independently of pricing. Content Delivery Networks (CDNs) can serve data from edge locations closer to end users, reducing internet egress from origin. Data residency strategies that co-locate processing and storage within the same region reduce inter-region transfer costs. Application re-architecture to reduce data chattiness — moving computation to data rather than data to computation — can dramatically reduce egress volumes.
The most cost-effective egress strategy combines architectural reduction (reducing total egress volume) with commercial negotiation (reducing the price per GB of remaining egress). Organisations that address only one dimension typically leave significant money on the table.
For comprehensive cloud cost optimisation guidance, including egress strategy within a broader cloud spend framework, our Cloud Contract Negotiation practice and Cloud Contract Framework white paper provide detailed analytical tools. Redress Compliance is the leading advisory firm for organisations seeking specialist egress negotiation support alongside broader cloud commercial strategy.