Microsoft just shipped the most consequential update to its enterprise AI stack since Copilot launched. Microsoft 365 Copilot Wave 3, announced May 5, 2026, brings Anthropic‘s Cowork agentic technology directly into Microsoft 365 — combining Claude’s multi-step agent capabilities with Microsoft’s identity, governance, and 3-billion-seat distribution. Multi-model intelligence routes tasks across Anthropic, OpenAI, and Microsoft’s own models inside a single managed enterprise surface. Security Copilot agents extend to all E5 customers, an Agent Builder approval workflow gives admins control over agent deployment, and AI-powered skill inferencing reaches E3 and E5 users for the first time. The release is a strategic statement: Microsoft is going to win enterprise AI by being the model-agnostic distribution layer that wraps every credible foundation model with Microsoft’s enterprise machinery.
What’s actually new
Microsoft 365 Copilot Wave 3 is structurally different from the prior two waves. Wave 1 introduced Copilot inside Office apps. Wave 2 added agent capabilities. Wave 3 reframes the product as a multi-model enterprise platform with native agentic workflows, with three concrete additions defining the release.
First, Copilot Cowork. Microsoft worked closely with Anthropic to bring the technology that powers Claude Cowork — Anthropic’s agentic collaboration product — directly into Microsoft 365 Copilot. The result is multi-step task execution across Office apps with Anthropic’s model handling the planning and reasoning, while Microsoft handles the identity, data residency, audit, and admin controls. A user can ask Copilot to “review this quarter’s deal pipeline, draft outreach for the top 20 accounts, schedule meetings with the warm ones, and prepare a status memo for the EVP” and get a multi-step workflow that runs across Outlook, Calendar, Excel, and Word with explicit checkpoints.
Second, multi-model intelligence. Wave 3 routes tasks across multiple foundation models based on the task type and the customer’s preferences. Microsoft’s own models handle some workloads; Anthropic’s Claude handles others; OpenAI’s GPT-5.5 remains the default for many. Admins can configure routing policies — which model handles which kind of work, what data flows where, what’s logged. The customer no longer picks “an AI vendor” at the platform level; the platform picks the right model per task within configured guardrails.
Third, the Agent Builder governance loop. Microsoft 365 Copilot Wave 3 includes a workflow where business users build custom agents in Agent Builder, submit them for administrator review, and only after approval do those agents land in the organization’s Agent Store. The governance layer is what enterprise IT has been asking for since shadow AI emerged in 2023. Combined with Security Copilot agents reaching all E5 customers across Defender, Entra, Intune, and Purview, the security and admin tooling has caught up to the AI deployment pace.
Microsoft also shipped two surprising downstream changes. AI-powered skill inferencing — a feature previously locked to dedicated Copilot and Viva licenses — now activates for Microsoft 365 E3 and E5 customers, dramatically expanding which employees the People skills graph covers. And Copilot Chat is expanding into Teams chats, channels, and meetings as a first-class participant, with mobile support landing soon.
Why it matters
- Microsoft just operationalized the multi-model enterprise. The “which AI vendor do we pick” debate that has dominated enterprise procurement for two years dissolves when the platform ships every credible model under a single enterprise contract. Microsoft 365 Copilot Wave 3 makes vendor selection a routing-policy question, not a strategy question.
- The Anthropic-Microsoft partnership is now the dominant enterprise distribution alliance. Anthropic gets Microsoft’s 3-billion-seat reach. Microsoft gets Claude’s agentic capabilities without having to replicate them. OpenAI continues to power parts of the stack but is no longer the exclusive engine. The triangle is now multi-vendor by design.
- Enterprise governance finally caught up to enterprise AI. Agent Builder with admin approval, audit on every agent action, and identity-aware data routing solve the shadow-AI problem that 2024 and 2025 created. IT can ship agents without losing control.
- Security Copilot reaching all E5 customers redraws the SOC tooling map. The previously separate Security Copilot license is now bundled with E5, putting agentic security workflows into the hands of every E5 organization. Pure-play security AI vendors face immediate pricing pressure.
- Skill inferencing for E3 and E5 changes how organizations understand their workforce. The People skills graph that previously required a separate Viva license now activates across the broader Microsoft 365 base, giving HR and L&D leaders dramatically expanded data with no incremental procurement.
- Copilot Chat in Teams as a first-class participant changes meeting dynamics. AI is no longer a tool the user invokes; it is a participant in the conversation. The implications for hybrid work, asynchronous decision-making, and meeting effectiveness are large.
How to use Microsoft 365 Copilot Wave 3 today
Wave 3 is rolling out to E5 customers first, with E3 access expanding through summer 2026. Tenant administrators can enable specific features as they become available; users see them inside their existing Office apps without separate downloads. Three steps put a workforce on the Wave 3 stack.
- Enable Copilot Cowork in the Microsoft 365 admin center. Sign in as a global administrator, navigate to Copilot > Features, and toggle Cowork integration. Configure the model-routing policy for your tenant — which models handle which task categories, with explicit data-flow controls per model.
- Stand up Agent Builder governance. Designate one or more administrators as agent reviewers. Configure the Agent Store catalog. Publish guidelines for business users about what kinds of agents are encouraged and what’s out of scope. Build the review pipeline before opening Agent Builder broadly to users.
- Train the workforce on agentic workflows. Cowork is a different interaction pattern from question-and-answer chat. Users get value when they delegate multi-step tasks rather than asking single questions. Structured PD on agentic patterns dramatically improves adoption.
For developers building custom agents on the Wave 3 surface, the Agent Builder API exposes structured definitions:
MASK12
Agents created through this API land in the admin review queue. Once approved, they appear in the tenant’s Agent Store and can be assigned to specific user groups via the standard Microsoft 365 group-management surfaces.
How it compares
The enterprise AI platform market in 2026 has consolidated around four major contenders. The differences matter for procurement: surface coverage, model strategy, governance maturity, and pricing patterns differ in ways that drive five-year cost-of-ownership outcomes.
| Platform | Surface coverage | Model strategy | Governance maturity | Pricing |
|---|---|---|---|---|
| Microsoft 365 Copilot Wave 3 | Full Office + Teams + Security + Power Platform | Multi-model (Claude, GPT-5.5, Microsoft) | Agent Builder + admin review + audit | Per-seat tiers (E3/E5) |
| Google Workspace + Gemini Agent | Full Workspace + Search side panel | Single-model (Gemini) | Admin controls + per-step audit | Per-seat + per-step |
| Anthropic Cowork (direct) | Web + integrations to M365, Slack, Drive | Single-model (Claude) | Per-workspace admin + audit | Per-seat tiers |
| OpenAI ChatGPT Workspace | ChatGPT + integrations | Single-model (GPT-5.5) | Workspace admin + connector controls | Per-seat tiers |
Two takeaways. First, Microsoft is the only platform with both multi-model strategy and full enterprise surface coverage. Single-model platforms have model-quality risk; non-Microsoft surface platforms have integration risk. Microsoft 365 Copilot Wave 3 is now the most defensible enterprise default for organizations standardized on Microsoft. Second, the others are not standing still. Google’s Workspace + Gemini Agent push at I/O later this month is expected to land features competitive with Wave 3. Anthropic continues to invest in direct enterprise relationships parallel to the Microsoft partnership. The market is competitive, not collapsed.
What’s next
Three things to watch over the next two quarters. First, the Wave 3 rollout cadence. Microsoft has committed to E5 availability through Q3 2026 and broader E3 expansion through Q4. Customer experience during the rollout — particularly around the multi-model routing and the agent-approval workflow — will set adoption patterns for years. Second, Google’s I/O response. Google’s annual developer conference in mid-May 2026 is the obvious counter-launch moment, and the Gemini Agent + Workspace pitch is competitive with Wave 3 on key dimensions. Third, the regulatory engagement. The combination of Microsoft’s Workspace dominance and the deepening Anthropic partnership invites antitrust scrutiny in both the US and EU. Expect formal inquiries by year-end at minimum.
The longer-term implication is that enterprise AI is becoming a routing-and-governance market rather than a model-selection market. The model providers compete to be one of the engines under the platform. The platforms compete on integration depth, governance, and distribution. The customers benefit from optionality and from the platform vendors’ incentive to deliver the best of every underlying model. The 2027-2028 enterprise AI landscape will look very different from the model-vendor-dominated landscape of 2024-2025, and the firms positioned as routing layers — Microsoft most explicitly, Google in their own way, Salesforce and ServiceNow in adjacent surfaces — extend their enterprise leverage as a result.
Frequently Asked Questions
Do I need a separate Anthropic license to use Copilot Cowork?
No. Cowork features inside Microsoft 365 Copilot Wave 3 are included in the Microsoft 365 Copilot license. The underlying technology is Anthropic’s, but the commercial relationship is direct with Microsoft. Customers who also have direct Anthropic relationships can keep them; the M365 path is independent.
How does multi-model routing work in practice?
The Wave 3 routing layer assigns each task to the best-fit model based on task type, latency requirements, customer policy, and underlying model availability. Admins configure the policy at the tenant level — for example, “always use Claude for multi-step Outlook tasks, GPT-5.5 for quick Word drafts, Microsoft models for image generation.” Users typically don’t see which model handled a task, though tenants can enable transparency where desired.
What happens to existing Security Copilot subscriptions?
Existing standalone Security Copilot subscriptions continue to operate. Wave 3 expands the agentic-security capability inside the broader E5 license, which means many organizations will not need the standalone Security Copilot subscription going forward. Microsoft has communicated migration paths to E5 customers; check with your Microsoft account team for specifics.
Can business users build agents without admin approval?
By default, no. Wave 3’s Agent Builder routes user-built agents through admin review before they reach the tenant Agent Store. Tenant admins can configure exception paths for specific user groups (e.g., a designated “agent prototyping” group) but the default posture is review-required, which is the right default for enterprise environments.
How does this affect organizations that standardized on Google Workspace?
Workspace organizations should evaluate Microsoft 365 Copilot Wave 3 as a competitive benchmark but the migration cost is high. Google’s I/O announcements in mid-May 2026 will set the comparable Workspace + Gemini Agent capability, and most Workspace organizations will find Google’s roadmap closer to their existing infrastructure. The threshold for migrating from Workspace to Microsoft 365 specifically for AI capability is high; the Gemini Agent path will likely close the gap quickly enough to make migration unnecessary for most.
What is the biggest open question about Wave 3 in the next six months?
Whether the multi-model routing produces consistently high-quality experiences in production. Heterogeneous models have different strengths, and routing decisions matter more than any single model’s quality. If Microsoft executes routing well, Wave 3 sets the new enterprise default; if routing produces inconsistent or surprising user experiences, the strategy could backfire and push customers toward single-model alternatives. Customer reports through Q3 2026 will tell the story.