A joint statement from OpenAI and Microsoft
read at source ↗ openai.com
A joint statement from OpenAI and Microsoft
Source: OpenAI Date: 2025-09-11 URL: https://openai.com/index/joint-statement-from-openai-and-microsoft
Summary
Joint statement from OpenAI and Microsoft published September 11, 2025, the same day as the nonprofit/PBC restructuring statement. The joint statement addressed the terms of OpenAI’s restructuring and its implications for the Microsoft partnership — specifically how Microsoft’s equity stake, licensing rights, and commercial terms would be maintained or modified under the PBC structure. Microsoft had invested $13B+ in OpenAI through 2024 and had significant contractual rights; the restructuring required renegotiating or affirming those terms.
Implications
The Microsoft relationship as the central dependency. Microsoft’s Azure hosting of OpenAI models, its integration into Microsoft 365 Copilot, and its exclusive cloud provider status were the most consequential commercial relationships for OpenAI’s growth. The joint statement was necessary to assure Microsoft investors and OpenAI stakeholders that the restructuring didn’t destabilize this relationship.
Partnership terms as competitive intelligence. Whatever was disclosed or implied in this statement about licensing terms, exclusivity, and compute access shapes OpenAI’s competitive position. If Microsoft retains preferential pricing and first access to new models as part of the restructuring terms, that’s a significant structural advantage for Azure’s AI positioning.
Thread: OpenAI-Microsoft relationship. This is the restructuring-era statement; the “next chapter” partnership post (October 2025) likely describes what the post-restructuring relationship looks like in practice. Both should be read together as the documents that define the Microsoft-OpenAI relationship through the end of the decade.
Watch: Whether any renegotiated terms give OpenAI more freedom to pursue non-Microsoft cloud and partnership relationships, which would be a significant shift from the near-exclusive Azure dependency.