Invest1 publisher2 min readPublished
Microsoft widens Grok across Copilot 205 days after its US-only preview
Claude went into Copilot Studio a year ago, Grok 4.1 Fast reached a US preview in February, and the September 12 announcement takes Grok across Copilot. Some xAI models run outside Microsoft's own infrastructure.
The Investor · Invest desk
What happened
- Microsoft said on September 12, 2026 that it is adding xAI's Grok models to its Copilot lineup, giving enterprise customers another third-party system inside Microsoft's productivity stack.
- The announcement broadens an existing Grok integration across Microsoft's Copilot experiences more widely.
- Anthropic's Claude models were integrated into Copilot Studio in September 2025, the first outside vendor named in Microsoft's Copilot roster.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- decision The purchasing decision moves down to the task. A legal team's contract analysis and a marketing team's copy can sit on different engines under one Copilot interface, and IT picks routes instead of standardising on a vendor.
- constraint Each externally hosted engine sends the buyer's compliance team back through a data-residency review that Microsoft's own contract does not answer. An engine that fails that review is not a switching option at any price.
- exposure On Crypto Briefing's reading, Microsoft's exposure to one vendor's pricing or slippage falls with every model it adds. Each vendor's revenue now depends on where the platform points the traffic.
- contradiction In Crypto Briefing's account the same roster is both the selling point and the unresolved risk: model choice is the enterprise benefit, and the piece questions whether governance stays consistent across it.
Routing gives a buyer leverage only where the engines substitute for one another. An enterprise gets a better price out of a model vendor only when it can move the workload to another engine at comparable cost and under terms its own compliance function will sign. Some xAI models, including certain Grok variants, are hosted outside Microsoft's infrastructure and governed by separate terms [6]. A customer with a strict residency policy can order fewer engines than Microsoft lists.
The dates show a staging pattern. Microsoft said at Build in May 2025 that Grok models would be hosted on Azure AI Foundry [5]. Grok 4.1 Fast reached preview for US organizations through Copilot Studio on February 19, 2026 [3], and the wider Copilot announcement followed 205 days after that [10]. Sixteen months from the hosting commitment to broad availability [11]. Claude entered Copilot Studio in September 2025, roughly twelve months before the same announcement [2][12], so the developer surface takes the model first and the general Copilot experience gets it two or three quarters later.
The report does not disclose pricing or revenue-share terms for the integration, or how enterprise traffic divides between engines [13].
Crypto Briefing frames the multi-model approach as defensive. It cuts Microsoft's dependency on any single provider and insulates it against a partnership that sours, a model that falls behind, or a vendor whose pricing becomes unpalatable [7]. I would put it more narrowly. The party that owns the interface owns the switching decision. The counter-thesis sits in the same source's closing question, which asks whether Microsoft can hold quality and governance consistent across an expanding roster, especially where models run on infrastructure it does not directly control [8]. Each addition also spends Copilot integration and governance engineering on a vendor Microsoft does not own.
Concentration is what would break the argument. If one engine takes the overwhelming share of Copilot calls, the extra vendors buy Microsoft governance work and no bargaining position. The per-team choice the source illustrates, a legal team on one model for contract analysis and marketing on another for rapid content generation [9], describes a demo more than a purchasing pattern. The argument also fails in the other direction: if the externally hosted variants never clear a large customer's residency review, Microsoft has added a name to the list without giving that customer an alternative to the incumbent [6].
What to watch
- Any move of the externally hosted Grok variants onto Azure AI Foundry would bring them under Microsoft's own contract terms.
- Whether the wider Grok rollout extends past US organizations, the limit that applied to the February preview.
- A third outside vendor joining the Copilot roster on the roughly annual cadence set by Claude in 2025 and Grok in 2026.