Microsoft: capex bear market or FCF inflection buy? Running the burger through the depreciation wedge

⟳ UPDATE — 2026-07-29 (Q4 FY26 earnings): the check

This note was authored 2026-07-02 as a checkable prediction ahead of Q4 FY26 earnings. Those results are now out. The original thesis and tool are preserved unchanged below for the record; this block scores it against the actuals.

Verdict so far: the thesis is winning, and the market agrees — shares jumped ~8% after hours. Three of the four drivers moved bullishly versus my base case; the one that got worse (capex) was defused by the two moves I'd flagged to watch (FCF-positive guide + the lease/useful-life accounting).

Results: Q4 revenue $90.0B (vs. ~$87.6B est), adjusted EPS $4.74 (vs. $4.24 est; GAAP $4.81). FY26 revenue >$331B (+18%), operating income >$155B (+21%). Note the beat was flattered by a $3.2B Anthropic investment gain and lower voluntary-retirement costs — so the operating beat is real but smaller than the headline. Azure crossed $100B annual revenue; Microsoft Cloud >$214B.

Scorecard vs. the four drivers:

Driver	Note's base assumption	Actual / new guide	Read
Azure (meat)	Glide down to ~32% by FY27-end	Guided ~45% CC for Q1 FY27, accelerating, still capacity-constrained	✅ Bullish — moved opposite my base, the meat is cooking hotter
Capex (wedge)	Plateau ~5-12%/yr = bull/base	Still rising — Q1 FY27 capex >$50B; FY27 elevated, "further growth"	❌ Bearish — no plateau; the arms race did not stop
M365 (bread)	High-teens growth	Held; PBP guided +~16-17%	➖ In line
Copilot (garnish)	~7% penetration by FY29	>30M paid seats now (~6.7% of ~450M base)	✅ Bullish — hit the FY29 base case ~2yr early

FCF: Q4 free cash flow $19.6B, down 23% — the squeeze got worse, as expected. But Hood explicitly guided FCF-positive for FY27, directly rebutting the "FCF stays trapped" bear tail.

The lease/useful-life move (your specific question — and I have to correct my earlier take): The pre-earnings "$255–260B FY27 capex" figure I cited was a preview estimate and is now wrong/not comparable. What Hood actually announced, effective start of FY27: - Useful life of data-center + office buildings extended 15 → 25 years. Slows annual depreciation on the long-lived (~⅓) bucket. She said this only shifts timing of depreciation with minimal FY27 operating-income benefit — but note it flatters every future margin comparison, and it does not touch the short-lived GPUs/CPUs (~⅔ of spend), which is where the real obsolescence debate sits. - More future data-center leases shift from finance leases to operating leases. Her exact mechanic: "finance leases are included in capital expenditures while operating leases are not" — so operating-lease capacity drops out of the reported capex line and is expensed as rent through opex instead. - Net optical effect: this reclassification restates calendar-2026 capex from ~$190B down to ~$175B with zero change in actual spending. So the headline capex number falls, but the cash committed to compute is unchanged. This is the "GAAP-ugly vs. cash-reality" gap in my note working in reverse — it now makes the capex line look milder than the underlying spend. A skeptic's flag (rightly): stretching depreciation schedules on assets at the center of an obsolescence debate is a choice that flatters margins.

What this does to the note's core question ("does capex plateau, unlocking a convex FCF inflection?"): capex did not plateau in absolute terms — so on the literal wedge, the bear was right. But the market re-rated up anyway, because (a) Azure re-accelerating to 45% means the capex is demand-backed, not stranded, and (b) the FCF-positive FY27 guide + the depreciation-stretch together break the "FCF trapped forever" tail even without a spending plateau. The thesis' spirit (capex is productive, cash inflects) is being validated through a different mechanism than the one I modeled. Tool driver re-baseline (Azure up, Copilot up, capex still-high, add a lease/depreciation-accounting factor) is now warranted — flagging as the next step, not done in this addendum.

MSFT is down ~27% off its January 2026 high, to a 52-week low near $349 before bouncing to ~$390 — despite Azure growing 40%, the AI business hitting a $37B run rate (+123% YoY), and a fourth straight EPS beat. This isn't an earnings problem. It's a capex-return problem, and the market is currently pricing the pessimistic answer to one specific, checkable question: does capex plateau by FY27, letting free cash flow inflect, or does the AI arms race keep pushing capex higher than revenue can follow?

The trailing numbers already show the fork. Operating cash flow is $170.1B TTM, up 26% — the business itself is compounding fine. But capex is $97.2B TTM and running toward a ~$150-190B annualized pace (including finance leases), so free cash flow is stuck at $72.9B, essentially flat versus last year. Because roughly two-thirds of that capex is short-lived GPU/CPU hardware on a 3-5 year depreciable life, the resulting depreciation is about to grind through GAAP earnings for several more quarters regardless of what happens next — GAAP EPS will look "ugly" even in the bull case. The disagreement worth having isn't about GAAP; it's about whether the cash line turns before the market gets impatient.

The meat: Azure

Azure is the only driver that can actually break this thesis. It's currently growing 40% (39% CC), with AI services contributing roughly 12 of those points, up from 9 a year ago — meaning ~28 points of growth is still ordinary cloud migration, not an AI bubble metric. Azure is also supply-constrained, not demand-constrained: management has said growth would be higher with more capacity. The base case assumes an orderly deceleration — 40% now, ~32-35% by FY27-end, ~25% by FY29 — because a $250B+ run-rate business mathematically can't hold 40% forever. The tell to watch isn't the level, it's the slope: a smooth glide is maturation; an abrupt break below ~27-30% ahead of schedule, especially if it coincides with capacity going unused, would be the demand-side alarm that invalidates the whole thesis.

The wedge: capex growth (not the level — the rate of change)

This is the actual pivot variable. The FCF inflection isn't triggered by revenue accelerating — it's triggered by capex growth simply stopping. As long as OCF keeps compounding at ~15-25%/yr while capex growth decelerates toward flat, the gap between the two lines (i.e., FCF) widens fast and bends convexly upward. Q4 FY26 earnings (July 28, 2026) is the first real data point: the specific sentence to watch is how management frames the FY27 capex guide — "still ramping" keeps the thesis in bear territory; "moderating" or "plateauing" is the earliest confirmation of the bull/base case.

The bread: M365 Commercial cloud (funds the kitchen, isn't what's being built)

M365 Commercial cloud (+19%, 15% CC) is not what today's capex is for — that's Azure AI infrastructure. M365 runs on mature, cheap-to-serve software and carries the highest margin in the company. Its role here is different from Azure's: it's the demand/margin health signal and the high-margin cash that funds the buildout, so it governs FCF magnitude, not direction. If it decelerates, the FCF snap-back still happens (assuming Azure and capex behave), just with a shallower slope and a slightly worse blended margin as revenue mix tilts toward lower-margin Azure AI.

The garnish: Copilot (validates the bet, but it's hedged)

Copilot paid seats sit at roughly 20M, or ~4.4% penetration of the ~450M commercial M365 base — the lowest conversion of any major AI platform, even after seats jumped from 15M to 20M in a single quarter. Copilot's real job is validating that giving first-party AI priority claim on scarce GPUs was worth it. But because the compute fleet is fungible, a Copilot disappointment with Azure demand intact just means that capacity gets reallocated to paying Azure customers — a higher-ROIC outcome, and close to FCF-neutral. The failure mode that actually matters is Copilot and Azure demand softening together, which would mean the fungible-fleet hedge has nothing to reallocate into. Watch paid seats and M365 Commercial cloud growth (where Copilot revenue actually shows up); ignore total-user and DAU counts, which are engagement theater, not monetization.

Base case, in numbers

At a ~$385 entry, the base case assumes Azure glides to ~32% by FY27-end, capex growth decelerates to roughly 12%/yr, M365 Commercial cloud holds high-teens growth, and Copilot penetration reaches ~7% by FY29. That implies FY29 EPS near $24, a modest re-rate to ~24x (versus ~22x today, well below the ~30-32x five-year average), and a three-year target near $580 — roughly 15%/yr price return plus a ~1.5%/yr blended dividend-and-buyback yield, near 16-16.5%/yr total. Notably, that $580 three-year target sits only modestly above where Street consensus already expects the stock in twelve months (~$529-560), so the base case is giving the thesis two extra years to clear a bar it's nominally supposed to clear in one — that gap is the margin of safety.

What's already priced in

The ~27% drawdown has priced in real capex-return skepticism: forward P/E at ~21-22x is the cheapest since 2023, and the technical picture confirms the pessimism (below both the 50- and 200-day moving averages, a death cross, RSI in the low-to-mid 30s). What is not obviously priced in: the ~27% OpenAI equity stake worth roughly $135B, the OpenAI relationship's shift to a capped, non-exclusive structure through 2032 (de-risking the concentration story), and the mechanical fact that FCF doesn't need heroic revenue growth to inflect — just a capex plateau.

Risks worth tracking

The dominant risk is that the arms race doesn't stop: AWS and Google are building identical AI capacity, and if Azure's growth premium over them compresses at the same time capex keeps climbing, the entire capex-return bet is broken, not just delayed. Secondary risks: the EU's "Cloud Gatekeeper" designation under the Digital Markets Act creates a licensing/pricing overhang on Azure; component (DRAM/NAND) cost inflation could keep pressuring margin independent of the capex-growth story; and OpenAI, while now capped and non-exclusive, remains a large single-partner concentration inside the $627B RPO backlog.

Bottom line

This is a rerating story, not a broken business — the multiple compressed by roughly a third while earnings kept growing. The single checkable disagreement with the market is whether capex plateaus on schedule; everything else (Azure, M365, Copilot) is either confirming evidence or a magnitude modifier, not the trigger. At ~$385, I'm underwriting the bond-like base case (~15-16%/yr) with real upside optionality if the convex snap-back shows up, and I'm treating the July 28 FY27 capex framing as the first real checkpoint rather than a reason to wait longer.