A model developer as well as a cloud provider
Microsoft builds developer tools, enterprise software and Azure, and distributes AI through Copilot and Foundry. Its own anniversary account dates the company's start to April 4, 1975. The same product portfolio gives it places to train, serve and use models, alongside its investments in other AI companies. [1]
Microsoft AI's October 15, 2026 technical account described completed pre-training of MAI-Base-2, with 2.8 trillion total parameters and 80 billion active. Microsoft also identified MAI-Thinking-1 as a model post-trained on its earlier MAI-Base-1. These are its own model-development efforts, not merely the resale of OpenAI access. [2]
MAI-Base-2 was still undergoing post-training in that account. A proposed route to license weights to trusted Foundry partners was future work, rather than an unrestricted weight release. Microsoft's held-out comparisons and efficiency estimates were company-run evaluations. [2]
Infrastructure and outside models
Microsoft’s July 2019 partnership with OpenAI paired a $1 billion investment with work on Azure supercomputing and an exclusive cloud arrangement. It was an important earlier infrastructure and financing contribution, separate from Microsoft’s later MAI model development and from the partnership terms subsequently revised. [6]
Microsoft's Maia program connects those models to custom inference hardware. Its October 2026 announcement said Maia 200 was serving production workloads, while Maia 300 and multi-gigawatt expansion were planned for 2027. The distinction separates deployed systems from the announced next generation. [3]
Microsoft also continues to supply outside models. Its April 2026 OpenAI agreement retained a non-exclusive license through 2032 and a primary-cloud relationship while allowing broader cloud distribution. The separate Anthropic partnership brought Claude to Azure. Investment, hosting and licensing establish commercial relationships; they do not make those developers Microsoft subsidiaries. [4][5]
The earlier Tay chatbot incident remains part of this history. Microsoft's March 2016 account describes the abusive interactions that caused it to take Tay offline and the changes it intended to make, an example of deployment behavior that model capability alone did not settle. [7]