Hyperscaler exit-egress waiver programs (AWS, Google Cloud, Azure)
Parent: Migration and Cutover Cost (Live Migration, mongosync, Dual-Running, Egress) · Published reference · snapshot 2026-10-31
↓ Facts as markdownall context files
Source-anchored research for Hyperscaler exit-egress waiver programs (AWS, Google Cloud, Azure). Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Structure and components
- Google’s exit program requires ending all use of the departing service, while other Google Cloud services may remain. It covers internet transfers for listed eligible products; moving only part of a service does not qualify. (low confidence) (verified as of 2025-09-11) [source]
How it works
- Google requires an Exit Notice before migration, an initial 14-day period, a subsequent 30-day initiation window, and at least a further 30-day migration period. Customers must notify support at least two working days before starting; extensions are possible under the documented process. (low confidence) (verified as of 2025-09-11) [source]
- Azure excludes normal service charges and transfers from ExpressRoute, ExpressRoute Direct, VPN, Azure Front Door and Azure CDN. For partner-purchased services, the partner handles the transfer, cancellation and credit process. (low confidence) (verified as of 2026-06-07) [source]
Comparisons and alternatives
- AWS, Google Cloud and Azure offer conditional credits for qualifying exit transfers; these programs require advance notification and completion of the provider-specific exit process rather than automatically eliminating ordinary egress charges. (medium confidence) (verified as of 2026-10-30) [source]
- Treat an exit-egress waiver as a network-cost reduction rather than a free migration: application changes, planning, staff time and skills remain migration costs. This is an operational inference supported by Forrester's analysis and independent expert commentary reported by Computer Weekly. (medium confidence) [source]
Facts and statements
- AWS's current FAQ covers complete exit or moving all data from a particular AWS service across eligible payer accounts. It requires advance approval and at least two months' notice before transfer begins. Remaining data and workloads in exited services must be deleted by the agreed completion date; account closure is an alternative. (low confidence) (verified as of 2026-10-30) [source]
- AWS exit credits cover internet data transfer, exclude standard service charges, and exclude specialized transfer services including Direct Connect, CloudFront, Snow Family and Global Accelerator. AWS can reclaim credits used for purposes other than exiting. (low confidence) (verified as of 2026-10-26) [source]
- Google requires a Completion Notice after the migration period, within 180 days of its end. Termination follows at a month-end at least 30 days later. Final invoices carry the transfer credit; production migrations during the later Data Recovery Period receive no credit. (low confidence) (verified as of 2025-09-11) [source]
- Azure's general offer requires advance support notice, a declared start date and transfer estimate, followed by cancellation of all associated subscriptions and a credit request. Eligible egress credits cover at most 60 calendar days from that start date; longer migrations should be described in the initial request. (low confidence) (verified as of 2026-06-07) [source]
- For UK-billed customers transferring from UK datacenters, Azure permits exit from individual services, covers internet and Microsoft Premium Global Network egress, and extends eligible egress credits to 180 days. Consumption of the exited services must end. (low confidence) (verified as of 2026-06-07) [source]
- AWS’s October 8, 2026 blog update gives eligible customers outside the EU 180 days to complete their exit; additional time requires notifying Support. Its FAQ leaves the applicable transition timeline to Support and refers EU and UK customers to separate addenda. (medium confidence) (verified as of 2026-10-08) [source]
- For migration budgeting, distinguish waived outbound transfer from total migration cost: AWS and Azure explicitly exclude ordinary service usage, so an egress waiver alone does not establish a zero-cost migration. (medium confidence) (verified as of 2026-10-30) [source]
Children
- No children recorded.