Public Cloud Earnings: Is Cloud Revenue Clearing the Hurdle Rate
This board answers four things: whether the three clouds' revenue growth has caught up with the hurdle rate, how much money the AI dividend really is, whether the order book supports today's spending, and when the depreciation pressure arrives.
Read from the map: In progress, still below the hurdle rate
Three-cloud revenue growth
55.7%
3Q26|AWS + Azure + Google Cloud combined, YoY
Four-hyperscaler D&A growth
35.8%
3Q26|The hurdle rate itself; projected at 53 to 55% in 2027
Cloud revenue added in a quarter
$39B
3Q26|Dollars above the same quarter a year ago, the AI dividend
Backlog AWS / Google
$578B / $568B
3Q26|Microsoft's company-wide RPO is a different measure
Next check
2027 hurdle rate for cloud growth ≈ 53–55%; analyst consensus for the three clouds in 2027 is +45% (Sep 30), 8 to 10 points short
Three-cloud revenue growth now 55.7% (3Q26)
How to read this board
Expand
Core view: Combined revenue of the three public clouds grew 55.7% year on year in 3Q26, ahead of the 35.8% growth in depreciation, so it is winning the race for now; but the hurdle rate climbs with depreciation to 53 to 55% in 2027, and today's growth is still short of that. Three things hold the line up: $39B of cloud revenue added in a single quarter (the AI dividend in dollars), backlogs that jumped at all three, and cloud operating margins of 35 to 40%. The worry is depreciation: capex runs at 3 to 6 times depreciation and assets not yet in service are at a record, and today's spending is the depreciation of the next two years.
- Watch the increment, not the installed share: who gets the AI dividend shows up in the share of new revenue, because installed market share moves too slowly.
- Today's capex is the depreciation of the next two years: with capex at 3 to 4 times depreciation, depreciation must accelerate, and only a return to about 1× marks the end of the investment cycle.
- If depreciation keeps growing faster than cloud revenue, margins get squeezed: judge the trend, not a single quarter.
- The three order books are not the same measure (AWS backlog, Microsoft company-wide RPO, Google revenue backlog), so read each one's trend and do not compare levels.
- Server useful life is the lever that moves the hurdle rate directly: extending it lowers depreciation and lowers the bar.
Term: The hurdle rate for cloud growth = the year-on-year growth of the four hyperscalers' combined depreciation and amortization, projected mechanically from capex already spent plus analyst capex estimates at each company's fitted depreciation life, about 53 to 55% in 2027. Cloud revenue growth has to outrun it for margins to hold. The AI dividend = the dollars of cloud revenue added over the same quarter a year earlier, not the percentage.
Question 1Has growth caught up with the hurdle rate
1The growth race: cloud revenue versus depreciation
This is the key chart of the board. The green line is the three clouds’ combined revenue growth, the red line is the four hyperscalers’ combined depreciation growth, and the depreciation line is the hurdle rate. Margins hold only while revenue outruns depreciation; today the green line is on top. But the bar does not stay here: the depreciation projection in group 4 shows depreciation growth climbing to 53 to 55% in 2027, so today’s 55.7% is not yet enough. Read the trend, not a single quarter.
D&A Growth vs Cloud Revenue Growth (YoY, Combined)#
How to read this chart
If depreciation growth stays above cloud revenue growth, margins come under pressure. The dashed line is the mechanically projected hurdle rate, same method as above. Read the trend, not single quarters; there is a model seam where actuals meet the projection.
Source: Company filings and analyst estimates (FinSight compilation and estimates) · Updated 2026-10-30
2Each cloud’s growth rate
The three clouds’ revenue growth on one chart, latest quarter Google Cloud 102.6%, Azure 48.2%, AWS 39.3%. All three are around 40% with Google Cloud jumping to 80%, a steady recovery from the early-2023 trough.
Three Public Clouds: Revenue YoY#
Source: FinSight compilation and estimates · Updated 2026-10-30
3Each company against its own hurdle rate: who has room to beat it
One panel per company: the red line is the company’s own depreciation growth (dashed where projected), the green line is its cloud revenue growth (Meta has no cloud segment, so company-wide revenue is used), and the grey dashed line is the 2027 threshold. The numerator is company-wide depreciation, so the bar is systematically high; the right use is to judge how thick the cushion is and which way it is heading. Google is the only one beating the bar, still ahead even with all company depreciation charged to Google Cloud; Amazon is on the line and one more step up in AWS growth clears it, and its shortened server life makes its bar the most honest; Microsoft has a wide gap but the strictest measure, with Office depreciation in the numerator; Meta’s gap is structural, because its AI returns come through advertising, so faster depreciation presses straight on margins.
Google: GCP growth 102.6% vs 2027 threshold 67.2%#
Source: FinSight compilation and estimates · Updated 2026-10-30
Amazon: AWS growth 39.3% vs 2027 threshold 41.9%#
Source: FinSight compilation and estimates · Updated 2026-10-30
Microsoft: Azure growth 48.2% vs 2027 threshold 60.4%#
Source: FinSight compilation and estimates · Updated 2026-10-30
Meta: company-wide revenue growth 26.1% vs 2027 threshold 65.0%#
Source: FinSight compilation and estimates · Updated 2026-10-30
4Quarterly revenue of the three clouds
AWS at $46B a quarter, Azure $33B, Google Cloud $31B, all three still accelerating. Azure is Microsoft's restated September 2026 definition, excluding GitHub, developer services, Security Copilot and the healthcare cloud; quarters before 3Q24 are estimates projected back from the actuals and drawn dashed. Google Cloud includes TPU system sales from 2Q26, so it is not fully comparable with earlier quarters. The three charts below are each company's revenue bars with its growth line.
Three Public Clouds: Quarterly Revenue ($B)#
How to read this chart
Azure from 3Q24 to 2Q26 is Microsoft's restated actual figure on the new definition (excluding GitHub, developer services, Security Copilot and healthcare cloud). Earlier quarters are estimates, back-cast from the 3Q24 anchor using the growth rates the company disclosed at the time, and drawn dashed.
Source: Company filings and earnings calls; FinSight compilation and estimates · Updated 2026-10-30
Three Public Clouds Combined: Revenue and YoY Growth#
How to read this chart
The three quarterly revenues summed; Azure before 3Q24 is estimated, so the total carries that estimate. YoY is the total against the same quarter a year earlier.
Source: Company filings and earnings calls; FinSight compilation and estimates · Updated 2026-10-30
AWS Revenue and YoY Growth#
How to read this chart
Left axis: quarterly revenue in $B. Right axis: year-over-year growth. The latest quarter is highlighted in orange-red.
Source: Company filings and earnings calls; FinSight compilation · Updated 2026-10-30
Azure Revenue and Disclosed YoY Growth#
How to read this chart
Dark bars are Microsoft's restated actuals from 3Q24 on the new definition; light bars are estimates back-cast from those actuals. The YoY line is the growth rate the company disclosed each quarter: 2Q26 uses the new definition (42%, versus 43% on the old one), and other quarters round to the same number either way.
Source: Company filings and earnings calls; FinSight compilation and estimates · Updated 2026-10-30
Google Cloud Revenue and YoY Growth#
How to read this chart
From 2Q26, revenue includes TPU system sales, so it is not fully comparable with earlier quarters.
Source: Company filings and earnings calls; FinSight compilation · Updated 2026-10-30
Question 2How big the AI dividend is
5The AI dividend in dollars, and who takes it
Left: revenue each cloud added over the same quarter a year earlier. The three combined went from about $6B in 2Q23 to $39B in 3Q26, the most direct revenue evidence that AI investment is paying back. Right: each company's share of the combined increment; installed share moves slowly, so the share of new revenue is what shows competitiveness today. Azure's share is slipping and Google Cloud's is rising, and one reading is that in-house chips are the deciding factor.
Cloud Revenue Added Year Over Year ($B/Quarter): the AI Dividend in Dollars#
How to read this chart
Increment = this quarter's revenue minus the same quarter last year. The combined increment grew from about $6B in 2Q23 to about $31B in 2Q26, the most direct revenue evidence that AI investment is paying off. Azure is an estimated series, so the total differs slightly from outside reports.
Source: Company filings and earnings calls; FinSight compilation and estimates · Updated 2026-10-30
Share of the Growth: Each Company's Cut of the Three Public Clouds' YoY Increment#
How to read this chart
Installed share moves slowly; share of new revenue reflects competitiveness right now. One reading is that in-house chips (TPU, Trainium) are the deciding factor, and Microsoft's lack of a top-tier chip is why its share of the increment is slipping.
Source: Company filings and earnings calls; FinSight compilation and estimates · Updated 2026-10-30
Question 3Do orders and margins hold up
7Backlog not yet recognized, and whether spending is chasing orders
Left: all three backlogs jumped in the latest quarter, AWS $578B, Google $568B, Microsoft's company-wide RPO $683B, mostly long contracts signed by model companies: about 45% of Microsoft's cloud orders are OpenAI-related, OpenAI plus Anthropic are about a third of AWS's, and Google's includes Anthropic. Right: capex divided by backlog; the ratio has been fairly stable historically, so capex is effectively governed by the order book, and a falling ratio means orders are growing faster than spending, leaving room for capex to be revised up. The three measures differ, so read each trend on its own.
Backlog / RPO Not Yet Recognized ($B)#
How to read this chart
Definitions differ: AWS reports backlog, Microsoft reports company-wide remaining performance obligations (RPO), Google reports revenue backlog. Backlog quality in 2Q26: Microsoft $684B, of which cloud is about $625B with roughly 45% OpenAI-related; AWS $496B including $138B over eight years from OpenAI plus $33B-plus cumulative from Anthropic, so model developers are about a third; Google $519B including Anthropic.
Source: SEC filings (10-K, 10-Q); FinSight compilation · Updated 2026-10-30
CapEx ÷ Backlog (%/Quarter): Is Spending Chasing Orders?#
How to read this chart
Historically this ratio has been fairly stable, which you can read as backlog governing CapEx. A falling ratio means orders are growing faster than spending, so CapEx has room to be revised up. Definitions: Microsoft uses company-wide RPO, Amazon uses AWS backlog, Google uses Google backlog. Levels are not comparable across companies; watch each trend on its own.
Source: Company filings and analyst estimates (FinSight compilation and estimates) · Updated 2026-10-30
8Cloud operating margin: buying chips and holding margins at the same time
AWS 38.7%, Microsoft Intelligent Cloud 35.2%, Google Cloud 36.2%, all three between 35 and 40%, with Google Cloud having climbed there from a loss. Microsoft's Intelligent Cloud segment disappears from fiscal 2027, leaving only the dashed Microsoft Cloud gross margin to follow, which is a gross margin rather than an operating margin, so read its direction only.
Cloud Operating Margin#
How to read this chart
Microsoft has two lines. The solid line is Intelligent Cloud operating margin; the segment is discontinued from FY27 Q1, so it stops at 2Q26. The dashed line is Microsoft Cloud gross margin, which Microsoft keeps reporting quarterly, but it is a gross margin rather than an operating margin, so read the trend only and do not rank it against AWS or Google Cloud.
Source: Company filings and earnings calls; FinSight compilation · Updated 2026-10-30
Question 4When the depreciation pressure arrives
9Depreciation and amortization: the echo of past capex
Left: each company's depreciation and amortization, accelerating every quarter. Right: the four combined, dollars plus year-on-year growth; the pale bars and dashed line are a mechanical projection from capex already spent plus analyst estimates at fitted depreciation lives, not company guidance, and the growth rate keeps rising into 2027, which is why the hurdle rate climbs.
Depreciation and Amortization ($B/Quarter)#
Source: FinSight compilation and estimates · Updated 2026-10-30
four hyperscalers Combined D&A: Dollars and a Mechanical YoY Projection#
How to read this chart
Bars are combined D&A; the line is YoY growth. Light bars and dashed lines are a mechanical projection built from CapEx already spent plus analyst CapEx estimates, run through each company's fitted depreciation life; not company guidance.
Source: Company filings and analyst estimates (FinSight compilation and estimates) · Updated 2026-10-30
10Lead indicators: capex ÷ depreciation, and depreciation ÷ cloud revenue
Left: capex as a multiple of depreciation, Google 6.1×, Meta 4.9×, Microsoft 3.8×, Amazon 3.6×; multiples this high mean depreciation must accelerate, and only a return to about 1× marks the end of the investment cycle. Right: company-wide depreciation divided by cloud segment revenue; the numerator includes non-cloud depreciation, so read the trend rather than the level. It is falling, which means cloud monetization is outrunning depreciation, and a turn upward is when to worry.
CapEx ÷ D&A (x) = a Lead Indicator of Future Depreciation Pressure#
How to read this chart
Today's CapEx is the depreciation of the next two years.
Source: FinSight compilation and estimates · Updated 2026-10-30
D&A ÷ Cloud Revenue (Company-Wide D&A ÷ Cloud Segment Revenue)#
How to read this chart
The numerator includes non-cloud depreciation, so read the trend rather than the level.
Source: FinSight compilation and estimates · Updated 2026-10-30
11Assets not yet in service: capital bought but not yet switched on
Left: assets bought but not yet in service, which neither depreciate nor earn, Google $145B, Meta $89B; a record pile means capex is running ahead of the ability to power up and commission. Amazon discloses only annually, Oracle only in its May fiscal year, Microsoft never. Right: the same stock expressed as months of capex parked, like days of inventory, Google about 11 months, Meta about 10; flat means commissioning keeps up with spending, rising means it is falling behind. The third chart is capex efficiency: new annualized cloud revenue per dollar of earlier capex, with 0.33 as the three-year revenue payback line, a pass mark rather than a good one, since it is revenue paid back, not profit.
Assets Not Yet in Service (construction in progress, $B, period-end)#
How to read this chart
Capital bought but not yet in service, which neither depreciates nor earns. A growing pile means CapEx is running ahead of the ability to energize and commission (power, shells, deliveries). Disclosure: Google and Meta quarterly; Amazon annual only; Oracle annual with a May year-end; Microsoft never.
Source: FinSight compilation and estimates · Updated 2026-10-30
Months of CapEx Parked Not Yet in Service = assets not yet in service ÷ trailing four-quarter CapEx × 12 (period-end)#
How to read this chart
Stock divided by flow, read as months of capex parked in the warehouse, like days of inventory. The period-end version uses the quarter-end balance of assets not yet in service; Oracle fell from 8.5 months in fiscal 2025 to 8.1 in fiscal 2026.
Source: FinSight compilation and estimates · Updated 2026-10-30
CapEx Efficiency: New Annualized Cloud Revenue per $1 of Earlier CapEx#
How to read this chart
Trailing-four-quarter incremental cloud revenue divided by trailing-four-quarter CapEx four quarters earlier; Meta has no cloud segment and is excluded. The 0.33 line is a three-year revenue payback, a pass mark rather than excellence: it recovers revenue, not profit, and at roughly 35% cloud operating margin the profit payback is 8 to 9 years, beyond a server's six-year life. Judge by trend and by peers.
Source: FinSight compilation and estimates · Updated 2026-10-30
12Depreciation life policy: the lever that moves the hurdle rate
Who has changed server useful lives, by how much, and what it did to earnings. Extending the life flatters current earnings and pushes the depreciation tail into the future; Amazon is the only one that moved the conservative way, so its hurdle rate is the most honest. What to watch: anyone else shortening AI server lives is admitting GPUs have a shorter economic life, which pushes the whole industry’s hurdle rate up; conversely, another extension by Meta would be a red flag.
Depreciation Useful-Life Policy Tracker (the Lever That Moves the Hurdle Rate)#
| Company | Server useful-life history | Latest change | Earnings impact |
|---|---|---|---|
| MSFT | 3 → 4 years (Jul 2020) → 6 years (Jul 2022) | Extended in 2022 | About +$3.7B operating income in FY23 |
| GOOG | 3 → 4 years (Jan 2021) → 6 years (Jan 2023) | Extended in 2023 | About +$3.9B net income in 2023 |
| AMZN | 3 → 4 (2020) → 5 (2022) → 6 (2024) → ▼ 5 years (Jan 2025) | Shortened in 2025 (the only reversal) | About −$1.3B in 2025 (including early retirements); reason given: faster AI iteration |
| META | → 5 years (Jan 2023) → 5.5 years (Jan 2025) | Extended in 2025 | About −$2.9B of depreciation in 2025 (flattering earnings) |
Source: FinSight compilation and estimates · Updated 2026-10-30
