Microsoft 365 Copilot Wave 3 and Copilot Cowork — What the Shift to Agentic Execution Means for Government

The premise of AI assistance has been relatively consistent since Copilot launched: you ask, it responds. The response might be a draft, a summary, an answer, or a recommendation. You take that output and do something with it.

Wave 3 of Microsoft 365 Copilot, announced in March 2026, represents a deliberate shift away from that model. The headline feature — Copilot Cowork — is designed around execution, not just assistance. The framing from Microsoft is direct: Copilot should take action, not just chat.

For federal agencies evaluating their AI roadmap, this is worth understanding in detail.

What Wave 3 Actually Introduces

Wave 3 is positioned as a new version of M365 Copilot that moves beyond single-turn prompts and responses toward what Microsoft calls "embedded agentic capabilities." The core architectural change is that Copilot can now sustain work across time — breaking complex requests into steps, coordinating actions across tools and files, running in the background, and checking in at defined points.

Copilot Cowork is the primary manifestation of this. Rather than generating a single artifact per prompt, Cowork allows users to delegate multi-step work. The sequence: describe an outcome, Cowork turns it into a plan, the plan executes in the background with visible progress checkpoints, and the user can steer, pause, or approve changes throughout.

Work IQ is the context layer that powers this. Cowork draws on signals across Outlook, Teams, Excel, and the rest of M365 — emails, meetings, messages, files — to ground its actions in the same context the user would bring to the task themselves. This is meaningful because agentic execution without context is unreliable; Cowork's outputs are grounded in actual organizational data, not generic reasoning.

Multimodel architecture is worth noting. Wave 3 brings Anthropic's Claude technology into Copilot alongside Microsoft's own models. The framing is that Copilot chooses the right model for the task regardless of who built it. For government buyers, this raises questions about data handling across model providers — questions worth raising with Microsoft's account team in the context of your tenant's data protection configuration.

Concrete Examples That Translate to Federal Work

Microsoft published specific scenarios with Wave 3. Several have direct analogs in federal environments:

Calendar management and focus time. Cowork can review an Outlook schedule, identify low-value meetings and conflicts, propose changes, and apply them once approved. For senior federal leaders and program managers whose calendars are often over-committed, this is a practical time recovery tool — not a novelty.

Meeting preparation. Cowork can pull from relevant emails, meetings, and files to produce a briefing document, supporting analysis, and presentation deck ahead of a stakeholder meeting. Federal program reviews, congressional briefings, and customer engagements all involve this kind of preparation work. The difference with Cowork is that the multi-step assembly happens autonomously under user supervision.

Research synthesis and document production. Complex policy analysis, contract reviews, and program assessments require pulling from multiple sources and synthesizing into structured outputs. Cowork's ability to sustain multi-step work — running for minutes or hours as needed — is directly relevant to these workflows.

The Governance Architecture Matters

For federal agencies, the governance design of Cowork is as important as the capability itself. Microsoft is explicit about this in the announcement: work is observable, actions are transparent, progress can be reviewed and stopped, and everything operates within Microsoft's security, identity, and governance framework.

That architecture — observable, stoppable, enterprise-protected — is the minimum viable design for government adoption. Agentic AI that acts without audit trail or human intervention points would not be deployable in federal environments under current policy requirements. Cowork's design at least aligns with what government use requires, though agencies will need to evaluate it against their specific ATO and data governance requirements.

Availability and GCC/GCCH Status

Cowork was announced in March 2026 as a research preview with a limited set of commercial customers. It is not generally available as of this writing. Timeline to broader availability has not been formally committed.

This is important context: Wave 3 and Cowork represent Microsoft's direction, not a capability available in federal tenants today. Agencies should track this closely but should not build deployment timelines around features that remain in preview. GCC and GCCH availability will follow commercial GA; the gap is typically weeks to months for Copilot features, longer for GCCH.

What Federal Agencies Should Do Now

Understand the architectural shift. Copilot is evolving from a prompt-response tool to a task-execution platform. Agencies that have built adoption programs around current Copilot capabilities should plan for this evolution. Training, governance frameworks, and change management approaches will need to account for agentic execution — not just AI-assisted drafting.

Identify high-value delegation candidates. The strongest near-term use cases for Cowork are multi-step, recurring tasks with clear inputs and outputs: weekly reports, meeting prep packages, document assembly, inbox triage. Identify these workflows now so you're ready when availability expands.

Flag the multimodel question. Work with your Microsoft account team to understand how data flows across model providers in the Cowork architecture, and how that interacts with your tenant's data protection configuration — especially for GCC and GCCH environments.

Monitor for GA and GCC timelines. Preview features can move to GA quickly. Establish a process for tracking Copilot release notes and Message Center notifications so Cowork's availability doesn't catch your adoption program unprepared.

The Bigger Picture

Every major platform transition has a moment when the architecture changes enough that early decisions about adoption strategy need to be revisited. The shift from Copilot as assistant to Copilot as executor is that kind of transition.

Agencies that have treated Copilot primarily as a drafting aid will need to think differently when the same platform can sustain hours-long, multi-step work autonomously. The governance questions, the change management requirements, and the use-case identification work are all different at that scale.

Wave 3 and Cowork are in preview. But the direction is clear and the pace is fast. Federal agencies that wait for GA to start thinking through the implications will be behind.

Sources: Microsoft 365 Blog, March 9, 2026 · Copilot Cowork announcement, March 9, 2026