Microsoft's FY2026 Q3 earnings call on April 29 disclosed $31.9 billion of capital expenditures for the quarter — below the $34.9 billion FactSet consensus. CFO Amy Hood then guided FY2026 full-year capex to "roughly $190 billion," approximately $55 billion above the prior consensus near $135 billion. [1] [2] Q4 capex is guided to "more than $40 billion." Hood attributed roughly $25 billion of the upward revision to "higher component pricing." [3] The stock fell 5% in after-hours trading. The disclosure architecture is the second-order question.

A $55 billion change in projected annual capital expenditures is, by any reasonable interpretation of materiality, the kind of fact a public company is required to report promptly. Item 2.06 of Form 8-K — material impairments — does not directly cover capex revisions. Item 8.01 — "other events" — covers material events the registrant chooses to disclose at its discretion. The narrower question, which has SEC staff attention but no published guidance, is whether a 61% one-quarter increase in projected FY capex is a material event under Item 1.01 (entry into a material agreement) when the underlying agreements are component-supply contracts whose terms are not disclosed. Microsoft has not filed an 8-K on the FY26 capex revision. The disclosure was made in the Q3 10-Q script and the prepared remarks. [3]

The 8-K-versus-10-Q question is not academic. The Microsoft, Meta, Google, and Amazon "Big Four" combined are now guiding to between $695 and $725 billion of 2026 capex, against a 2025 base of approximately $360 billion. [1] The aggregate revision in the past two quarters exceeds the GDP of the Netherlands. None of the four has filed a stand-alone 8-K on the year-on-year change.

A 61% one-year capex revision — driven by component-pricing inflation Microsoft itself characterized as a $25 billion impact — is the kind of change reasonable investors would consider in pricing the security. Reasonable-investor materiality is the SEC's standard for Item 8.01 disclosure. Whether Microsoft's disclosure architecture meets the standard is a question staff has not yet resolved publicly.

If the SEC issues interpretive guidance — a no-action letter, a Compliance & Disclosure Interpretation, or a public statement — that hyperscaler AI-capex revisions of more than 25% warrant an 8-K, the disclosure regime for the entire AI-infrastructure cycle changes. The negotiation leverage NVIDIA, TSMC, and SK Hynix have over the hyperscalers becomes, in effect, public information.

The component-pricing line itself is the cipher. Industry analysis points to high-bandwidth memory as the dominant driver, with HBM3E spot pricing up roughly 35% in the past two quarters and HBM4 supply tight through 2026. [1] [2] Two-thirds of Q3 capex went to "short-lived assets," primarily GPUs and CPUs. [3] The disclosure language is the same the company has used for three quarters. The number under it has grown 61%.

Meta raised FY26 capex guidance from $115-135 billion to $125-145 billion. Google raised from $180 billion to $180-190 billion. [1] [4] All four hyperscalers raised in the same window. None has filed an 8-K specifically on the revision.

The question for the next four weeks is whether the SEC's filing review process produces a comment letter on the Microsoft Q3 10-Q. Comment letters are public after the company responds. A comment letter that asks the company to expand its disclosure of the capex revision — or, alternatively, that asks why an 8-K was not filed — would be the regulatory data point that informs the architecture question for the rest of the cycle. The Q3 10-Q was filed Wednesday. The first staff review window typically runs three to six weeks. Mid-June is when the answer arrives.

Until then, the question sits where Microsoft put it: in the prepared remarks, not in an event filing.

-- THEO KAPLAN, San Francisco