Microsoft–OpenAI Amend: Multi-Cloud Rights, Capped Revenue Share, Non-Exclusive IP
Microsoft and OpenAI’s April 27 amendment keeps Azure first-ship primacy but lets OpenAI serve any cloud; IP license to Microsoft stays through 2032 but turns non-exclusive; OpenAI→Microsoft revenue share continues through 2030 with a total cap; Microsoft stops paying revenue share to OpenAI.
The partnership that built enterprise ChatGPT is no longer a quasi-exclusive cloud marriage. The amendment codifies multi-cloud commercial freedom while locking a capped, time-bounded money pipe back to Microsoft — Azure first-ship preference survives; exclusivity does not.
Microsoft and OpenAI (April 27) announced an amended long-term agreement. Microsoft remains primary cloud partner; OpenAI products ship first on Azure unless Microsoft cannot and chooses not to support required capabilities. OpenAI may serve all products across any cloud provider. Microsoft’s license to OpenAI IP for models and products runs through 2032, now non-exclusive. Microsoft no longer pays a revenue share to OpenAI. OpenAI→Microsoft revenue share continues through 2030 at the same percentage, independent of OpenAI’s technology progress, subject to a total cap. Microsoft stays a major shareholder.
What changed
| Term | New posture (company blogs / CNBC) |
|---|---|
| Cloud distribution | Any cloud OK; Azure first unless MSFT can’t/won’t support |
| IP license | Through 2032, non-exclusive |
| MSFT → OpenAI rev share | Ended |
| OpenAI → MSFT rev share | Through 2030, same %, capped total |
| Equity | Microsoft remains major shareholder |
Both sides say the change simplifies the relationship and supports joint infrastructure (datacenters, next-gen silicon, cybersecurity AI). Earlier structures had tighter exclusivity and AGI-tied mechanics — desk context from contemporaneous reporting, not a full contract dump.
Claims vs checks
Deal mechanics above are from Microsoft’s official blog and aligned wire coverage (CNBC). Exact percentage, dollar cap, and AGI-clause retirement text are not fully public in the blog post — treat “same percentage” and “total cap” as company-described, not audited schedules. Consistency with prior AWS/Google Cloud OpenAI availability is framing, not a new independent disclosure.
Limits
- Cap amount and share rate undisclosed in the primary blog.
- “Ship first on Azure” exception criteria are qualitative.
- Shareholder economics beyond “major” stake are not refreshed here.
Sources
- Microsoft blog: “The next phase of the Microsoft-OpenAI partnership” (April 27, 2026).
- CNBC: “OpenAI shakes up partnership with Microsoft, capping revenue share payments” (April 27, 2026).
- Directions on Microsoft and other contemporaneous reporting on the amended terms.