The UK Competition and Markets Authority (CMA) closed its review of Microsoft’s partnership with Mistral AI on May 17, 2024, after deciding the arrangement then in place did not qualify for a merger investigation. The CMA found that Microsoft had not gained the ability to materially influence Mistral’s commercial policy. That was a narrow jurisdictional decision—not a full finding that the partnership posed no competition risks. The companies announced a substantial expansion in July 2026, which the 2024 decision did not assess.
What Microsoft and Mistral agreed to
Microsoft and Mistral announced a multi-year strategic partnership on February 26, 2024. Its components included Azure access to AI-optimised supercomputing infrastructure for Mistral’s model training and inference, distribution of Mistral models to Microsoft customers, and cooperation on commercial opportunities, research and selected development initiatives. Microsoft also introduced Mistral Large on Azure. Microsoft’s announcement described model availability through Azure AI Studio, Azure Machine Learning and its Models-as-a-Service offering.
This was a partnership involving infrastructure, distribution and cooperation; it was not an acquisition of Mistral. Access to Azure and model distribution can give both companies commercial advantages without necessarily transferring control of Mistral’s business to Microsoft.
Why the CMA examined the arrangement
UK merger control can apply to some partnerships even when one company has not bought another. The CMA considered whether Microsoft and Mistral had ceased to be distinct businesses under section 26 of the Enterprise Act 2002—specifically, whether Microsoft had acquired the ability to materially influence Mistral’s commercial policy.
Recommended Free Tools
#1 Best Overall
The review formed part of wider regulatory attention to partnerships between large technology companies and developers of AI foundation models. The CMA had invited views on AI partnerships and other arrangements amid concerns that such deals could reinforce existing market power across the AI value chain. Its broader concerns did not, by themselves, establish that this particular partnership was a merger. The CMA’s announcement on AI partnerships set out that wider context.
What the CMA decided—and why
The CMA invited third-party comments on April 24, 2024, announced a merger inquiry on May 16, and closed the case the next day. Its full decision concluded that Microsoft and Mistral had not ceased to be distinct for the purposes of section 26. Because the arrangement did not create a relevant merger situation, it did not qualify for investigation under the merger provisions.
In assessing material influence, the CMA considered the contractual relationship and Microsoft’s rights, as well as possible collaboration on model training, development, customers and public-sector work. It concluded that the contemplated collaboration and development opportunities were too uncertain, in the absence of other factors, to establish that Microsoft could materially influence Mistral’s commercial policy.
The legal questions were not simply whether the companies worked closely or whether their relationship might affect competition. The CMA’s merger analysis asked whether a relevant merger situation existed and, if so, whether it could be expected to result in a substantial lessening of competition in a UK market. It stopped at the first threshold: the companies had not ceased to be distinct under the test it applied.
What “survives scrutiny” means—and what it does not
It is broadly fair to say the partnership survived the CMA review: the case closed without a merger remedy or prohibition, and the parties were not referred for a full Phase 2 merger investigation. But “cleared” can suggest a broader merits assessment than the CMA actually conducted. The regulator found that this arrangement, on the facts before it, did not qualify for investigation under merger law; it did not issue a general endorsement of Microsoft’s position in AI or cloud markets.
- It means: the CMA did not find that Microsoft had acquired material influence over Mistral under the partnership then reviewed.
- It does not mean: the CMA found no competitive risks in AI or cloud computing, or that Microsoft is immune from future scrutiny.
- It does not decide: whether a materially changed agreement—such as one adding governance rights, exclusivity, or control over commercial strategy—would meet merger thresholds.
Nor does a decision under merger provisions rule out scrutiny under other competition-law theories or regulatory powers. The CMA’s separate AI and cloud work illustrates why those questions should not be collapsed into this merger-jurisdiction decision.
Rank #4
How the partnership developed after the review
| Date | Development |
|---|---|
| November 2023 | Microsoft said Mistral 7B had been integrated into the Azure AI model catalog. |
| February 26, 2024 | The companies announced their multi-year partnership and introduced Mistral Large on Azure. |
| April 24, 2024 | The CMA invited third-party comments on the partnership. |
| May 16–17, 2024 | The CMA announced its merger inquiry, then closed the case after deciding the arrangement did not qualify for investigation. |
| July 24, 2024 | Microsoft announced Mistral Large 2 and Mistral Nemo as serverless, pay-as-you-go Azure offerings. Microsoft’s Azure AI announcement described the deployments. |
| July 21, 2026 | Microsoft and Mistral announced an expanded strategic partnership, including a multibillion-dollar Microsoft commitment connected to Mistral’s European AI-compute expansion, and wider model availability through Microsoft Foundry and Copilot Studio. Microsoft’s announcement also described Azure, Azure Local and disconnected deployment options. |
The 2026 expansion shows commercial continuity and a deeper relationship; it does not show that the CMA separately assessed or cleared the later arrangements. A materially different agreement may present different questions from those the CMA resolved in 2024.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the decision means for AI competition
Cloud platforms can make AI models easier to discover, deploy and scale for customers already using their services. Hosting third-party models also gives enterprises more model choice within a familiar cloud environment. But model availability through one platform can strengthen reliance on that platform’s billing, identity, data, monitoring and development tools. A technically available model is not necessarily easy to move between providers once applications depend on platform-specific APIs and workflows.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The CMA separately closed its Microsoft–OpenAI merger inquiry in March 2025, but that was a different case with different facts—not a precedent that automatically resolves the Mistral arrangement. Likewise, the CMA’s cloud-services work concerns issues such as competition involving Microsoft and Amazon Web Services; it should not be read as part of the 2024 Mistral decision. See the Microsoft–OpenAI case and the cloud-services market investigation.
What enterprise buyers should check
The regulatory outcome does not determine whether Azure-hosted Mistral models are the right choice for a particular organisation. Availability, licensing and operating requirements vary by model and deployment. Before committing, buyers should verify:
- Model and region: confirm that the required model and deployment type are available for the relevant Azure subscription and geography.
- Deployment and data handling: establish where data is processed, what is logged or retained, and whether the proposed environment is public cloud, cloud-connected, local or genuinely disconnected.
- Licensing and commercial terms: identify the applicable model licence and pricing. Microsoft says partner providers define the licensing terms and prices for their models offered through Azure, and availability varies by model and region. Microsoft’s partner-model documentation explains these distinctions.
- Total cost: account for more than token charges. Networking, storage, monitoring, orchestration, support and data-transfer costs can also affect the bill.
- Portability and dependencies: check whether prompts, tools, evaluations and application code can move to another provider, and how much the system depends on Foundry, Copilot Studio or Azure-specific services.
- Operational commitments: confirm support, service levels, update procedures, security controls and continuity arrangements in the applicable contract.
For current Azure deployment patterns, Mistral describes managed pay-as-you-go services and real-time endpoints tied to selected GPU infrastructure in its Azure deployment documentation. Those options, and the models available through them, should be checked against the buyer’s region and requirements rather than assumed to be universal.
Conclusion
The CMA’s May 2024 decision was narrow: it found no relevant merger situation in the Microsoft–Mistral partnership as then structured because Microsoft lacked material influence over Mistral’s commercial policy. The relationship continued and expanded, but the 2024 outcome is not a permanent exemption or a ruling on the substantially expanded arrangement announced in 2026.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
