Microsoft and OpenAI Rewrite Partnership: Multi-Cloud, AGI Clauses Out

Microsoft and OpenAI announced an amended partnership agreement on Monday morning, ending one of the most consequential exclusivity deals in tech and clearing the way for OpenAI to run its products on any cloud, including Amazon Web Services and Google Cloud. The new framework caps the revenue share OpenAI sends to Microsoft, removes the so-called "AGI trigger" provisions, and extends Microsoft's IP license through 2032 — but on a non-exclusive basis.

The timing is not subtle. Jury selection in Elon Musk's lawsuit against OpenAI began the same morning in Oakland, with Microsoft itself named as a co-defendant in the trial we covered earlier today. The amendment quietly defuses several of the partnership pressure points the suit had spotlighted.

What Actually Changed

Under the original deal, OpenAI's API and many of its enterprise products were exclusive to Microsoft Azure. That exclusivity is gone. OpenAI can now serve all of its products across any cloud provider, though Microsoft remains the "primary" cloud partner, and OpenAI says new products will continue to ship on Azure first unless Microsoft can't or won't support the required capabilities.

Microsoft also loses its exclusive license to OpenAI's models. The license itself runs through 2032 — two extra years versus the prior 2030 expiration — but Microsoft no longer has the sole right to commercialize OpenAI IP through its own products. Both companies can now pursue AGI research and partnerships independently, including with each other's competitors.

The revenue share pipe has also been narrowed. OpenAI will keep paying Microsoft a cut of revenue through 2030, but the total amount is now subject to a cap. And Microsoft no longer pays a revenue share to OpenAI for the OpenAI products it resells through Azure — a meaningful margin shift in Microsoft's favor on the cloud side.

The AGI Clause Is Finally Dead

The most-watched change is what the companies removed. The original agreement contained complex language giving OpenAI's board the right to declare it had achieved artificial general intelligence — and once declared, Microsoft would lose access to future OpenAI technology. That clause hung over every Microsoft Azure customer and every OpenAI valuation conversation for the past three years.

That entire mechanism is gone. The amended deal does not make Microsoft the arbiter of AGI, and it does not give OpenAI's board a contractual lever to cut Microsoft off. Both parties can now point to the same shared capabilities roadmap without a binary "switch" sitting in the middle of it.

For investors and enterprise buyers, this is the change that matters most. The AGI clause was a major source of partnership uncertainty — and removing it makes commitments on either side easier to underwrite.

Why It's Happening Now

OpenAI has been trying to lock in compute capacity from every major cloud since late 2025. The reported $50 billion infrastructure deal with Amazon, the deepening Google relationship, and OpenAI's own Stargate buildout with Oracle and SoftBank had all run up against the original exclusivity language. The amendment is essentially Microsoft formalizing what was already happening in practice.

Microsoft, for its part, has been steadily diversifying its model supply. Microsoft 365 Copilot now routes meaningfully through Anthropic's Claude models for some workloads, and Mustafa Suleyman's MAI team has been shipping in-house Microsoft AI models. The exclusive license was no longer matching Microsoft's own product strategy.

The Musk trial provides the cleanest political cover. By restructuring before the courtroom phase, both companies blunt the central narrative that Microsoft and OpenAI were locked into a quasi-merger that violated OpenAI's nonprofit commitments.

Who This Affects

Enterprises are the biggest near-term winner. Customers who have wanted to standardize on OpenAI models but are committed to AWS or Google Cloud no longer have to wait. Expect AWS Bedrock and Google Vertex to add first-party OpenAI model endpoints over the coming months.

For Anthropic, the calculus is more complex. Microsoft losing exclusivity means OpenAI competes on equal cloud footing, but it also means Microsoft is now a freer buyer of Claude models — which it has been doing aggressively since Anthropic's $40 billion Google investment last week.

For developers, the practical change is that OpenAI's "ship on Azure first" default goes away faster than expected. Multi-cloud deployments that used to require waiting for Microsoft channel availability should now move in parallel.

What Industry Watchers Are Saying

Analysts called the deal a "marriage contract rewrite" rather than a divorce. Microsoft shares dipped roughly 1% in early trading on the revenue-share clarity, while OpenAI's secondary market valuation continued its upward trajectory toward the $500 billion range that recent tender offers have priced.

CNBC reported that the amendment also ends Microsoft's legal exposure tied to OpenAI's $50 billion Amazon infrastructure deal — a contract that, under the old exclusivity terms, would have required Microsoft sign-off OpenAI was reluctant to seek.

What Comes Next

OpenAI has signaled that its enterprise products will be available on AWS and Google Cloud "in the coming months," with no firm date yet. Microsoft is expected to use Q3 earnings on Wednesday to walk investors through the financial impact, including the capped revenue share figure.

The trial in Oakland continues regardless. Removing the AGI clause does not make Musk's underlying claims moot — they hinge on alleged conduct from 2023 and 2024 — but it does narrow the relief Musk could plausibly request.

The Bottom Line

The biggest exclusivity arrangement in modern AI is over. OpenAI gets multi-cloud freedom, Microsoft gets a cleaner financial picture and a longer license window, and the AGI trigger that haunted the partnership for years is gone. For enterprise buyers, this is the moment to revisit any "we can't standardize on OpenAI because we're not on Azure" assumption — that constraint just disappeared.