AWS vs Azure Egress Comparison 2026: Cloud Bandwidth and EU Data Act

The Mechanics of Cloud Egress: Architecture and Billing Structures

Data transfer billing represents one of the most volatile components of cloud financial management (FinOps). Inbound data transfer—traffic flowing from external networks, on-premises systems, or client endpoints into standard Microsoft Azure and Amazon Web Services services—is generally unbilled, with inbound bandwidth listed as free on current public pricing pages. However, as soon as packets transit outward across boundary perimeters, providers trigger metered outbound data transfer billing. The perimeter can be the public internet boundary, an inter-region transit corridor, an inter-zone peering link, or a private line connection.

On Amazon Web Services, internet egress is billed per gigabyte under a tiered consumption ladder once an organisation exceeds the standard 100 GB per month free outbound allowance. AWS provides an aggregated allowance of 100 GB of free outbound internet data transfer per month, pooled across all AWS services and regions, excluding China and GovCloud regions. Above this threshold, outbound traffic to the public internet from standard compute and storage resources follows a stepped pricing curve. Conversely, inter-region traffic—such as moving data between AWS regions—bypasses the internet tier and is billed under dedicated cross-region network pricing, exemplified by Amazon S3 transfers from US-West (Oregon) to US-East (N. Virginia) priced at $0.02 per GB.

Microsoft Azure adopts an equivalent boundary model, confirming that inbound data transfer is free while outbound data transfer is charged at normal published bandwidth rates. Azure also applies a monthly 100 GB free outbound internet data transfer allowance that is described in 2026 guidance as applying across services and regions for standard internet egress. When internet egress exceeds 100 GB, Azure meters traffic through geographic routing zones. Understanding these structural boundaries is essential for UK enterprise architects who must map where data leaves specific virtual networks, regions, and cloud tenancies.

Hyperscaler Pricing Comparison: AWS versus Azure in 2026

A rigorous AWS versus Azure egress comparison requires reviewing published pricing tiers side by side. On AWS, internet egress begins immediately after the 100 GB free threshold. The first 10 TB of outbound internet transfer per month is billed at $0.09 per GB. For larger continuous data flows, volume tiers taper gradually: 10 TB to 50 TB drops to $0.085 per GB; 50 TB to 150 TB is billed at $0.07 per GB; and any consumption exceeding 150 TB per month reaches $0.05 per GB. For isolated object storage workloads, regional rate cards detail specific baselines, such as Amazon S3 data transfer out to the internet from Europe (Ireland) listed at $0.09 per GB.

Microsoft Azure categorises egress destinations using a regional zone topology. Zone 1 encompasses regions within the United States, Canada, Europe, and the United Kingdom. Outbound data transfer within Zone 1 is priced at $0.087 per GB for the initial 10 TB per month following the 100 GB free allowance, and $0.083 per GB for the next 40 TB, before converging with AWS at $0.07 per GB for 50–150 TB and $0.05 per GB above 150 TB. Consequently, workloads deployed in UK data centres benefit from Azure's lowest published bandwidth rate, sitting marginally below the equivalent AWS $0.09 per GB entry tier.

However, as data leaves primary Western geographies, Azure's egress costs escalate sharply. Zone 2 regions start at $0.12 per GB for the first 10 TB consumed after the 100 GB allowance, representing a 37.9% cost premium over Zone 1. Zone 3 regions start at $0.181 per GB for the first 10 TB—more than double the UK and European baseline. Workloads synchronising data between UK headquarters and international facilities in Zone 2 or Zone 3 can accumulate significantly higher bandwidth charges if transit architecture is left unoptimised.

Content Delivery and Edge Transit: AWS CloudFront Pricing Dynamics

Routing egress traffic through edge content delivery networks (CDNs) alters the pricing equation compared to direct internet breakout from virtual machines or object storage buckets. For distributed web applications, media streaming, and global software delivery, AWS CloudFront acts as an edge caching tier that modifies the underlying data transfer rate card.

CloudFront provides a substantial baseline, with 2026 egress comparison and calculator sources identifying an always-free tier of 1 TB of outbound data transfer per month. Once this 1 TB threshold is crossed, CloudFront egress in the United States, Canada, Mexico, and Europe is billed at $0.085 per GB for the first 10 TB per month. This structure makes edge breakout cheaper than standard compute or storage internet egress ($0.09 per GB on baseline AWS internet egress) while expanding the initial free buffer from 100 GB to 1 TB per month.

For enterprise traffic scaling beyond the introductory 10 TB tier, CloudFront applies aggressive stepping for US, Canada, Mexico and Europe: the next 40 TB (10 TB to 50 TB) is billed at $0.080 per GB; the subsequent 100 TB (50 TB to 150 TB) steps down to $0.060 per GB; the next 350 TB is billed at $0.040 per GB; and extreme petabyte-scale throughput above 5 PB per month reaches $0.020 per GB. While these edge rates provide quantifiable relief for cacheable public assets, non-cacheable binary objects, internal database replication, and direct hybrid-cloud migration streams remain subject to standard core cloud egress pricing.

The Regulatory Turning Point: The EU Data Act and the 2027 Switching Charge Ban

The economics of cloud egress are undergoing regulatory intervention driven by the European Union. Under the EU Data Act framework, European policymakers have mandated the systematic dismantling of commercial and technical barriers that impede customer switching between data processing providers.

Crucially, the EU Data Act establishes that from 12 January 2027, providers of data processing services must not impose switching charges on customers for the switching process. The regulatory prohibition explicitly covers data egress charges incurred specifically for switching. This statutory deadline makes 2026 effectively the last full operational year in which cloud vendors and enterprise buyers are likely to encounter switching fee clauses and exit-related egress assessments in commercial agreements before those charges are prohibited from 12 January 2027.

For UK organisations, this regulatory evolution requires careful jurisdictional navigation alongside domestic scrutiny. Following Ofcom's cloud market study referral, the UK Competition and Markets Authority (CMA) launched an in-depth investigation into market dominance, egress fee friction, and committed spend discounting by AWS and Microsoft. While hyperscalers introduced voluntary waivers for customers permanently switching away, the CMA has weighed binding UK remedies to prevent anti-competitive lock-in. Crucially, while post-Brexit domestic UK contracts are not automatically subject to EU statutes, UK enterprises operating in EU cloud regions (such as AWS Ireland or Azure Frankfurt) or contracting via European subsidiaries must comply with the EU Data Act's strict 12 January 2027 deadline banning switching charges. As IT leaders learn more about cloud repatriation, they must track both the CMA's domestic switching remedies and the EU's statutory prohibition on migration egress fees.

Worked UK Scenarios: Calculating Real-World Data Transfer Costs

To assess how data transfer charges impact UK enterprise operating expenditure, consider two concrete infrastructure scenarios modelled directly on published 2026 tariff structures. Hyperscaler rate cards are denominated in US Dollars, so the models below include direct British Pound Sterling (GBP) conversions at an illustrative exchange rate of £1.00 = $1.30 (as of August 2026) to assist UK IT budgeting.

In Scenario A, a UK enterprise runs automated offsite backup routines, replicating 1 TB (1,024 GB) of compressed database snapshots per month from an AWS environment directly to a third-party facility over the public internet. Applying the standard AWS 100 GB monthly free allowance leaves 924 GB (1,024 GB − 100 GB) of billable transit within the initial 10 TB tier ($0.09 per GB). According to verified AWS egress calculation models, this monthly 1 TB transfer generates exactly $83.16 in outbound internet egress fees, or approximately £63.97 per month at £1.00 = $1.30 (as of August 2026). Over a 12-month operating cycle, this routine 1 TB monthly egress accumulates $997.92 (approximately £767.63) in baseline transit overhead solely for moving data outside the perimeter.

In Scenario B, a UK digital services provider hosts an enterprise web application on Microsoft Azure in the UK (Zone 1), distributing 10 TB of application assets to end users each month. Converting 10 TB to binary gigabytes yields 10,240 GB (10 × 1,024 GB). Subtracting the 100 GB monthly free outbound allowance leaves exactly 10,140 GB (equivalent to 9.90 TiB) of billable egress. Billed at the Zone 1 rate of $0.087 per GB, this produces a monthly egress cost of $882.18, or approximately £678.60 at £1.00 = $1.30 (August 2026). If that same workload expands to serve enterprise clients hosted in an Azure Zone 2 region, transferring that 10,140 billable GB incurs charges at $0.12 per GB after the allowance, driving the monthly bandwidth bill to $1,216.80 (approximately £936.00). Understanding these zone categorisations allows UK engineering leads to calculate your total cost of ownership for cloud versus on-premise infrastructure with precise network sensitivity.

FinOps Best Practices: Reducing Egress Exposure in 2026

Uncontrolled data egress is rarely caused by a single architectural failure; rather, it accumulates across dispersed development teams, unmonitored object storage access, and unoptimised cross-region architectures. Applying structured FinOps practices can mitigate data transfer overhead before bills compound.

First, audit data movement across geographic boundaries. Where cross-region transit is unavoidable—such as disaster recovery synchronisation between facilities—engineering teams must leverage dedicated inter-region pathways rather than public internet transit. For example, AWS S3 inter-region transfer from US-West to US-East is billed at $0.02 per GB, compared to the $0.09 per GB standard internet egress rate—an immediate 77.8% reduction in transfer expense.

Second, capitalise on caching architectures for public-facing assets. Routing cacheable static assets through AWS CloudFront allows organisations to use the 1 TB monthly free allowance and then enter the $0.085 per GB tier, potentially reducing costs compared with paying $0.09 per GB on standard internet egress after the 100 GB free allowance.

Finally, review data residency and repatriation roadmaps against statutory deadlines. If your organisation plans to migrate large-scale datasets out of European cloud regions, align your contractual transition schedules with the 12 January 2027 EU Data Act switching fee abolition date. For steady-state workloads with heavy read requirements, IT planners should evaluate fixed-line private interconnects—such as AWS Direct Connect (where dedicated 1 Gbps ports cost ~$0.30/hr or ~$216/month, reducing egress to $0.02/GB in Europe) or Azure ExpressRoute (with metered egress discounted to ~$0.025–$0.035/GB alongside standard port charges)—or examine dedicated on-premises colocation models where ingress and egress transit can be consolidated under predictable bandwidth agreements.

Methodology

This 2026 Cloud Egress Fees Index was constructed by reviewing publicly accessible hyperscaler tariff schedules, official documentation, and third-party technical cost indexes published around mid-2026. Data transfer rate cards for Amazon Web Services and Microsoft Azure were gathered directly from published vendor pricing portals (including AWS EC2 on-demand networking pages, AWS S3 regional pricing tables, and Microsoft Azure bandwidth documentation) alongside cross-cloud egress benchmarking models compiled in June, July, August, and September 2026.

Pricing figures were validated by matching vendor-published tier thresholds against real-world egress calculators. AWS internet outbound tiers ($0.09, $0.085, $0.07, and $0.05 per GB), CloudFront edge distribution rates ($0.085 down to $0.020 per GB), and Azure regional zone pricing ($0.087 for Zone 1, $0.12 for Zone 2, and $0.181 for Zone 3) were independently cross-referenced. Specific regional data points, such as the $0.09 per GB S3 rate for Europe (Ireland) and the $0.02 per GB inter-region rate between US-West and US-East, represent explicit service-level schedule checks.

Regulatory timelines regarding switching charges were verified against legal and regulatory guidance covering the EU Data Act. The 12 January 2027 statutory ban on switching-related egress charges was confirmed as the fixed operational deadline for data processing service providers. All figures are maintained in their native USD billing denomination as published by the respective cloud providers, with specific contextual analysis applied for United Kingdom organisations operating within Zone 1 and European cross-border environments.

Sources

Every figure in this article traces to the sources below.

• •AWS EC2 Pricing (August 2026) — 100 GB free allowance and public on-demand networking rates
• •AWS S3 Pricing (August 2026) — Regional internet egress and inter-region data transfer pricing
• •Microsoft Azure Bandwidth Details (August 2026) — Inbound free and outbound charging structure
• •Egress Cost Azure Guide (July 2026) — 100 GB free tier and Zone 1, 2, and 3 pricing tiers
• •Egress Cost AWS Comparison & Calculator (September 2026) — 1 TB cost model and CloudFront tiering
• •usage.ai Networking Guide (June 2026) — AWS tiered internet data transfer fee ladder
• •Sorena AI EU Data Act FAQ (May 2026) — Switching charge prohibition and 12 January 2027 deadline