Microsoft

Last updated: 2026-10-21 · Author: Claude (claude-fable-5-1 subagent) · Status: reviewed · Reviewer: Codex (gpt-6-astra) cross-check, applied 2026-10-17 · Updated 2026-10-21 from signals/2026-10-21.md

Summary

• Microsoft is a major hyperscaler and OpenAI's primary cloud partner. In fiscal 2026 (ended 30 June 2026), capital expenditure including finance leases totalled $145.3 billion, up 65% from $88.2 billion, against operating cash flow of $182.9 billion. Cash PP&E was $115.9 billion and free cash flow $67.0 billion, down from $71.6 billion despite net income rising 31% to $133.7 billion (claims 1-5).
• Cash PP&E consumed 63% of operating cash flow, versus 38% in FY2024. After cash PP&E, finance-lease principal and gross cash shareholder distributions, $15.170 billion remained; subtracting $19.861 billion of other investing gives an illustrative negative $4.691 billion residual. Finance-lease liabilities ended at $66.594 billion, up $20.422 billion. The filing reports $743.821 billion of contractual obligations, including $443.506 billion of lease payments encompassing $329.1 billion of uncommenced leases; these are overlapping measures, not amounts to add together (claims 10-13, 41-43).
• Primary demand disclosures include FY2026 Azure revenue above $100 billion (+41%), June-quarter Azure and other cloud services growth of 43%, September-quarter guidance of about 45% in constant currency, more than 30 million paid Microsoft 365 Copilot seats, and a March 2026 AI-business annual run-rate of $37 billion (+123% year over year). Management reported capacity constraints in the selected calls cited here. Nearly 90% of FY2026 Microsoft Cloud revenue came from customers outside frontier model companies; this is revenue mix, not backlog mix or a non-AI share (claims 14-17, 35, 46).
• OpenAI concentration is material: approximately 45% of December 2025 commercial RPO of $625 billion implies about $281.25 billion; the June OpenAI balance is undisclosed, and a 41.48% June share is only an unchanged-balance scenario. FY2026 OpenAI revenue including revenue share was $24.1 billion (7.3% of total), with $6.0 billion receivable. Microsoft held about 25% as-converted at June 2026 and had funded $11.9 billion of its $13.0 billion commitment. December's approximately $10.0 billion was a net investment gain, primarily reflecting recapitalization, rather than a separately measured gross dilution gain (claims 19-24).
• The October 2025 agreement added a $250 billion Azure purchase commitment and removed Microsoft's compute right of first refusal. April 2026 broadened OpenAI's cloud freedom and made Microsoft's IP license non-exclusive through 2032, while ending Microsoft's outgoing revenue share and preserving capped payments from OpenAI through 2030 independent of AGI progress. April announced no fresh incremental Azure commitment. On October 21, OpenAI models entered Google Cloud private preview with Codex integration and purchases eligible against existing GCP commitments; Microsoft remains the primary cloud partner. This adds distribution competition, without disclosed incremental revenue or financing (claims 26-27, 56).
• Neocloud supply includes Nebius ($17.4-19.4 billion over five years), IREN ($9.7 billion over five years), Nscale (about 200,000 GB300 GPUs; primary dollar value undisclosed), and Lambda (a company-confirmed multibillion-dollar, multiyear deal; exact value undisclosed). Microsoft accounted for 67% of CoreWeave's 2025 revenue. Microsoft's filing discloses aggregate purchase and construction commitments without allocating them by named supplier (claims 29-33, 41, 48).
• The FY2027 building-life change from 15 to 25 years shifts more future datacenter leases from finance to operating classification, reducing reported calendar-2026 capex guidance from about $190 billion to about $175 billion with minimal operating-income benefit. It reduces comparability of finance-inclusive capex; economic payments and operating-lease liabilities remain reported (claims 7-8).
• The central uncertainty is how OpenAI's payment capacity, replacement customers and contract recoveries compare with Microsoft's infrastructure obligations. December's derived backlog balance is not a current exposure estimate. OpenAI's March announcement of $122 billion of committed capital and an undrawn $4.7 billion revolver supports financing capacity, but does not establish current unrestricted liquidity or funding for all supplier obligations (claims 20-21, 47).

Key claims

Type: primary / secondary / tertiary. Grade: A–D (see report/methodology.md).

Analysis

What Microsoft is in the stack

Microsoft sells AI three ways: raw Azure capacity to model builders (OpenAI above all, now also Anthropic), Azure AI services to enterprises, and AI features inside its own software (Microsoft 365 Copilot, GitHub Copilot). It also owns about a quarter of OpenAI and collects a revenue share from it. This combines broad software and cloud distribution with material exposure to one private counterparty; the evidence here does not establish a peer ranking for either advantage or concentration.

Profitability and cash generation

FY2026 revenue grew 18% to $331.8 billion, operating income 21% to $155.2 billion, and operating cash flow 34% to $182.9 billion (claims 1-2). Annual Azure revenue exceeded $100 billion (+41%); the quarterly Azure and other cloud services KPI grew 43% in June, with about 45% constant-currency growth guided for September (claim 14). Paid Microsoft 365 Copilot seats more than doubled in six months to over 30 million (claim 17). The AI-business annual revenue run-rate rose from $13 billion in December 2024 to $37 billion in March 2026, nearly tripling over 15 months, not one year; the separately disclosed 123% is year-over-year growth, and a run-rate is not annual realized revenue (claim 16). AI contributed 16 of 33 Azure growth points in March 2025, about half the growth in percentage-point terms, not half of Azure revenue. Later acceleration does not establish AI's share of incremental revenue (claim 15).

Microsoft Cloud gross margin fell to 66% for the year and 65% in June, with AI infrastructure investment among the stated drivers (claim 18). Depreciation rose 56% to $34.3 billion (claim 9), and finance-lease interest expense reached $2.5 billion (10-K, Note 13). Free cash flow was $67.0 billion on $133.7 billion of net income, 50% cash conversion versus 84% in FY2024 (claims 1-4). The FY2026 OpenAI investment impact increased net income by $4.963 billion after tax; removing it gives $128.786 billion. Anthropic's $3.2 billion Q4 gain is pretax other income, not an additional $3.2 billion of after-tax net income (claims 24, 34).

Is the build funded by cash flow?

The narrow cash calculation has positive headroom, but it omits material investing uses. Operating cash flow exceeded cash PP&E, finance-lease principal, cash dividends and gross cash share repurchases by $15.170 billion. The $22.271 billion repurchase line includes employee tax-withholding settlements; discretionary program repurchases were $16.7 billion (claims 13, 43). Other investing used $19.861 billion, with its year-over-year increase primarily associated with facilitating component purchases. Subtracting all of it gives an illustrative negative $4.691 billion residual, not a new standardized FCF measure or proof every dollar is AI capex. PP&E remaining in accounts payable rose from $6.9 billion to $26.7 billion, adding supplier-financing and payment-timing exposure beyond cash PP&E (claims 42-43).

Investment purchases of $58.351 billion were offset by maturities of $34.605 billion and sales of $21.798 billion: net purchases were $1.948 billion, not a $58 billion net drain. The full cash-equivalents bridge is $182.935 billion operating inflow minus $139.500 billion investing outflow, $52.546 billion financing outflow and $0.196 billion exchange-rate effects, a $9.307 billion fall. Short-term investments fell another $8.415 billion, reconciling the $17.722 billion decline in combined cash and short-term investments (claim 43; 10-K cash flows and balance sheet). Debt carrying value was $40.294 billion, without new FY2026 issuance, but recognized financing also includes $66.594 billion of finance leases and $21.925 billion of operating leases (claims 10, 12). Cash PP&E/OCF rose from 38% to 47% to 63% across FY2024-26.

Finance-inclusive capex totalled $145.3 billion, $29.352 billion above cash PP&E; lease additions and payment timing both contribute to the difference (claims 3, 5; Q1 FY26 call). The June quarter reached $41 billion, with September guidance above $50 billion already incorporating the lease reclassification (claim 7). Applying half FY2026's 64.74% growth rate gives a FY2027 scenario of approximately $192.3 billion, not cash-capex guidance (claim 55). Reclassification and payment timing prevent translating it directly into FCF. Microsoft guides positive FY2027 FCF without an amount (claim 39). A financing-gap forecast needs assumptions for cash PP&E, lease principal, other investing, taxes and shareholder returns; borrowing is one possible response, alongside cash reserves or changing repurchases, rather than an arithmetic necessity. Calendar-2026's $175 billion guidance is a separate period and basis.

September's dividend increase also matters to such scenarios: $0.98 quarterly at an unchanged 7.427 billion shares implies a $29.114 billion annual cash run-rate, rather than simply reusing FY2026's $26.445 billion paid. This is an illustration, not a forecast of actual FY2027 dividends (claims 13, 54).

The off-balance-sheet build

Uncommenced leases were $329.1 billion at June 2026, primarily datacenters, with starts in FY2027-FY2033 and terms of 1-20 years (claim 11). The balance rose $236.4 billion over twelve months and $132.5 billion from March: more than tripled year over year. These are net balance changes, not gross new contracts. The commitments are not current-year capex or recognized present-value debt, and some arrangements depend on contractual conditions being met. Recognized finance-lease liabilities were $66.594 billion, up $20.422 billion, with $89.686 billion of undiscounted payments (claim 10). Adding liabilities to undiscounted commitments would mix measurement bases.

The filing directly reports $443.506 billion of operating and finance lease payments including interest, encompassing both commenced and uncommenced leases. The $329.1 billion is included, not additional; these leases are primarily, but not wholly, datacenters (claim 41). This is part of $743.821 billion in total contractual obligations, of which $241.922 billion is due in FY2027. These payments overlap future operating costs, investment and leases: the total is neither an amount to add to capex guidance nor a demonstrated financing deficit. Counterparty developers' financing against Microsoft's contracts transmits build risk, but does not remove Microsoft's own contractual obligations.

Extending datacenter and office building lives from 15 to 25 years shifts more future leases to operating classification and lowers reported calendar-2026 capex guidance by about $15 billion, from $190 billion to $175 billion, without an economic spending cut (claims 7-8). Finance-inclusive capex becomes less comparable across periods; cash payments, operating-lease liabilities and the uncommenced-lease disclosure remain visible. The announced FY2027 operating-income benefit is minimal. Two-thirds short-lived assets describes Q4's capex mix, not necessarily the whole year; GPU/server useful lives are unchanged (claims 6, 8-9).

OpenAI: the concentration

The disclosed December 2025 OpenAI share was approximately 45% of $625 billion in commercial RPO, implying about $281.25 billion. The arithmetic complement is $343.75 billion; the CFO described it as roughly $350 billion (claim 20). Total-company RPO movements do not identify OpenAI's starting balance, new bookings or revenue runoff. June's statement that sequential commercial RPO growth came from outside frontier model companies does not bridge December to June or establish that OpenAI's balance stayed unchanged. Retaining December's balance would imply 41.48% of June commercial RPO, but this is a C-grade scenario, not a disclosed share (claim 21). Headline commercial RPO growth of 84%, versus 25% excluding OpenAI, demonstrates a material OpenAI contribution without identifying its current balance (claim 19). Commercial RPO is distinct from the filing's total-company RPO.

FY2026 recognized revenue from OpenAI, including revenue share, was $24.1 billion, or 7.3% of company revenue; $6.0 billion was receivable at June 30 (claim 22). Recognized revenue is not proof of cash collected. The filing does not split Azure consumption from revenue share, and the December-derived RPO amount is not a current receivable.

Microsoft funded $11.9 billion of a $13.0 billion commitment and held about 25% as-converted at June 2026, versus 27% in March; the earlier 32.5% stake description excluded recent funding rounds (claim 23). HLBV equity-method accounting does not simply multiply OpenAI's profit or loss by the ownership percentage. The named FY2024, FY2025 and September-2025-quarter losses sum to $10.4 billion, but comparing them with June 2026 funded capital is not a September investment roll-forward. December's approximately $10.0 billion was a net investment gain, primarily reflecting recapitalization, not a separately established gross dilution gain. The FY2026 net pretax impact was $6.5 billion; the rounded quarterly inputs imply a Q4 residual of about $0.619 billion (claim 24). These disclosures and the CFO's general loss-cap statement (claim 25) do not establish a $20 billion carrying value or precise future loss-recognition capacity; the differing interpretations are recorded below.

The October 2025 agreement added a $250 billion Azure commitment and removed Microsoft's compute right of first refusal, while extending model/product IP rights through 2032 (claim 26). April 2026 broadened any-cloud rights and made that license non-exclusive; Azure-first distribution has the exact exception “unless Microsoft cannot and chooses not to support the necessary capabilities.” April also ended Microsoft's outgoing revenue share and retained capped OpenAI payments through 2030 independent of AGI progress, without announcing a new incremental Azure commitment (claim 27). The approximately 20% revenue-share rate remains reported and unverified (claim 28). The chronology includes both concessions and benefits, rather than evidence that every concession bought new volume.

Exposure if OpenAI cannot pay

A payment failure could impair receivables and investment value, reduce future revenue and backlog, and leave underutilized capacity. FY2026's $24.1 billion recognized revenue is a historical flow; the $6.0 billion receivable is an outstanding asset that may relate to it. These exposures are not additive at face value, and lost revenue is not equal to lost profit. June OpenAI RPO, recoveries, contract damages and capacity redeployment are undisclosed; neither a precise backlog wipeout nor 25% post-default growth follows from the historical ex-OpenAI growth rate (claims 19-24).

The 10-K explicitly warns of underutilization and asset impairment if demand is overestimated (claim 36). Uncommenced leases cannot be assumed cancellable. Management argues that the fleet is fungible and contracted GPU lives and alternative customers support reuse (Q2 FY26 call); Anthropic's $30 billion commitment is one source of demand (claim 34). Nearly 90% of Cloud revenue outside frontier labs is another buffer, without establishing that spare AI capacity can all be redeployed at current prices (claim 46).

OpenAI's March disclosure of $122 billion of committed capital and an undrawn $4.7 billion revolving facility is relevant support for payment capacity, not a verified current unrestricted cash balance or proof all supplier obligations are funded (claim 47). The October revenue report (claim 51) also makes revenue-definition comparability relevant to assessing that capacity. Microsoft's software earnings and broad cloud customers provide buffers, but do not establish a peer ranking or how many years it could carry idle capacity. Microsoft equity holders bear lower cash generation and impaired returns; an OpenAI failure may also impair its receivable and investment. Suppliers and financiers can suffer earlier liquidity or market-value losses, yet Microsoft remains obliged under valid accepted contracts. Loss order depends on delivery, acceptance, termination and recourse terms.

The neocloud layer

Nebius's five-year Vineland agreement is $17.4 billion, up to $19.4 billion with options, with tranche termination rights for late delivery (claim 29). IREN's four Childress tranches total about $9.7 billion over five years; Horizon 1 was accepted in August 2026 (claim 30). Microsoft's prepayments are 20% by tranche, approximately $1.94 billion over the whole contract, not proof that amount is already paid (claim 44). At June 30, only $0.938 billion of IREN's $3.645 billion GPU program had been funded/issued. Its remarketing guarantee is conditional on valid termination and failure to find a qualified replacement customer, and releases as Microsoft accepts tranches. Supplier financing is therefore partly customer-funded, and recourse changes after acceptance; it is not a perpetual blanket parent guarantee (claim 45).

Nscale announced about 200,000 GB300 GPUs and an option on a further Texas phase; its primary contract value is undisclosed, with about $23 billion reported but unverified (claims 31-32). Lambda itself confirms a multibillion-dollar, multiyear agreement, while withholding an exact value (claim 48). Microsoft represented 67% of CoreWeave's 2025 revenue (claim 33). Verified Nebius base plus IREN is $27.1 billion, or $29.1 billion with Nebius options. The reported >$60 billion aggregate is not independently established by those sums or the unverified Nscale amount (claim 32).

Microsoft's FY2026 10-K discloses $194.060 billion of purchase commitments, primarily related to datacenters, including $169.008 billion due in FY2027, alongside $34.566 billion of construction commitments. It does not allocate these totals by named neocloud supplier. Supplier announcements must not be added to these aggregates without checking overlap (claim 41). The obligations table makes funding exposure more tangible than supplier announcements alone, without treating every purchase commitment as a neocloud contract.

Recent developments provide evidence in both directions. On September 22, CoreWeave completed $4.2 billion of 2.875% convertible notes due 2033, including the $0.5 billion option: financing remained available, with added debt and potential dilution; this coupon is not a comparable straight-debt yield (claim 49). On October 15-16, FT coverage reported datacenter/neocloud credit selling (C), but the full original and Yahoo syndication could not be accessed in this verification pass. The Microsoft-leased QTS/Project Excalibur price lead remains D, with no independently verified security-level price or Microsoft default established (claims 52-53).

Capacity constraints versus overcapacity

The selected July/October 2025 and April/July 2026 calls document repeated demand-above-supply statements, with the expected constraint horizon moving out (claim 35). They do not document every quarter since April 2024. The January CFO framing of Azure guidance as allocated capacity supports management's supply-limited interpretation (Q2 FY26 call). Capacity allocation can influence growth, but these statements do not prove profitable end-customer demand at every future price or guarantee a clean turning-point signal.

Finance-inclusive capex grew 65% versus revenue's 18%, and the uncommenced-lease balance more than tripled (claims 1, 5, 11). Rapid commitments and OpenAI-dependent backlog growth warrant scrutiny. Against that, nearly 90% of FY2026 Microsoft Cloud revenue came from customers outside frontier model companies (claim 46); this qualifies a single-customer demand story, but is neither a backlog split nor evidence that 90% is non-AI. On September 21 Microsoft reported its India South Central region live with named enterprise customers, within an existing $20.5 billion India commitment. That is deployment and diversified-demand evidence, not another incremental obligation to add to the filing (claim 50). The combined evidence supports monitoring returns and counterparty funding, rather than treating either persistent shortages or inevitable overbuild as established.

What the stock discounts

On the note's October 16 quote, $529.05 and a $3.93 trillion market capitalization imply approximately 29.5 times trailing earnings and 58.7 times FY2026 FCF under the cash-PP&E definition (claims 4, 37). The reported 26.8 times forward multiple lacks a dated consensus earnings denominator here and remains qualified. FY2026 operating margin was about 46.8% (claim 1). The reported January after-hours decline of about 6% and July gain of 15.5% show price sensitivity around earnings, without isolating the contribution of OpenAI exposure, Azure growth or capex accounting (claim 38).

The FCF multiple alone does not identify the market's assumed OpenAI repayment probability, capex trajectory or future cash flow. Calendar-2026 guidance and a FY2027 capex scenario should not be merged into one market-implied path. Nor does one year's 56% depreciation growth establish continued 50% annual growth. The original note's stronger pricing interpretation and the review's objection are both recorded in Conflicts.

Conflicts and open questions

• OpenAI distribution versus historical exclusivity. October 21's Google Cloud preview implements the broader distribution described in April; the October 2025 Azure-exclusivity terms in claim 26 must not be read as the current channel perimeter. OpenAI still identifies Microsoft as its primary cloud partner. GCP commitment drawdown does not establish new financing, lost Azure revenue or cancellation of existing Azure commitments (claims 27, 56).
• Capex guidance basis. Some coverage labels $175 billion as FY2027; the company's July transcript identifies calendar 2026 and separately guides FY2027 growth from the FY2026 base. The note and cross-check use the calendar reading (claims 7, 39). No quantified full-year FY2027 capex guidance follows from that calendar amount.
• Capex definitions. Management's finance-inclusive capex differs from cash PP&E plus stated finance leases (Q1 FY2026: $34.9 billion versus $19.4 billion plus $11.1 billion). The 10-K's $24.6 billion of finance-lease ROU assets obtained also differs from the $28.1 billion sum of quarterly stated lease amounts. The CSV preserves the reported quarterly measures; payment timing and classification prevent a simple reconciliation.
• Funding pressure and FY2027 borrowing — differing assessments. The original note judged the build internally funded with declining headroom and predicted roughly zero post-distribution cash and necessary debt under continued capex acceleration. The cross-check finds the original funding discussion too narrow because it omitted component-related investing, unpaid PP&E and the obligations schedule, but rejects inevitable borrowing: finance-inclusive capex is not cash PP&E, reclassification changes comparisons, and cash reserves or repurchase changes are alternatives. The revised Analysis retains financing pressure as a risk and labels the FY2027 calculation a C-grade scenario (claims 41-43, 55), without claiming a demonstrated corporate financing deficit.
• OpenAI June RPO — differing interpretations. The original note carried December's derived balance forward to infer about 41% at June, interpreting non-frontier sequential growth as confirmation. The reviewer finds this unjustified: the statement neither bridges December-March nor measures OpenAI runoff, renewals or bookings. Claim 21 retains 41.48% solely as an unchanged-balance scenario (C); the actual June balance remains undisclosed. The original inference of pre-existing OpenAI RPO from total-company backlog movements is not identifiable from those inputs.
• Revenue-share rate and cap. The approximately 20% rate remains reported and unverified; the April total cap and the split of FY2026 revenue between consumption and revenue share are undisclosed (claims 22, 27-28).
• Partnership concessions — differing interpretations. The original note framed October and April together as exclusivity exchanged for volume. The cross-check agrees on reduced exclusivity, but finds that causal packaging overstates the record: the incremental Azure commitment was announced in October, while April announced none and included benefits for Microsoft through ended outgoing payments and AGI-independent capped incoming payments. Both the strategic-concession interpretation and these commercial benefits matter; the revised chronology distinguishes the two announcements (claims 26-27).
• Equity method and loss capacity — differing interpretations. The original note inferred that recapitalization reopened loss-recognition capacity, estimated a $20 billion carrying value and treated subsequent impacts as evidence of renewed exposure. The reviewer says net gains, funded capital and the cited losses do not provide a carrying-value roll-forward or quantify remaining capacity; HLBV results can mix dilution effects and operating losses. A general equity-method mechanism remains plausible, but neither interpretation of the small subsequent net impacts is established by these disclosures (claims 23-25).
• Demand breadth and rankings — differing assessments. The original note called Microsoft best placed on demand evidence and most concentrated on a private counterparty, and said the capacity narrative rested on OpenAI and Anthropic. The cross-check finds the peer rankings unsupported and emphasizes the nearly 90% non-frontier share of Cloud revenue and enterprise deployment evidence (claims 46, 50). Concentrated backlog and diversified realized revenue can coexist; the review does not establish that spare AI capacity will earn adequate returns from alternative customers.
• Default loss and transmission — differing assessments. The original scenario assumed a full OpenAI backlog cancellation, added historical revenue to receivables and incremental consumption, and emphasized supplier-financed capacity. The reviewer rejects the additive loss calculation and fixed loss ordering. Microsoft shareholders bear reduced cash generation and impaired returns; suppliers and lenders can face earlier liquidity or market-price stress, but Microsoft remains liable under valid accepted contracts. Prepayments, acceptance, recoveries and conditional guarantees determine the actual order (claims 22, 44-45). This retains the overbuild/concentration concern without assuming losses automatically pass to suppliers.
• Neocloud totals and disclosure. The original note said the commitments were absent from Microsoft's filings; the review identified the aggregate contractual-obligations table (claim 41), correcting that factual assertion. Named-supplier allocations remain unavailable. Nebius plus IREN is $27.1 billion before options; Lambda's qualitative agreement is now primary-confirmed, while exact Lambda/Nscale values and the >$60 billion aggregate remain unverified (claims 29-32, 48). Do not add supplier announcements to filing totals without overlap checks.
• Valuation — differing interpretations. The original note argued that the stock priced continued Azure acceleration, a $175-200 billion capex path and OpenAI payment, while excluding zero FCF or prolonged rapid depreciation growth. The reviewer finds no reverse valuation or probability-weighted model establishing those market expectations; the range mixes periods and accounting bases. The revised Analysis reports the conditional 58.7 times FCF calculation while retaining the original interpretation here as unproven. The forward P/E's dated consensus denominator is also missing (claim 37).
• Credit evidence and source access. The review records a C-grade FT-reported selloff and a D-grade Microsoft-leased QTS price lead. This pass could fetch the third-party summary, but not the full FT article or Yahoo syndication. Neither the review nor this application verifies the specific security's market price; a dated TRACE/dealer observation is required (claims 52-53). OpenAI's committed financing likewise is not its current cash balance (claim 47).
• “$440 billion wipeout”. Existing press/social claims of this post-January market-cap decline remain unverified (D); the cited evidence supports only an approximately 6% after-hours move, not that larger amount (claim 38).
• Open questions. How much Azure growth and outstanding RPO belongs to OpenAI? What are the lease cancellation rights, revenue-share cap, current OpenAI liquidity, investment carrying value and supplier-specific obligation allocations? October 28 results are the next scheduled earnings update (claim 40); the associated filing may update these exposures but need not answer every question.

Signals to watch

Sources

1. Microsoft Corp, Form 10-K for fiscal year ended 30 June 2026, filed 29 July 2026. Microsoft earnings package, MSFT_FY26Q4_10K.docx (downloaded and verified 2026-10-17); SEC filing URL: https://www.sec.gov/Archives/edgar/data/0000789019/000119312526323660/msft-20260630.htm (SEC fetch unavailable in this application pass).

2. Microsoft Corp, Form 10-K for fiscal year ended 30 June 2025, filed 30 July 2025. https://www.sec.gov/Archives/edgar/data/789019/000095017025100235/msft-20250630.htm (accessed 2026-10-17)

3. Microsoft Corp, Form 10-Q for quarter ended 31 March 2026, filed 29 April 2026. https://www.sec.gov/Archives/edgar/data/789019/000119312526191507/msft-20260331.htm (accessed 2026-10-17)

4. Microsoft Corp, Form 10-Q for quarter ended 31 December 2025, filed 28 January 2026. https://www.sec.gov/Archives/edgar/data/789019/000119312526027207/msft-20251231.htm (accessed 2026-10-17)

5. Microsoft Corp, Form 10-Q for quarter ended 30 September 2025, filed 29 October 2025. https://www.sec.gov/Archives/edgar/data/789019/000119312525256321/msft-20250930.htm (accessed 2026-10-17)

6. Microsoft, FY26 Q4 earnings release, 29 July 2026. https://www.microsoft.com/en-us/investor/earnings/fy-2026-q4/press-release-webcast (accessed 2026-10-17)

7. Microsoft, FY26 Q3 earnings release, 29 April 2026. https://www.microsoft.com/en-us/investor/earnings/fy-2026-q3/press-release-webcast (accessed 2026-10-17)

8. Microsoft, FY26 Q2 earnings release, 28 January 2026. https://www.microsoft.com/en-us/investor/earnings/fy-2026-q2/press-release-webcast (accessed 2026-10-17)

9. Microsoft, FY26 Q1 earnings release, 29 October 2025. https://www.microsoft.com/en-us/investor/earnings/fy-2026-q1/press-release-webcast (accessed 2026-10-17)

10. Microsoft, FY26 Q4 earnings call transcript, 29 July 2026. https://www.microsoft.com/en-us/Investor/events/FY-2026/earnings-fy-2026-q4 (accessed 2026-10-17)

11. Microsoft, FY26 Q3 earnings call transcript, 29 April 2026. https://www.microsoft.com/en-us/Investor/events/FY-2026/earnings-fy-2026-q3 (accessed 2026-10-17)

12. Microsoft, FY26 Q2 earnings call transcript, 28 January 2026. https://www.microsoft.com/en-us/Investor/events/FY-2026/earnings-fy-2026-q2 (accessed 2026-10-17)

13. Microsoft, FY26 Q1 earnings call transcript, 29 October 2025. https://www.microsoft.com/en-us/Investor/events/FY-2026/earnings-fy-2026-q1 (accessed 2026-10-17)

14. Microsoft, FY25 Q4 earnings call transcript, 30 July 2025. https://www.microsoft.com/en-us/Investor/events/FY-2025/earnings-fy-2025-q4 (accessed 2026-10-17)

15. Microsoft, FY25 Q3 earnings call transcript, 30 April 2025. https://www.microsoft.com/en-us/Investor/events/FY-2025/earnings-fy-2025-q3 (accessed 2026-10-17)

16. Microsoft, FY25 Q2 earnings call transcript, 29 January 2025. https://www.microsoft.com/en-us/Investor/events/FY-2025/earnings-fy-2025-q2 (accessed 2026-10-17)

17. Microsoft, FY25 Q1 earnings call transcript, 30 October 2024. https://www.microsoft.com/en-us/Investor/events/FY-2025/earnings-fy-2025-q1 (accessed 2026-10-17)

18. Microsoft, FY24 Q4 earnings call transcript, 30 July 2024. https://www.microsoft.com/en-us/Investor/events/FY-2024/earnings-fy-2024-q4 (accessed 2026-10-17)

19. Microsoft, FY24 Q3 earnings call transcript, 25 April 2024. https://www.microsoft.com/en-us/Investor/events/FY-2024/earnings-fy-2024-q3 (accessed 2026-10-17)

20. Microsoft Official Blog, "The next chapter of the Microsoft–OpenAI partnership", 28 October 2025. https://blogs.microsoft.com/blog/2025/10/28/the-next-chapter-of-the-microsoft-openai-partnership/ (accessed 2026-10-17)

21. Microsoft Official Blog, "The next phase of the Microsoft-OpenAI partnership", 27 April 2026. https://blogs.microsoft.com/blog/2026/04/27/the-next-phase-of-the-microsoft-openai-partnership/ (accessed 2026-10-17)

22. Microsoft Official Blog, "Microsoft, NVIDIA and Anthropic announce strategic partnerships", 18 November 2025. https://blogs.microsoft.com/blog/2025/11/18/microsoft-nvidia-and-anthropic-announce-strategic-partnerships/ (accessed 2026-10-17)

23. Nebius Group N.V., Form 6-K, "Commercial agreement with Microsoft", 8 September 2025. https://www.sec.gov/Archives/edgar/data/1513845/000110465925088312/tm2525580d1_6k.htm (accessed 2026-10-17)

24. IREN Ltd, Form 10-K for fiscal year ended 30 June 2026, filed 27 August 2026. https://www.sec.gov/Archives/edgar/data/1878848/000187884826000052/iren-20260630.htm (accessed 2026-10-17)

25. Nscale, "Nscale contracts approximately 200,000 NVIDIA GB300 GPUs with Microsoft", 15 October 2025. https://www.nscale.com/press-releases/nscale-microsoft-2025 (accessed 2026-10-17)

26. Nscale, Norway expansion with Microsoft, 14 April 2026. https://www.nscale.com/press-releases/nscale-microsoft-norway (accessed 2026-10-17)

27. CoreWeave, Inc., Form 10-K for year ended 31 December 2025, filed 2 March 2026. https://www.sec.gov/Archives/edgar/data/1769628/000176962826000104/crwv-20251231.htm (accessed 2026-10-17)

28. The Register, "Microsoft investors sweat cloud giant's OpenAI exposure", 29 January 2026. https://www.theregister.com/2026/01/29/microsoft_earnings_q2_2026/ (accessed 2026-10-17)

29. CFO Dive, "Microsoft holds line on AI spending plans", July 2026. https://www.cfodive.com/news/microsoft-holds-line-ai-spending-plans/826648/ (accessed 2026-10-17)

30. TIKR, "Did Microsoft really cut its capex?", 2026. https://www.tikr.com/blog/did-microsoft-really-cut-its-capex-heres-the-accounting-move-behind-the-headline (accessed 2026-10-17)

31. PYMNTS, "Microsoft extends data center lifespans to soften AI buildout costs", July 2026. https://www.pymnts.com/earnings/2026/microsoft-extends-data-center-lifespans-to-soften-ai-buildout-costs/ (accessed 2026-10-17)

32. Introl, "Microsoft's $60B neocloud bet", December 2025 (tertiary; cites Bloomberg and company releases). https://introl.com/blog/microsoft-60-billion-neocloud-spending-capacity-crunch-december-2025 (accessed 2026-10-17)

33. StockAnalysis, Microsoft (MSFT) statistics, 16 October 2026 close. https://stockanalysis.com/stocks/msft/ (accessed 2026-10-17)

34. Finviz, "Microsoft announces quarterly earnings release date", 7 October 2026. https://finviz.com/news/400058/microsoft-announces-quarterly-earnings-release-date (accessed 2026-10-17)

35. Om Malik, "What Microsoft's 10-Q says about OpenAI", 1 May 2026 (secondary; revenue-share rate). https://om.co/2026/05/01/what-microsofts-10-q-says-about-openai/ (accessed 2026-10-17)

36. IREN Ltd, December 2025 Form 10-Q, Strategic Customer Agreement. SEC filing (fetched 2026-10-17).

37. Microsoft, FY2026 10-K, MD&A Contractual Obligations/Cash Flows and Notes 6, 13, 15. Company-hosted earnings package (downloaded and figures verified 2026-10-17).

38. Lambda, Microsoft agreement announcement, 3 November 2025. Company release (fetched 2026-10-17).

39. OpenAI, funding announcement, 31 March 2026. Company disclosure (fetched 2026-10-17).

40. CoreWeave, Form 8-K signed 22 September 2026, convertible-note closing. SEC filing (fetched 2026-10-17).

41. Microsoft, India South Central deployment announcement, 21 September 2026. Company release (fetched 2026-10-17).

42. Axios, 8 October 2026. Revenue report (fetched 2026-10-17; reported, unverified).

43. Financial Times, datacenter bond selloff coverage, 15-16 October 2026. Original and indexed syndication (fetch attempted 2026-10-17; inaccessible); HeadlinesBriefing summary (fetched 2026-10-17). Broad report C; specific QTS price lead D.

44. Microsoft, quarterly dividend increase, 15 September 2026. Company release (fetched 2026-10-17).

45. Microsoft Investor Relations, upcoming earnings date. Microsoft IR (fetched 2026-10-17).

46. Codex (gpt-6-astra), independent cross-check, 17 October 2026; findings applied with source verification, differing judgments recorded in Conflicts.

47. OpenAI, OpenAI models are coming to Google Cloud, and Google Cloud, Google Cloud brings OpenAI models to customers, 2026-10-21; both fetched 2026-10-21. The Google post directly confirms private-preview status and commitment drawdown; OpenAI confirms Microsoft's continuing primary-partner status.

48. Microsoft, FY2027 Q1 earnings event, re-fetched 2026-10-21, confirms October 28. July call also re-fetched 2026-10-21: ~$175bn calendar-2026 capex is prior guidance after lease reclassification, without lower physical investment.