Microsoft loosens OpenAI exclusivity
- Microsoft and OpenAI rewrote their partnership on April 27, ending Microsoft’s exclusive rights and letting OpenAI sell and run products across any cloud. - The sharpest detail is the trade: Microsoft stops paying OpenAI revenue share, while OpenAI keeps paying Microsoft through 2030 under a capped formula. - Azure stays first in line, but not alone — which weakens Microsoft’s moat and gives OpenAI real multi-cloud leverage.
Cloud access is the real story here. For years, Microsoft’s alliance with OpenAI gave Azure a special position in the AI market — not just as an investor’s platform, but as the place where OpenAI’s commercial products lived first and most tightly. That setup helped Microsoft sell Azure and helped OpenAI get massive compute. But it also boxed OpenAI in. On April 27, Microsoft and OpenAI changed the deal, and the relationship is now much less exclusive. (blogs.microsoft.com) ### What changed in the agreement? Three things matter most. OpenAI can now serve all its products to customers across any cloud provider. Microsoft’s license to OpenAI intellectual property still runs through 2032, but it is now non-exclusive. And Microsoft will no longer pay a revenue share to OpenAI, while OpenAI’s revenue-share payments to Microsoft continue through 2030 at the same percentage, with a total cap. (blogs.microsoft.com) ### Does that mean Azure lost OpenAI? No — but Azure lost exclusivity. Microsoft says it remains OpenAI’s primary cloud partner, and OpenAI products will still ship first on Azure unless Microsoft cannot or decides not to provide the needed capabilities. So Azure keeps pole position. It just no longer has the track to itself. (blogs.microsoft.com) ### Why does non-exclusive matter so much? Because exclusivity was the strategic prize. Microsoft didn’t just want financial upside from OpenAI — it wanted a product moat. If the best-known AI models and tools were effectively tied to Azure, that gave enterprise customers a reason to stay in Microsoft’s ecosystem. A non-exclus(blogs.microsoft.com)ps. (blogs.microsoft.com) ### Why would OpenAI push for this? Scale and bargaining power. OpenAI needs enormous computing capacity, and one cloud was becoming too tight a bottleneck for a company trying to serve consumers, developers, and large enterprises at once. Multi-cloud access gives OpenAI more room to place workloads where capacity, price, or s(blogs.microsoft.com)turally dependent on one provider. That is the big unlock. (arstechnica.com) ### So did Microsoft give up too much? Not really. Microsoft keeps a major equity stake in OpenAI, remains the primary cloud partner, and continues to receive revenue-share payments through 2030. It also still has rights to OpenAI models and products through 2032. Basically, Microsoft gave up exclusivity, not the relationship. That is a meaningful concession, but it is not a breakup. (blogs.microsoft.com) ### What about the old AGI clause? That piece appears to be gone from the new setup, which matters because the earlier structure tied some rights and economics to whether OpenAI’s board declared it had reached AGI — a messy trigger with obvious governance risk. Removing that kind of tripwire makes the partnership simpler and less weird. It turns a philosophical clause into a more normal commercial contract. (unite.ai) ### Who gains from this right now? OpenAI gains flexibility first. Amazon, Google, and Oracle gain a shot at OpenAI workloads and distribution. Microsoft keeps deep ties, but loses a cleaner Azure advantage. For enterprise buyers, the immediate effect is optionality — they may be able to buy OpenAI-powered services without committing as tightly to Microsoft’s cloud stack. (arstechnica.com) ### What’s the bottom line? This is less a divorce than a rewiring. Microsoft and OpenAI are still closely linked, but the relationship now looks more like a strategic partnership inside a competitive market than a locked-up alliance. OpenAI gets room to expand. Microsoft keeps enough economics and access to stay (arstechnica.com) for. (blogs.microsoft.com)