The Projection — a symmetric watercolor butterfly

The Projection

The surface is never the system.

AI

Microsoft Capex

Earnings 07-29 is the near-term test — the "$97B TTM" figure is OUR arithmetic (unconfirmed; $80.1B 9-mo FY26 is the IR number). Crawl 07-27 traced: WI+GA "AI superfactory" (~2GW, fiber-linked) + a distinct Pecos TX ~2GW on Chevron's Kilby PPA ($7B, 2.7GW); Maia 200 confirmed DUAL-PURPOSE (OpenAI inference + MAI training) with the split undisclosed; TMI/Crane restart tracking 2027; $37B AI run-rate +123%. The $250B OpenAI commitment has NO disclosed capex mapping — nobody publishes the OpenAI-vs-own split. Watch Wednesday: FY26 full-year capex, FY27 guide, any split disclosure.

STATUS · DEVELOPING OPENED · 2026-07-23 LAST SEEN · 2026-09-03
Microsoft

Summary

Microsoft's Azure business crossed $100 billion in annualized revenue this morning, the clearest monetization proof point from last night's earnings.

Whether Microsoft ever discloses the split between OpenAI-inference and its own MAI-training workloads on Maia 200 remains the open question.

2026-09-02 — Microsoft collapses three reporting segments into two — “Agents and Infra” and “Devices and Consumer” — and promises quarterly revenue for each key business

2026-08-10 — Microsoft reportedly books 300,000+ Maia 300 chips from TSMC

2026-07-29 — CORRECTED 2026-09-01: Microsoft’s FY27 capex guidance was NOT purely qualitative — a hard $175B figure was given on the same call

2026-07-29 — Earnings beat, Azure accelerates, the named split still didn’t happen

2026-07-23 — Thread opened, quiet

← Backstory

(finding: artifacts/findings/microsoft-capex-2026-07-27.md · bundle: artifacts/bundles/microsoft-capex-2026-07-27/provenance.yaml)

This week's evidence

🕰 Correction, not addition: Microsoft's 07-29 earnings call did NOT leave FY27 capex guidance purely qualitative, as this map's own record stated. CFO Amy Hood gave a hard figure — "approximately $175 billion" — tied to a 15-to-25-year useful-life accounting change that shifts future leases from finance to operating classification; the map was right to reject the ~$255-260B analyst-preview number but wrong to call the guide purely qualitative. Caught by the cold rotation. (Earnings transcript via The Globe and Mail) 2026-08-31
Microsoft filed an 8-K at 16:30 ET collapsing its three reporting segments into two from FY27 — "Agents and Infra" and "Devices and Consumer" — with quarterly revenue disclosed for each key business, Azure included. Nadella's note: AI is "blurring the boundaries between our products and reshaping our business models." The capex-to-revenue question this map asks of every hyperscaler print becomes answerable at the Azure line. On Microsoft Capex. (Microsoft 8-K, Exhibit 99.1) 2026-09-02
Microsoft's 8-K of Wednesday evening restructures FY27 reporting into two segments — "Agents and Infra" and "Devices and Consumer" — with quarterly revenue disclosed for each key business, Azure included. Dated 09-02 and in that digest's late catch; noted here because it is the first time the capex-to-revenue question can be answered at the Azure line rather than inferred. (Microsoft 8-K, Exhibit 99.1) 2026-09-03

Related threads (shared entities)

· Memory Squeeze
· Microsoft's Hedge
· Hyperscaler Capex
· Compute Spend
· Power Buildout
· In-House Silicon
· Nuclear for AI
· Big Tech into Health
· Microsoft Health
· Dragonfly Return
· Mistral AI
· Targets