Azure bandwidth free grants and GCP Internet egress free tiers also cliff: quiet months mislead averages once complimentary allotments end. Map path class first, price only above-cliff GB with dated $/GB, and sibling-check the AWS Internet egress free-tier cliff spoke.
Updated
Complimentary bandwidth and egress allotments end — model Azure free-grant and GCP free-tier cliffs beside the AWS cliff spoke.
Path matrix: Azure bandwidth vs GCP Internet egress free-tier cliff drivers (educational)
Dated starting points only — Unknown until verified means no invented $/GB. PipeToll does not scrape private consoles or guarantee figures.
PipeToll’s free-tier cliff vocabulary extends beyond AWS. This matrix covers Azure bandwidth free-grant and GCP Internet egress free-tier cliffs as siblings to the AWS Internet egress free-tier cliff. Complimentary allotments are real — and finite. Educational arithmetic only; no guaranteed savings.
Path templates to model
Azure public Internet bandwidth from compute/LB — classic bandwidth meter; free grant / trial text matters.
Azure Blob → Internet downloads — Blob bandwidth vs storage ops; don’t paste one number.
GCP Internet egress from Compute Engine / GKE — Always Free / Free Trial interactions; confirm current SKU.
GCS public GET traffic — download meters vs ops classes; multi-region placement ≠ free downloads.
Same workload on AWS — walk the sibling AWS cliff with identical GB for apples-to-apples FinOps.
Common traps
Annualizing a $0 free-tier month. Blending Azure bandwidth grants with Blob ops. Assuming GCP Always Free covers every Internet path forever. Forgetting CDN edge free tiers can create a second cliff while origin fill still bills. No scorecrowns from Incomplete cells — badge Unknown until verified.
FinOps checklist
Identify which SKU meters your Internet path (bandwidth vs egress vs download).
Read current free grant / Always Free / trial text for that SKU — date-stamp the cite.
Worked estimate walkthrough: 1,500 GB above Azure/GCP free grants
Remaining ≈ 1,500 GB × $/GB in Mode A after a free grant (exact grant GB stays Unknown until verified). Cite dated sources — Azure Bandwidth pricing and GCP network pricing / Free Tier (as-of 2026-09-09) — before pasting rates. Run once with Azure vocabulary and once with GCP; sibling-check the AWS cliff. Synthetic only; no savings guarantee.
The point where complimentary egress or bandwidth allotments end and list $/GB begins. Averages that ignore cliffs mislead FinOps reviews — see the glossary term.
Are Azure and GCP grants identical to AWS?
No. Vocabulary (bandwidth vs egress), product surfaces, and trial vs always-free rules differ. Map path class first.
How do I price above the cliff?
Use calculator Mode A with a verified $/GB for the path alone. Cross-link the AWS cliff spoke for the same workload shape.
