What Is Copilot Wave 3? Microsoft’s Agentic AI Update

Copilot Wave 3 is Microsoft’s agentic AI update that went generally available May 1, 2026, alongside Microsoft 365 E7 and Agent 365. It’s the third major iteration of Microsoft 365 Copilot — and the first where agents are first-class rather than bolted on.

Last verified: May 2, 2026

The three Waves explained

Wave	Year	What it did
Wave 1	2023-2024	Copilot in Word, Excel, Outlook, PowerPoint, Teams — single-shot AI assistance
Wave 2	2025	Expanded Copilot to more apps; Copilot Studio for custom Copilots; agent capabilities introduced
Wave 3	May 2026	Multi-model orchestration; Copilot Cowork; Agent 365 integration; agentic Office apps

Wave 1 was “AI inside the apps.” Wave 2 was “more apps and custom AI.” Wave 3 is “agents inside Office, with humans alongside.”

What Wave 3 actually shipped

Microsoft’s March 9, 2026 announcement defined Wave 3 around four pillars:

1. Multi-model orchestration

Copilot Wave 3 routes tasks across multiple AI vendors per task type:

• Anthropic Claude (Opus 4.7 family) — added through 2026 for reasoning-heavy and coding tasks.
• OpenAI next-gen models (GPT-5.5 family) — for general-purpose work.
• Microsoft’s own models — for Microsoft-specific workflows and lower-cost tasks.

The routing is invisible to users. Microsoft picks which model handles each task based on what it’s good at. Excel Python analysis might run on a different model than a Word document draft, which might run on a different model than a Teams meeting summary.

2. Copilot Cowork

Copilot Cowork is the new collaborative surface where humans and agents work side-by-side inside the same document. Instead of “ask Copilot a question, get an answer,” Cowork is “agent edits the document while you watch, you accept or reject changes inline, you steer with comments.”

It’s the answer to “how do agents fit into a Word document I’m already editing.” Cowork works across Word, Excel, Outlook, and Teams.

3. Agent 365 integration

Wave 3 ships in lockstep with Agent 365. Copilot is the user-facing surface; Agent 365 is the control plane (identity, governance, lifecycle). Wave 3 features assume Agent 365 is the way agents are managed, even when you’re using standalone Copilot rather than the E7 bundle.

4. Agent-aware Office apps

Office apps now expose agent affordances natively:

• Excel agents that reason across multiple workbooks (cross-workbook analysis is new at GA).
• Outlook agents that triage, draft, and summarize at the inbox level.
• Teams agents that join meetings and produce structured outputs.
• Word agents that draft long-form documents with company context (via Microsoft Graph).

How Wave 3 compares to Wave 2

Capability	Wave 2 (2025)	Wave 3 (May 2026)
AI model	OpenAI primary	Multi-vendor routing
Agents	Custom Copilots in Studio	Native Agent 365 integration
User surface	Copilot chat panel	Copilot Cowork in-document
Excel	Python execution (preview)	Cross-workbook analysis (GA)
Identity	Standard M365 user identity	Agent identity in Entra
Governance	M365 admin	Defender for Agents (preview to June 2026)

The shift from “Copilot helps you” to “Copilot and agents work alongside you” is the core narrative.

Pricing

Wave 3 features ship to anyone with a Microsoft 365 Copilot license. The licensing matrix:

• Microsoft 365 Copilot — $30/user/mo standalone add-on. Gets Wave 3 features but not Agent 365.
• Agent 365 — $15/user/mo standalone add-on. Gets the agent control plane and prebuilt agents.
• Microsoft 365 E7 — $99/user/mo. Bundles E5 + Copilot + Agent 365 + Entra Suite + advanced governance.

For most knowledge worker rollouts, the question is whether to buy E7 or assemble E5 + Copilot + Agent 365 separately. We covered the E7 vs E5 + Copilot pricing math separately.

What’s still preview, not GA

Wave 3 GA on May 1 didn’t include everything Microsoft announced in March:

• Defender for Agents runtime enforcement — preview through June 2026.
• Intune policy-based agent controls — preview through June 2026.
• Context mapping — preview through June 2026.

Identity governance is GA. Runtime governance is preview. That gap matters for security-sensitive deployments and is the main reason large enterprises are piloting Wave 3 now and waiting until late 2026 to scale up.

Why Microsoft built Wave 3 this way

Three strategic reasons stand out:

1. Multi-model is a hedge against single-vendor risk. Microsoft can’t be too dependent on OpenAI given OpenAI’s independent commercial trajectory. Adding Claude and Microsoft’s own models reduces concentration risk.
2. Cowork answers the “agents replace humans” anxiety with “agents work alongside.” Politically and culturally, the Cowork framing is easier for enterprise rollout than autonomous agent framing.
3. Agent 365 is the moat. The control plane (identity, governance, lifecycle) is harder to replicate than any single AI feature. Microsoft is using Wave 3 to drive Agent 365 adoption and lock in the control plane.

Who should adopt Wave 3 now

Adopt now:

• Microsoft 365 Copilot customers — Wave 3 features ship automatically.
• Organizations piloting Agent 365 standalone at $15/user/mo for hundreds of seats.
• M365 shops with mature Entra deployments wanting Cowork experience.

Wait until Q3-Q4 2026:

• Security-sensitive deployments needing runtime enforcement at scale.
• Organizations deciding between E7 and E5 + Copilot + Agent 365 (the math gets clearer once Defender features are GA).
• Highly regulated industries.

Bottom line

Copilot Wave 3 is Microsoft’s first agentic AI release where agents are first-class inside Office apps rather than bolted on. Multi-model routing, Copilot Cowork, and Agent 365 integration are the four pillars. The Defender governance gap (preview through June 2026) is the main reason to pilot now and scale later. Wave 3 features ship to anyone with a Microsoft 365 Copilot license, so you don’t need E7 to evaluate it — but E7 is the cleanest path to the full bundle if you already plan to adopt Agent 365 and Entra Suite.

Built with 🤖 by AI, for AI.