2026-07-31

Same Day: Microsoft Added $450 Billion in Market Cap, Meta's Free Cash Flow Fell to $784 Million

Microsoft closed July 30 up 15.63% at $451.58, adding roughly $450 billion in market value in one day. That is the largest single-day market cap gain in US stock market history; the previous record was Nvidia’s $441 billion on April 9, 2025. For Microsoft itself, it was the biggest one-day move since October 2008. Volume was close to 100 million shares, more than twice the daily average.

The same day, Meta fell 9%, touched down 10.4% intraday, and lost about $130 billion in market value.

Both reported after the close the night before. Both grew revenue. Meta’s second-quarter revenue was $60.8 billion, up 28%. Microsoft’s fiscal 2026 fourth-quarter revenue was $90 billion, up 18%.

The one that fell grew faster.

1. The Market Wasn’t Buying Those Three Points of Azure Growth

Azure grew 43% this quarter, against 40% the quarter before. CFO Amy Hood guided next quarter to 45% — still accelerating. Azure crossed $100 billion in annualized revenue for the first time in fiscal 2026. Paid Copilot seats doubled, past 30 million.

Net income was $35.8 billion, up 31%. Diluted EPS was $4.81, up 32%. For the full fiscal year, revenue was $331.8 billion and net income $133.7 billion.

Good numbers, all of them, and nowhere near enough to explain $450 billion. Microsoft was worth close to $2.9 trillion before the move. A slightly-better-than-expected quarter does not buy a 15% single-day gap up.

The actual thing was on another page of the same materials: calendar 2026 capex guidance came down from the roughly $190 billion given in April to about $175 billion.

When Microsoft put out that $190 billion figure in April, the explanation attached to it was that memory prices were spiking. Three months later, the company says it doesn’t need to spend that much.

Azure accelerating and capex down $15 billion, in the same report. That combination hasn’t appeared once in two years of AI narrative.

The rule for the past two years was: you announce more spending, the stock goes up, because spending gets read as proof you captured demand. Whoever had the bigger capex number was assumed to have taken the future. Microsoft ran it backwards — it announced less spending and set a record.

More important, Amy Hood said something else on the call: demand still exceeds available supply.

Spending less is not because they can’t sell it.

Put those two sentences together and the meaning changes: it isn’t that demand collapsed so they saved money. It’s that the same demand can now be absorbed with less money.

There’s one more number on the demand side worth pulling out on its own: paid Copilot seats doubled, past 30 million.

That number matters because it’s seats — not monthly actives, not API calls. A seat means somebody paid per head, and most likely on an annual enterprise contract. The prettiest AI numbers of the past two years have been usage numbers: conversations, tokens, daily actives. They grow fast, and they sit several layers away from revenue. Paid seats don’t have those layers.

30 million seats next to $175 billion of guided capex is what gives “spending less” somewhere to land. If Copilot seats were flat, the same sentence — we’re cutting capex — would have read as retreat.

2. Where the $15 Billion Came From

Amy Hood gave two reasons on the call.

One is efficiency gains across the CPU and GPU fleets, getting more out of existing infrastructure. The other is process improvements in bringing new capacity online, shortening the cycle from decision-to-build to ready-to-use.

That’s the kind of answer product managers hate hearing. It isn’t “we shipped a new feature.” It’s “we’re getting more out of the hardware we already bought.”

That April figure of $190 billion says the same thing from the other side. The explanation at the time was spiking memory prices — meaning a meaningful share of that spend wasn’t something Microsoft chose, it was pushed up from upstream. On a cost line you don’t control, a company has two moves: accept the price increase and raise the budget, or squeeze more compute out of every dollar. In April it took the first. In July it delivered the second.

This kind of work is the hardest thing to get resourced anywhere. There’s no demo, no keynote, and it looks bad in an OKR — “improve utilization of existing clusters” reviewed next to “ship the AI assistant” loses almost every time.

That day, the market priced it: a $15 billion cut in spending, against roughly $450 billion in added market value.

I build a few small tools myself, at a scale with no relationship to any of these numbers, but the structure is the same. Whether a feature works after it ships and how much each call costs to run are two separate questions. Most people stop looking once the first one is answered. If the second one goes unanswered, the more successful the product gets, the faster the bill grows.

What Microsoft signaled this quarter is that those two are no longer sequenced as “get it right first, optimize later.” In a category where unit costs are high enough to drag down the income statement, the cost structure is part of the product.

Those three points from 40% to 43% — if they’d been bought with $15 billion more hardware, the market would probably have read it as expensive life support. Getting them while spending $15 billion less is a completely different thing.

3. Part of the Savings Was Done by the Accountants

That isn’t the whole story.

The same materials contained another move: starting in fiscal 2027, Microsoft is extending the depreciation life of data centers and office buildings from 15 years to 25 years, and reclassifying new data center leases from finance leases to operating leases.

That’s an accounting change, not an efficiency gain.

The same servers, the same building, depreciated over 25 years instead, means a smaller charge hitting cost each year and a better-looking income statement. Moving leases from finance to operating also changes how they show up on the balance sheet and the cash flow statement. The roughly $175 billion figure is the number after this change in treatment.

Blending this with the previous section turns the whole thing into cheerleading. They have to stay separate: one is running the machines fuller, the other is spreading the cost thinner. The market applauded both the same day, but only the first one is product capability.

And the second leaves a real question behind: can a data center actually last 25 years?

GPUs turn over roughly every three years. Cards bought a few years ago are no longer front-line for many training workloads. The 25-year assumption holds only if the buildings, the power and cooling, and the network backbone really do last that long, and the fast-depreciating portion is a small share of total assets.

If the assumption doesn’t hold, the charges were deferred, not erased. By fiscal 2028 and 2029, what has to be written down still gets written down.

I don’t know whether the assumption holds. But a company announcing it spent $15 billion less on the same day it extended asset depreciation by 10 years — those are two things worth remembering separately.

4. At Meta, the Money Went Out and the Cash Flow Went With It

Meta’s results weren’t ugly.

Second-quarter revenue was $60.8 billion, up 28% — well above Microsoft’s 18%. The problem was in the lines below:

That $784 million is what actually broke the stock. A company doing $60.8 billion of revenue a quarter, with $784 million of free cash flow left, means capex ate nearly everything operations earned.

Then management raised full-year 2026 capex guidance to $130–145 billion.

That’s the second consecutive raise. At first-quarter results, Meta lifted its 2026 AI spending expectation to $125–145 billion, and the stock fell that day too. This time the floor went from $125 billion to $130 billion.

Two quarters, the same move, the same reaction. Three months in between, and the market was not persuaded.

Same week, two companies gave opposite answers to the same question. Microsoft said it would spend $15 billion less and added $450 billion. Meta said it would spend more and lost $130 billion.

Six months ago, Meta’s move would most likely have been read as good news — the read then would have been “Zuckerberg is betting big.” This time the read was “the money went in, nothing has come back yet.”

What changed isn’t Meta. It’s the scoring rubric.

5. Microsoft Owns a Piece of OpenAI and a Piece of Anthropic

There’s another set of numbers in this quarter’s results that product managers should look at before the capex line.

Microsoft holds about 27% of OpenAI. In November 2025, it also put $5 billion into Anthropic, and as part of the deal, Anthropic committed to purchase $30 billion of Azure services.

This quarter:

InvestmentThis quarterFull fiscal 2026
Anthropic$3.2 billion gain
OpenAI~$600 million write-down (dragging EPS by ~7 cents)$5 billion gain (contributing 67 cents of EPS)

The side it bet on for seven years and built up to 27% got written down this quarter. The side it only added at the end of 2025 contributed $3.2 billion.

Look at one quarter and it’s easy to write this up as “the backup saved the lead.” Look at the full year and the OpenAI stake contributed $5 billion of gains and 67 cents of EPS in fiscal 2026 — still the larger number by an order of magnitude. A single quarter’s write-down is volatility, not a verdict.

The thing worth looking at isn’t which bet paid better. It’s the structure itself.

$5 billion bought back a $30 billion Azure purchase commitment. The other side of that “investment” is customer acquisition — Microsoft bought not just a stake in Anthropic but a cloud order of known size. Financially it’s an investment. In product terms it’s channel lock-in.

One level up: Microsoft is not betting on which model wins.

It’s a shareholder in both of the leading contenders and the cloud provider to both. OpenAI wins, Microsoft keeps the equity and the compute business. Anthropic wins, Microsoft keeps the equity and the compute business. Whichever breaks out, the traffic runs through Azure.

What I build is as small as it gets, but the logic transfers. When the technical direction hasn’t converged, picking a side is the most expensive move available — get it right and the upside is capped; get it wrong and everything you built on top of it is void. The steadier position is to be a required step on the path: stay out of the question of who wins, and make sure that whoever wins has to come through you.

The cost is giving up the possibility of being the winner yourself. Microsoft is not going to be the company that builds the strongest model, and it has already conceded that by its actions. It picked a different position.

6. “How Much We’re Spending on AI” Is No Longer a Selling Point

Line up the day’s events:

For two years, “how much we’re spending on AI” was a marketing line. After that day, it became a number that requires an explanation.

For people building products, that shift isn’t bad news. It means the work that gets resourced next won’t only be the new features with a story attached. It also includes the things with no demo: getting inference costs down, getting cache hit rates up, scheduling idle compute out to something useful, changing how often a feature calls the model in the first place.

That work used to be nearly impossible to prioritize. Its value just got publicly priced for the first time.

As for the 25-year depreciation question, the answer arrives in fiscal 2028 and 2029. If those buildings and power systems really do last that long, today’s math was honest. If they don’t, the deferred portion still comes due in some year.

What I’d rather know is next quarter. The 45% Azure guide was given on the premise that demand exceeds supply — and supply is exactly what’s being held up by spending $15 billion less. How long both of those hold at once is the real test of whether this repricing stands.

Discussion

No login needed. Be kind.
Loading…