Software
PublicCopilot Cowork puts Anthropic's brain in the enterprise operating system
Microsoft embedded Anthropic's Claude into M365 Copilot as 'Copilot Cowork' — $30/seat/month for autonomous AI agents that run across your emails, files, and meetings. The $99/seat E7 bundle is Microsoft's play to own the enterprise AI operating system.
Research
The verdict
NOT ISSUED — this refresh is scoped to definitional resolution (capex, backlog) ahead of the 2026-07-29 print. No directional call taken; Lenses 12/13 deferred under the Socratic gate.
Primary sources
SEC filings
Research Trail
Covered in the Knowledge Base
Artificial Intelligence
They built a design tool in a browser when everyone said it was impossible—then proved that collaboration, not features, was what designers actually needed.
They asked a question nobody else would: What if we redesigned the browser from scratch for how we actually use the internet today? The answer was Arc—and it's either the future or a beautiful dead end.
Source documents — open to read in full
The primary figure, stated exactly.
"For calendar year 2026, we expect the mix of short-lived assets to remain similar to Q3. We expect to invest roughly $190 billion in capital expenditures, which includes approximately $25 billion from the impact of higher component pricing." — Amy Hood, CFO, Microsoft FY2026 Q3 earnings call, 2026-04-29 [primary: transcripts/2026-q1.md]
Its exact definition, on all three axes:
| Axis | Value |
|---|---|
| Period basis | CALENDAR year 2026 (Jan–Dec 2026). Explicitly stated. Microsoft's fiscal year ends 30 June, so CY2026 straddles fiscal H2-FY26 and fiscal H1-FY27. |
| Lease treatment | INCLUDES finance leases. Microsoft's "capital expenditures" metric has always been capex including finance leases — Hood reports the lease component separately each quarter ("this quarter, total finance leases were $4.7 billion"). |
| Cash vs accrual | Accrual (goods-received) basis, not the cash-flow-statement line. Hood, same call: "Cash paid for PP&E was $30.9 billion, roughly in line with capital expenditures as the impact from finance leases was partially offset by differences between the receipt of goods and payment." |
The three numbers for one quarter — this is the whole problem in miniature. Fiscal Q3 FY26 (Jan–Mar 2026):
| Metric | Value | Source |
|---|---|---|
| "Additions to property and equipment" — cash-flow statement | $30.876B | [primary: 10-Q filed 2026-04-29, XBRL PaymentsToAcquirePropertyPlantAndEquipment] |
| Finance-lease right-of-use assets obtained — lease note | $4.009B | [primary: 10-Q, XBRL RightOfUseAssetObtainedInExchangeForFinanceLeaseLiability] |
| Naive sum of the two | $34.885B | |
| Management's "capital expenditures" | $31.9B (of which $4.7B finance leases) | [primary: Hood, FY26 Q3 call] |
You cannot reconstruct Microsoft's headline capex from the cash-flow statement. The naive sum overstates it by $3.0B in this quarter and understates it in others. Two reconciling items: (a) accrual-vs-cash timing on goods received, (b) an unreconciled ~$0.7B/quarter difference between Hood's stated finance-lease figure and the XBRL ROU-additions tag (9M FY26: Hood $22.5B vs XBRL $19.486B — a persistent $3.0B gap, flagged as an open item).
Why "$120B" exists — three routes, all arithmetically defensible, none of them calendar-2026.
Route 1 — the analyst's half-year residual (most likely origin). On the same call where Hood said $190B, the next question was:
"Maybe, Amy, could you elaborate a little bit on the CapEx guidance you just provided? Obviously, it requires a fairly material pickup in CapEx in the second half of the calendar year, maybe to the tune of $120 billion." — Karl Keirstead, analyst, Microsoft FY26 Q3 earnings call, 2026-04-29 [primary: transcripts/2026-q1.md]
The arithmetic: CY2026 H1 = fiscal Q3 FY26 actual $31.9B + fiscal Q4 FY26 guided ">$40B" ≈ $72B. Residual for Jul–Dec 2026 = $190B − $72B ≈ $118B. The "$120B" is a six-month figure, said out loud on the call, quoted since as if it were the year.
Route 2 — calendar-2025 actual (the base, not the guide). Management-definition capex, four calendar quarters of 2025:
| Calendar quarter | Fiscal label | Capex incl. finance leases | Source |
|---|---|---|---|
| Jan–Mar 2025 | FY25 Q3 | $21.4B | |
| Apr–Jun 2025 | FY25 Q4 | $24.2B | |
| Jul–Sep 2025 | FY26 Q1 | $34.9B | [primary: Hood, FY26 Q1 call, 2025-10-29] |
| Oct–Dec 2025 | FY26 Q2 | $37.5B | [primary: Hood, FY26 Q2 call, 2026-01-28] |
| CY2025 total | $118.0B |
Cross-check: CNBC reported the $190B guide as "up 61% from 2025". $190B / $118.0B = 1.610 → +61.0%. The base reconciles exactly. A source quoting "$120B+" is, on this route, quoting last year.
Route 3 — fiscal 2026, cash-only. The route the fiscal-vs-calendar hypothesis predicts — but it only lands on $120B if you strip both axes:
| Definition | Period | Figure |
|---|---|---|
| Capex incl. finance leases | Calendar 2026 (guided) | ~$190B [primary] |
| Capex incl. finance leases | Fiscal 2026 (Jul-25→Jun-26) | ~$144B+ |
| Cash PP&E additions only | Fiscal 2026 | ~$113B |
| Cash PP&E additions only | Calendar 2025 | $83.1B [primary: XBRL, four quarters] |
So the fiscal-vs-calendar axis alone does NOT explain the gap. Fiscal 2026 including leases is ~$144B — nowhere near $120B. It takes fiscal year and cash-only together to get there.
THE VERDICT. Microsoft's 2026 capex is ~$190B, and that figure is calendar year 2026, capital expenditures including finance leases, on an accrual basis, as guided by the CFO on 2026-04-29. The "$120B+" figure is not a competing estimate of the same quantity — it is (most likely) the H2-CY2026 residual an analyst named on the call, or the CY2025 base, or a fiscal-year cash-only cut. All three land at $113–118B, which is exactly why they are indistinguishable once the definition is dropped. The $70B "dispersion" in the big-four aggregate is not a disagreement about Microsoft — it is an undeclared-definition error. For any aggregate that sums management-guided, calendar-year, lease-inclusive capex, Microsoft's line is $190B.
The trap to avoid on the way out. There is a primary-source Microsoft number near $190B that has nothing to do with 2026 capex: $196.6B of leases signed but not yet commenced as of 2026-03-31, commencing across fiscal 2026 through fiscal 2031 [primary: 10-Q, Note 12 — Leases]. It is a five-year commitment stock, not an annual flow. Anyone citing "$190B" without saying which one is 50/50 to be citing the wrong one.
Desk rule this establishes: every capex figure in the KB and in any aggregate must carry (period basis, lease treatment) — e.g. MSFT $190B (CY2026, incl. finance leases, guided). Without both tags the number is not verifiable.
One more forensic consequence — Microsoft's reported FCF excludes finance-lease capex entirely. Reported free cash flow is OCF minus cash PP&E additions only:
| Quarter | OCF | Cash PP&E | Reported FCF | Finance-lease PP&E additions (not in FCF) |
|---|---|---|---|---|
| FY26 Q1 | $45.057B | $19.394B | $25.663B | $9.147B |
| FY26 Q2 | $35.758B | $29.876B | $5.882B (Hood: "$5.9 billion") | $6.330B |
| FY26 Q3 | $46.679B | $30.876B | $15.803B (Hood: "$15.8 billion") | $4.009B |
| 9M FY26 | $127.494B | $80.146B | $47.348B | $19.486B |
[primary: XBRL 10-Qs; Hood quotes from transcripts]
On a lease-adjusted basis, 9M FY26 economic free cash flow is closer to ~$27.9B, a 41% haircut to the reported figure. Only ~$4.0B of finance-lease payments touched the cash statements in the period (operating cash flows from finance leases $1.829B + financing cash flows from finance leases $2.179B) [primary: 10-Q, Note 12]. As the finance-lease mix moves, reported FCF moves for reasons that have nothing to do with the capital actually deployed — Hood said as much in Q2: "free cash flow was $5.9 billion and decreased sequentially, reflecting the higher cash capital expenditures from a lower mix of finance leases."
Disclosed (primary):
| Fact | Value | Source |
|---|---|---|
| Total remaining performance obligations | $633B as of 2026-03-31 | [primary: 10-Q, Note 11] |
| Commercial RPO | $627B, +99% YoY | [primary: 10-Q + Hood, FY26 Q3 call] |
| Weighted-average duration | ~2.5 years (commercial) | [primary: 10-Q — "with a weighted average duration of approximately 2.5 years"] |
| Recognised within 12 months | ~30% of total RPO; ~25% of commercial RPO (the 12-month slice itself +39% YoY) | [primary: 10-Q + FY26 Q3 call] |
| Recognised beyond 12 months | +138% YoY | [primary: Hood, FY26 Q3 call] |
| OpenAI concentration | ~45% of commercial RPO ≈ $281B (as of 2025-12-31) | [primary: Hood, FY26 Q2 call — "Approximately 45% of our commercial RPO balance is from OpenAI"] |
| Ex-OpenAI commercial RPO growth | +28% (Q2 FY26), +26% (Q3 FY26) | [primary: FY26 Q2 and Q3 calls] |
| Reporting basis | Commercial RPO "continues to be reported net of reserves" | [primary: Hood, FY26 Q2 call] |
| Committed-but-not-commenced leases | $196.6B, commencing FY2026–FY2031, terms 1–21 years | [primary: 10-Q, Note 12] |
| Supply posture | "we expect to remain constrained at least through 2026"; "customer demand continues to exceed supply" | [primary: FY26 Q3 call] |
The RPO time series — the single most useful table for 07-29 [primary: XBRL RevenueRemainingPerformanceObligation, 10-K/10-Q]:
| As of | Total RPO | QoQ Δ |
|---|---|---|
| 2024-06-30 | $275B | |
| 2024-09-30 | $266B | −$9B |
| 2024-12-31 | $304B | +$38B |
| 2025-03-31 | $321B | +$17B |
| 2025-06-30 | $375B | +$54B |
| 2025-09-30 | $398B | +$23B |
| 2025-12-31 | $631B | +$233B ← OpenAI contract |
| 2026-03-31 | $633B | +$2B |
The entire OpenAI commitment landed in one quarter. Since then the backlog has grown $2B — 0.3% sequential. Hood's framing is that commercial RPO ex-OpenAI grew 26% "in line with historic seasonality," and that the OpenAI contract "represents multiyear demand needs from them, which will result in some quarterly volatility in both bookings and RPO growth rates going forward." Both readings are on the record; the 07-29 sequential print is the tiebreak.
Confirmed still undefined (the KB flag is correct on two of three):
Tone across FY26 Q1 (2025-10-29) → Q2 (2026-01-28) → Q3 (2026-04-29):
The phrase that changed: Q1/Q2 discussed balancing supply across first-party vs Azure demand; Q3 introduced a forward supply-constraint horizon with a date attached ("at least through 2026") and paired it with a specific reacceleration claim (H2 CY2026). What is new and quantified: AI business annual run rate $37B, +123%; Copilot paid seats surpassed 20 million, +250% YoY; first-party model efficiency claims (MAI Transcribe One, 67% GPU efficiency gain; MAI Image Two, up to 260%) and Maia 200 "with over 30% improved tokens per dollar compared to the latest silicon in our fleet" now live in Iowa and Arizona — i.e. the COGS-reduction lever is being disclosed with numbers for the first time.
OpenAI agreement mechanics, as management describes them post-restructure: royalty-free IP access through 2032; revenue share running through 2030 with Microsoft's rev-share to OpenAI eliminated. Hood: "having the revenue share exist through 2030 — the predictability of that is a real positive for us — and, as Satya pointed out, the IP being royalty-free with the elimination of our rev share to them." [primary: FY26 Q3 call]
Unchanged read: this name trades on the Azure growth rate and the capex/FCF trajectory, not on the headline beat.
Presented as arithmetic on management's own guide plus published consensus. No base/bull/bear paths and no target are set in this file — that is Connor's, after his own read.
No forecast.ts created — logging a Brier-scored EPS call would be taking the directional position this refresh is explicitly withholding.
Nadella and Hood unchanged; the capital-allocation judgment is unchanged from 2026-06-18 and is carried by reference. Two governance deltas:
Three items, all sharpened by this pass:
| Lens | Status |
|---|---|
| 1 · Company overview | Carried — see deep-dive-2026-06-18.md. Correct the RPO attribution per the Corrections table. |
| 2 · Supply chain | Carried unchanged — see deep-dive-2026-06-18.md. Add only: Maia 200 now live in Iowa and Arizona; Cobalt in nearly half of datacenter regions and supply "expanding significantly" [primary: FY26 Q3 call]. |
| 3 · Moats | Carried unchanged. |
| 4 · Segments | Refreshed into segments.csv from the Q3 FY26 earnings release; no structural change. |
| 7 · Comps | Carried — see deep-dive-2026-06-18.md. Not re-sourced this pass; the June multiples are ~5 weeks stale and the whole cohort has moved. Treat as n/a — not re-sourced 2026-07-22. |
| 12 · Bull vs bear | DEFERRED under the Socratic gate. Not written in this file. |
| 13 · Devil's advocate | DEFERRED under the Socratic gate. Not written in this file. |
| 14 · Management questions | Carried — see deep-dive-2026-06-18.md. Three additions below, all now answerable from the disclosure. |
Three questions added to Lens 14, ordered by information value:
Ranked by how much each would change the file.
They almost died twice before finding product-market fit. Then they built the tool that made everyone else's productivity stack feel broken.