Cloud egress cost negotiation: eliminating the data-transfer tax.
Egress charges are among the most consequential hidden costs in enterprise cloud spend, and among the least often negotiated. This note sets out the economics of data-transfer pricing across AWS, Azure and Google Cloud, the free-egress-on-exit rules now reshaping leverage, and the commercial and architectural levers buyers use to reduce — or waive — egress entirely.
Egress is a deliberate switching cost, not a cost of goods — and it is now negotiable in a way it was not five years ago. The winning play combines architectural reduction of egress volume with commercial waivers secured inside a larger commitment. Buyers with a credible migration story and EU exposure have captured egress credits of $500K+ per provider.
01 Key findings
Egress pricing is asymmetric by design. Ingress is free; exit is charged. The mechanism exists to raise switching costs, which rise as stored data grows — making egress a lock-in lever, not a cost-recovery fee.
Egress is a material, under-managed line item. It runs 8–15% of total cloud spend for a typical Fortune 500 estate, and above 20% for data-intensive workloads — frequently never raised in commercial negotiations.
List rates are close; negotiated rates diverge sharply. First-10TB internet egress spans just $0.080–$0.090/GB across the three providers. The real spread opens up in negotiated credits, waivers and free-exit terms.
Regulation has opened the door. The EU Data Act and the UK CMA's cloud findings target egress as an anticompetitive barrier; all three providers now offer free egress for customers switching away in the EU.
Concessions come inside commitments, not standalone. Egress is waived as a named line item within EDP, MACC or CUD packages — rarely in response to an isolated request to "reduce data-transfer costs".
02 Egress rates by provider
List pricing for the three transfer types that dominate enterprise bills: internet egress (data to the public internet), inter-region transfer, and dedicated interconnect egress (Direct Connect, ExpressRoute, Cloud Interconnect). Rates below are indicative list; strategic accounts negotiate beneath them.
| Provider | Internet egress (first 10 TB) | Inter-region transfer | Interconnect egress |
|---|---|---|---|
| AWS | $0.090/GB | $0.01–0.02/GB | $0.02/GB outbound (Direct Connect) |
| Azure | $0.087/GB | $0.02/GB (same continent) | $0.025/GB outbound (ExpressRoute) |
| Google Cloud | $0.080/GB | $0.01/GB (same continent) | $0.02/GB outbound (Cloud Interconnect) |
Interconnect egress is cheaper than internet egress but rarely free — ExpressRoute and Direct Connect still meter outbound. Internet egress also tiers down with volume: AWS falls to $0.085/GB on the next 40TB and $0.07/GB beyond. Model committed volume against the tiered rate, not the headline.
03 Cost at scale
At list, one petabyte of monthly internet egress runs into six figures a month — over $1M a year on a single workload. Most enterprises run dozens. First-10TB internet-egress list rates, indexed to the highest:
At these rates, 1 PB/month of internet egress costs roughly $90,000 on AWS, $87,000 on Azure, or $80,000 on Google Cloud. The list winner is seldom the negotiated winner — a provider that opens higher but grants deeper credits can land cheaper net of commitment.
04 The egress lock-in trap
The strategic function of egress pricing is to make leaving expensive. Ingress is free, so data flows in frictionlessly; the cost is loaded onto exit, and it compounds with every terabyte accumulated. By the time a migration is contemplated, the transfer bill to move the data out can rival the annual saving from switching — which is precisely the intent.
Egress is a tax on optionality. Left unaddressed at signing, it silently erodes your future leverage: the larger your data estate grows, the more it costs to credibly threaten a move, and the weaker your position at every renewal. Neutralise it before data accumulates — secure exit and migration egress terms in the initial commitment, not when you are already trying to leave.
05 Free egress on exit
The market shifted materially in 2023–2024 as regulators turned to cloud switching costs. The EU Data Act (2023) requires providers to enable data portability and remove switching barriers, including disproportionate transfer charges. In 2024 the UK's Competition and Markets Authority named egress pricing as an anticompetitive practice. AWS, Azure and Google Cloud have all publicly committed to free egress for organisations switching providers in the EU.
Buyers headquartered or materially operating in the EU or UK can credibly cite portability obligations and policy risk in egress talks. Providers are sensitive to regulatory scrutiny and will offer accommodations to avoid appearing to breach the spirit of emerging data-portability rules — even where strict legal requirements do not yet bind. Egress is now a legitimate negotiation topic; providers can no longer simply decline to discuss it.
06 Negotiation levers
Egress concessions follow specific plays. Each works best embedded in a broader commitment conversation rather than raised in isolation.
| Lever | How it works | Best suited to |
|---|---|---|
| Quantify exposure | Present egress by workload, service and destination in precise figures — e.g. "800 TB/month, $72K, 11% of spend" | Every negotiation; generic asks fail |
| Bundle into commitment | Name egress waiver as a line item in an EDP / MACC / CUD package: "$X over three years, including waiver on analytics egress" | Renewals and new commitments |
| Invoke portability rights | Cite EU Data Act and CMA findings to frame egress as a contested practice, not settled pricing | EU / UK-exposed buyers; Azure, AWS |
| Credible switching story | Active multi-cloud evaluation prompts migration egress credits to lower the switching barrier | Buyers with genuine second-provider plans |
| Workload-specific waiver | Waive egress on named high-volume workloads (analytics, CDN, DR replication) via side letter | When blanket discounts are refused |
The credible-exit lever: 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 cost — the belief that you might move is what unlocks them.
07 Cost-reduction framework
The most cost-effective strategy attacks egress on two axes at once: reduce the volume architecturally, and reduce the price of what remains commercially. Organisations that work only one axis leave money on the table.
Quantify first
Break egress down by workload, service and destination before any conversation. Commercial teams respond to specific numbers, not complaints about "high data-transfer costs".
Reduce the volume
CDNs serve from edge locations closer to users; co-locating processing and storage in-region cuts inter-region transfer; re-architecting for less data chattiness moves compute to data rather than data to compute.
Negotiate the price
Embed egress waivers as named line items in EDP, MACC or CUD commitments. Framed inside a multi-year package, egress is far more concession-able than as a standalone request.
Apply regulatory pressure
Reference EU Data Act portability and CMA findings, and pair them with a credible switching scenario. Together they convert egress from accepted pricing into a contested, negotiable term.
08 Provider context
Each provider carries different commercial sensitivities that shape how egress talks unfold.
- Will move on egress inside EDP for large commitments
- Direct Connect reduces inter-location transfer cost
- Formulaic terms benchmark reliably once opened
- Views transfer pricing as integral to its model
- Slowest to respond to regulatory pressure
- Declines blanket egress discounts by default
- Acutely sensitive to European regulatory scrutiny
- ExpressRoute competitively priced
- Will include egress credits for primary-cloud commitments
- Egress interacts with complex EA terms
- Benefits from specialist advice to unpick
- Less forthcoming outside EU-exposed accounts
- Regularly offers free egress for AWS / Azure migrations
- Publicly committed to more competitive transfer pricing
- Uses egress as a share-acquisition tool
- Exceptional egress terms can mask total economics
- Must be weighed against the full commitment
- Best terms tied to genuine migration scenarios
09 Our recommendation
Do not expect blanket discounts. Open egress inside the EDP, anchor it to specific high-volume workloads, and pair Direct Connect with negotiated waivers on internet egress. Push hardest at renewal.
Lead with the EU Data Act and CMA findings, fold egress credits into the MACC and EA together, and let ExpressRoute carry inter-region traffic. Microsoft's regulatory sensitivity is your strongest lever.
Bring a genuine AWS- or Azure-to-GCP migration case and capture the free-egress terms on offer. Then lock the total commercial picture before incentives lapse — model economics net of every credit.
Quantify your egress exposure
Our Cloud & FinOps practice maps egress by workload and negotiates waivers as part of your broader cloud commitment.
The Licensing Edge
Weekly cloud and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.