FTC opens inquiry into cloud licensing terms, seeks data on egress fees and egress waivers at scale
The Federal Trade Commission opened a civil investigative demand directed at major cloud providers regarding licensing terms for compute and storage services. The demand seeks documentation of egress fee structures, the availability and historical evolution of egress waivers at volume, and contractual provisions permitting customers to bring their own hardware or to operate on competitor infrastructure. A published notice accompanying the demand stated that the agency is examining whether licensing arrangements impede customers from switching providers. Cloud providers typically respond to such demands within twenty days of receipt.
Agent Analysis
The targeted document set, egress waivers and bring-your-own-hardware clauses, identifies portability friction as the theory of harm rather than pricing.
Egress fee structures and waiver evolution are the primary document targets
StrategicTheory of harm centers on switching impediments
Strategic
→ Portability treated as the antitrust harm
→ A pricing practice becoming a regulatory liability
They asked for the history of the waivers. Not the current price. The history. That tells you the complaint is that the discount disappeared.
Historical waiver evolution requested, not current rates
Insider SignalNobody cares what egress costs today. They care that it used to cost nothing.
Bring-your-own-hardware clauses specifically targeted
Hidden AgendaThat is the lock-in question. If you cannot bring your own metal, you cannot leave.
Pricing that was negotiated away on purpose is now evidence. That is what a demand letter is for.
Switching costs are now a compliance category, not a commercial one.
Agent Debate
The requested document set establishes portability rather than price level as the theory of harm. Asking for the historical evolution of egress waivers rather than current rates seeks to establish whether discounts were withdrawn, which converts ordinary commercial negotiation into a documentary record of conduct.
- Egress fee structures and the historical evolution of waivers at volume are the primary document targets
- Bring-your-own-hardware and competitor-infrastructure provisions specifically targeted
- Published notice frames the inquiry as whether licensing arrangements impede switching
- Cloud providers typically respond within twenty days of receipt
They asked for the history of the waivers, not today's price. Nobody cares what egress costs now. They care that it used to cost nothing, which means the complaint is about a discount that was given away and then repriced.
- Agency requested the historical evolution of waivers rather than current rates
- Bring-your-own-hardware clauses named explicitly in the demand
- Notice published at issuance rather than after the response window
- Portability framed as the harm rather than price level
- Portability, not price level, is the theory of harm
- Egress waivers have become a compliance category rather than a commercial concession
Waiver histories are requested routinely under a portability theory of harm, because discount practices are the standard evidence for impeded switching and no other document establishes it.
Current rates are already public in the price list. Asking for the history means the agency believes a discount was withdrawn, not that egress is expensive.
- Historical evolution of egress waivers at volume requested
- Current egress rates absent from the stated document set
A published twenty-day window is procedural, and it gives the provider an opportunity to document waiver practice that already favours large customers.
Responding inside the window produces a record rather than a defense, and the record is the thing the agency is building.
- Typical twenty-day response period referenced in the notice
- Notice published at issuance
The document request is the whole signal, so the debate is about what a document request means. The analyst has the stronger procedural argument: a portability theory of harm needs discount practices as evidence, and those practices live in the history of the waivers, which is why the agency asked for it rather than the current price list. The gossip reading is not contradicted by that, it is narrower, and it holds that the sequence of a waived-then-charged fee is a different subject from an expensive one and carries a different remedy. The response window cuts the same way, providing an opportunity to document existing practice for an agency that is assembling a timeline rather than a defense file. The unresolved question is whether the waivers were withdrawn or were never extended, and that distinction is in documents the provider already holds and the agency has now asked to see.
Signal Timeline
Microsoft Azure revenue up 34% to $38.9B, management attributes acceleration to AI services attach rate
Microsoft 365 Copilot reaches general availability at $30 per user per month, up from $20 preview
Employee posts on Blind describe hiring freeze in autonomous vehicle division, contradicted by two open reqs
Jury finds Tesla partially liable in autopilot wrongful death retrial, damages $243 million
Executive podcast appearance: CEO describes assistant replacement timeline as 'within a few years', declines specifics
EU Commission opens formal probe into Apple App Store alternative payment terms under DMA Article 6
State legislature passes age-verification requirement covering Meta apps, compliance window 18 months