Microsoft's Azure Business Just Grew 48% in a Quarter — Here's What the Numbers Actually Show

Table of Contents

• The headline numbers
• Quick glossary before you read further
• The capex number that's easy to miss
• What this doesn't tell you
• Where Azure sits against the rest of the cloud market
• Why this matters if you're learning cloud infrastructure
• The honest caveat

Microsoft reported its fiscal Q1 2027 earnings on October 28, 2026 — the quarter covering July through September 2026 — and the headline number that got repeated everywhere was Azure's 48% growth. That's a big figure, and it's real, straight from Microsoft's own investor relations release. But a growth percentage by itself doesn't tell you much without the base it's growing from, or what's actually behind it. Here's what the filing says, and what it doesn't.

The headline numbers

Total Microsoft revenue for the quarter came in at $92.3 billion, up 19% year-over-year (19% in constant currency, so currency swings weren't propping up the growth rate). Within that, Microsoft Cloud revenue — which bundles Azure with Microsoft 365 Commercial Cloud, Dynamics 365, and other cloud lines — was $63.9 billion, up 30% (31% constant currency).

Azure itself, reported separately, pulled in $33.165 billion against $22.384 billion in the same quarter a year earlier. That's where the 48% constant-currency growth figure comes from — and because Microsoft reported zero currency impact on that line this quarter, the as-reported and constant-currency numbers are the same.

Profitability moved too: GAAP net income was $36.629 billion, up 32% (33% constant currency), and GAAP diluted EPS was $4.92, also up 32%. On a non-GAAP basis — which strips out a $207 million net gain tied to Microsoft's OpenAI investment — net income was $36.422 billion (up 18%) and EPS was $4.89 (up 18%). The gap between the GAAP and non-GAAP growth rates is almost entirely that one-time investment gain, which is worth knowing before quoting either number without context.

Operating income was $45.915 billion, up 21% (22% constant currency). Cash from operations came in at $58.0 billion.

Quick glossary before you read further

A few terms in this release do a lot of work, and it's easy to skim past them without knowing exactly what they mean:

Constant currency strips out the effect of exchange-rate movements so you can see growth driven by actual business activity rather than the dollar getting stronger or weaker against other currencies. When a company reports the same percentage for "as reported" and "constant currency," like Azure's 48% this quarter, it means currency had no measurable effect on that particular line.

GAAP vs. non-GAAP is the difference between Microsoft's results calculated under standard US accounting rules (GAAP) and a version that excludes specific one-off items — in this case, a $207 million gain tied to Microsoft's investment in OpenAI. Companies report both because GAAP is the legally required figure, while non-GAAP is meant to show what the "core" business did without a one-time event skewing the comparison.

Commercial remaining performance obligation (RPO) is the dollar value of contracts customers have already signed but which Microsoft hasn't yet delivered and booked as revenue — essentially a backlog. A growing RPO suggests demand is outpacing what's currently being recognized on the income statement.

Capex (capital expenditure) is money spent on physical assets — in Microsoft's case, overwhelmingly data centers, servers, and networking equipment — rather than day-to-day operating costs. It shows up on the cash flow statement, not the income statement, which is part of why it's easy to miss in a press release that leads with revenue and EPS.

The capex number that's easy to miss

Buried in the cash flow statement, not the headline release copy, is this: Microsoft spent $39.367 billion on "additions to property and equipment" this quarter, against $19.394 billion in the same quarter last year. That's more than double, in a single quarter, on data center and infrastructure buildout — which is the physical cost of the AI and cloud capacity that's supposed to keep feeding Azure's growth.

Microsoft's release doesn't break that capex figure down by category, and it doesn't include forward guidance for the rest of fiscal 2027 — that detail, if Microsoft gives it at all, comes out on the earnings call and in a separate "Outlook" filing, not the press release itself. So anyone citing a specific full-year capex target for Microsoft right now is quoting something beyond what the primary release actually says, and it's worth checking the source before repeating a number like that.

It's worth sitting with the scale of that number for a second: $39.4 billion is more than many entire national IT budgets, spent by one company in three months, mostly on physical infrastructure that someone eventually has to design, provision, secure, and operate. That operational layer — not the capex line item itself — is where the job demand downstream of a number like this actually shows up.

What this doesn't tell you

The release reports commercial remaining performance obligation at $677 billion, up 73% year-over-year. That's a genuinely large number, and a 73% jump in backlog suggests customers are locking in multi-year commitments faster than Microsoft is currently able to deliver and recognize as revenue. But the release doesn't say how much of that backlog is Azure specifically versus the rest of Microsoft Cloud, and it doesn't say how much of Azure's 48% growth is net-new AI workloads versus organic growth in ordinary cloud migration and VM/database usage that has nothing to do with AI. Both of those are the kind of detail that gets argued over on the earnings call, not settled in the press release, so treat any confident breakdown you see elsewhere with some skepticism until Microsoft itself publishes one.

Where Azure sits against the rest of the cloud market

It's tempting to immediately line Azure's 48% up against Amazon's AWS and Google's Google Cloud and declare a winner. This article is deliberately not doing that. Every "AWS Q3 2026" figure available at the time of writing turned out, on closer verification, to be the prior year's (2025) results being recirculated under 2026-dated headlines — so there isn't a reliably verified, same-quarter AWS number to compare against right now. Making a competitive claim on top of a mismatched quarter would turn one solid, well-sourced number into a misleading comparison, which defeats the point of citing a primary source in the first place.

What can be said honestly: Microsoft's own release doesn't position Azure against any competitor by name or percentage, and any comparison you see elsewhere is layering on an outside analyst's framing, not Microsoft's own disclosure. If you want a genuine growth-rate comparison across the three major cloud providers, it needs to come from each company's own same-quarter release, checked individually — not from a single secondhand roundup.

Why this matters if you're learning cloud infrastructure

Numbers like a 48% growth rate are easy to read as pure hype, but they map onto something concrete: more organizations are running more of their actual infrastructure — virtual machines, databases, identity and access management, networking, container orchestration — on Azure than they were a year ago. That's a growing base of real environments that need people who can configure, secure, and troubleshoot them, which is a different skill set from the headline percentage itself.

That growth also tracks fairly closely with where entry-level and mid-level cloud hiring tends to concentrate: roles built around Azure administration, cloud networking, identity management, and increasingly DevOps-style deployment pipelines running on top of Azure infrastructure. Certification paths like Azure Fundamentals, Azure Administrator, and Azure Solutions Architect map almost directly onto the skill areas this quarter's revenue growth is funded by — compute, storage, identity, and the operational tooling that keeps all of it running once a company has actually migrated.

Innovative Academy's Azure Training program in Bangalore covers the core service areas behind that backlog figure: virtual machines and App Services, Azure Active Directory and identity management, storage accounts, virtual networking, and the monitoring and cost-management tooling that organizations need once they're running production workloads rather than just a pilot project. The program is built around the kind of day-to-day administration work that doesn't show up in an earnings headline but is exactly what keeps a growing Azure footprint running reliably. Contact for course details: 8447712333.

The honest caveat

None of this is a prediction about where Azure's growth rate goes next quarter, and a single quarter of accelerating cloud revenue doesn't tell you anything about Microsoft's AI monetization story in isolation — that's a much longer argument that this one release doesn't settle either way. What's verifiable right now is what's in the filing: the revenue figures, the growth percentages, and the capex jump. Anything built on top of that — forward guidance, competitive share shifts versus AWS or Google Cloud, or how much of the growth is AI-specific — is a separate claim that needs its own sourcing, and this article has deliberately stopped short of making those claims.