Azure’s $33.2 Billion Quarter: What Microsoft’s First Dollar Disclosure Changes in the Cloud Race

Cloud has long been a game of partial information. Amazon reports AWS revenue in dollars. Alphabet reports Google Cloud in dollars. Microsoft, until this quarter, reported Azure growth as a percentage and folded its revenue into broader buckets like “Intelligent Cloud.” That asymmetry made direct comparison awkward and left room for argument about who was really ahead. On October 28, 2026, Microsoft closed the gap.

The headline numbers

Microsoft’s first-quarter results, covered by TechCrunch, GeekWire, Reuters and Bloomberg within hours, contained several figures worth keeping in one place:

• Azure revenue: $33.2 billion for the quarter ended September 30, 2026, up 48% year over year, ahead of the 44–45% growth the company had previously guided.
• Total revenue: $92.3 billion, up 19%. Azure therefore represents roughly 36% of the company’s revenue.
• Microsoft Cloud revenue: $63.9 billion, up 30%.
• New segments: The company reorganized reporting into Agents and Infra, which includes Azure and generated $76.8 billion (up 25%), and Devices and Consumer, which declined 3%.
• Commercial remaining performance obligation: up 73% to $677 billion.
• Capital expenditures and finance leases: about $45.2 billion, below the roughly $50 billion the company had projected, partly because of delivery delays.
• Free cash flow: $18.6 billion.
• Guidance: second-quarter Azure growth of 49% to 50% in constant currency and total revenue of $96 billion to $97.1 billion.

Why the dollar disclosure matters more than the growth rate

Growth rates flatter small bases and punish large ones. A 48% rate on a base this size is remarkable, but a percentage alone does not tell you whether a cloud is a quarter of its rival’s size or a match for it. Dollars do. Amazon’s most recent quarter put AWS at an annualized run rate of roughly $184 billion, while Azure’s $33.2 billion quarter annualizes to a figure in the neighborhood of $130 billion. Treat that comparison with care: Microsoft’s definition of Azure and Amazon’s definition of AWS are not identical, and annualizing a single quarter ignores seasonality. But the order of magnitude is now visible in a way it was not before.

The Reuters framing on the day was that Microsoft’s cloud growth and cash flow offered “respite from AI spending fears.” That phrasing captures the real market question. Investors are not asking whether AI demand exists. They are asking whether the capital being poured into it earns an acceptable return, and how quickly. Microsoft’s answer this quarter was a combination of faster-than-guided revenue growth, a huge contracted backlog, and spending that came in under plan.

What the trend and coverage data show

Google’s U.S. daily trending list on October 31 is led by sports and entertainment queries, not cloud earnings, so there is no search-volume spike for Azure to point to. The more informative signal is the editorial one: the same week’s headlines paired Microsoft with Alphabet (“Alphabet vs. Microsoft earnings: why investors see their AI spending differently,” from Fierce Network; “Alphabet, Microsoft earnings reveal surging AI demand as spending soars,” from Fox Business) and later with Amazon. The story the press is telling is a comparison story, and the dollar disclosure gives that comparison its missing number.

For anyone building content or analysis around this topic, the underlying search intent is practical: How big is Azure? How does it compare with AWS? Should we change our cloud strategy? This article takes those questions in order.

The backlog is the number to watch

Revenue tells you what customers bought last quarter. Remaining performance obligation tells you what they have committed to buy. A 73% jump in commercial RPO to $677 billion means the contracted pipeline is growing faster than the revenue it will eventually become. It is the most forward-looking figure in the release.

It also needs context. A backlog is a promise, not cash. Large AI commitments can be concentrated in a small number of customers, can stretch over many years, and can be renegotiated if the economics of AI deployment change. Strong RPO supports the view that demand is real; it does not remove the risk that a few large counterparties account for a big share of it.

Capex that came in light: good news or a warning?

Microsoft spent about $45.2 billion on capital expenditures and finance leases in the quarter, against prior guidance of roughly $50 billion. Management attributed part of the gap to delivery delays, noting that third-party supply constraints had pushed back some capacity additions. Read that two ways.

• The optimistic read: Microsoft is not overbuilding. It is spending as fast as suppliers allow, and free cash flow of $18.6 billion shows the business can fund growth.
• The cautious read: Demand is outrunning supply of chips, power and construction. Delays mean customers waiting for capacity, and revenue that could have been recognized sooner is deferred.

Both can be true. For buyers, the second read matters most. If a vendor cannot deliver capacity on schedule, your project plan inherits the delay.

How Azure’s numbers compare with its peers

Microsoft is not alone in reporting strength alongside huge spending. In our own coverage of Amazon’s results, AWS grew 39.3%, its fastest pace in nearly five years, while trailing free cash flow turned to a $42.4 billion outflow on roughly $77 billion of quarterly property-and-equipment spending. Market reaction diverged: Reuters described Amazon as sinking as AI spending eclipsed its cloud growth, while Microsoft’s cash generation was framed as reassuring.

That divergence is the heart of the investor debate. Same industry, same demand, different balance sheets and different cash profiles. Microsoft’s quarter combined faster growth with positive free cash flow; Amazon’s combined faster growth with a large trailing outflow. The market is not rewarding growth alone. It is rewarding growth that visibly funds itself.

What the new reporting structure means

The reorganization into Agents and Infra and Devices and Consumer deserves attention. Naming a segment “Agents and Infra” is a strategic statement: Microsoft wants to be judged on infrastructure and AI agents together, not on legacy product lines. It also makes year-over-year comparisons harder for analysts accustomed to the old categories, since the new segments combine pieces of previous ones.

One open question is whether Microsoft will keep disclosing Azure in dollars. A company that starts publishing a number is under pressure to keep publishing it, and a reversion to percentages-only would be noticed. Watch the next two quarters.

A practical playbook for technology teams

1. Re-benchmark your multi-cloud model

If your concentration limits or board materials describe Azure’s scale qualitatively, update them with the disclosed figure. Pair it with AWS and Google Cloud’s reported dollars, using consistent periods and a note about definitional differences.

2. Audit commitments and coverage

Check whether reserved instances, savings plans and committed-spend agreements still match expected consumption. Growth at this pace can tempt teams to over-commit; delivery delays can leave them under-supplied. The right answer depends on your own utilization data.

3. Ask about capacity, not just price

Because management acknowledged supply-driven delays, ask directly about timelines for GPU clusters and regional expansion. Get dates in writing where the project depends on them, and build contingency into your roadmap.

4. Watch vendor financial health

Microsoft also announced a $25 billion bond issuance around the same time to help fund infrastructure. Large issuance is normal for a company of this scale, but it is a reminder that the AI build-out is being financed with a mix of cash flow and debt across the industry. Procurement and finance teams should track it as part of vendor-risk reviews.

5. Model the interest-rate backdrop

The cost of financing this buildout depends on rates. The Federal Reserve held at 3.75%–4.00% on October 28 with two dissenters favoring a hike; our finance note on the decision covers the implications. Higher-for-longer rates raise the bar for projects with long payback periods, including AI infrastructure.

What could go wrong

A balanced read includes the risks. Supply constraints may persist and delay revenue recognition. Backlog concentration could create exposure to a handful of customers. Power availability and permitting could become binding limits. And if AI revenue per dollar of capex disappoints, the market’s patience with heavy spending could shrink quickly, as the reaction to peers shows. None of that is visible in a strong quarter, but all of it is relevant to a multi-year contract.

Key takeaways

• Azure generated $33.2 billion in the September quarter, up 48%, and Microsoft disclosed the dollar figure for the first time.
• Commercial RPO rose 73% to $677 billion, a strong forward indicator but not the same as cash.
• Capex of $45.2 billion came in below the roughly $50 billion plan, partly due to delivery delays, while free cash flow was $18.6 billion.
• Management guided Azure growth of 49%–50% in constant currency for the next quarter.
• The market is separating growth that funds itself from growth that needs debt, which is why Microsoft and Amazon were received differently.

Frequently asked questions

How much revenue did Azure generate?

$33.2 billion for the quarter ended September 30, 2026, up 48% from a year earlier.

Is Azure bigger than AWS?

Not on the figures reported this season. AWS posted an annualized run rate of about $184 billion, while Azure’s quarter annualizes to roughly $130 billion, though definitions differ and a single quarter is a rough guide.

What is remaining performance obligation?

It is contracted revenue not yet recognized. Microsoft’s commercial figure rose 73% to $677 billion.

Why did capex come in under guidance?

Management cited delivery delays tied to third-party supply constraints.

What is Microsoft’s next-quarter guidance for Azure?

Growth of 49% to 50% in constant currency, with total revenue of $96 billion to $97.1 billion.

Sources and further reading

• Microsoft, “Microsoft announces first quarter results,” October 28, 2026
• Reuters, GeekWire, TechCrunch and Bloomberg coverage of Microsoft’s first-quarter results, October 28–29, 2026
• Fierce Network and Fox Business comparisons of Alphabet and Microsoft earnings, October 29, 2026
• Google Trends daily trending searches (U.S.), October 31, 2026

This article is for general information and analysis, not investment or procurement advice. Figures are from the sources above as of October 31, 2026.