vibes.jukkan.com › Cowork vs. Cowork

Analysis · April 2026

Cowork vs. Cowork

Same name, same model, completely different product. Here's how Anthropic's Claude Cowork and Microsoft's Copilot Cowork actually differ.

When Microsoft announced Copilot Cowork in March 2026, built on the same agentic harness as Anthropic's Claude Cowork, the naming got immediately confusing. They share a brand word, a model, and a general pitch — "describe the task, let the AI do the work." But what you actually get out of each is shaped by one foundational architectural split: one runs on your machine, the other runs in Microsoft's cloud. Everything else follows from that.

The core split

Claude Cowork — Anthropic

Boots a local Ubuntu VM on your device via Apple Virtualization (macOS) or Hyper-V (Windows). Files mount into the VM; tasks run on your hardware. The Desktop app must stay open. Add Computer Use and it can click around your actual screen too.

Copilot Cowork — Microsoft

Runs in Microsoft's cloud, inside your M365 tenant. No local process, no VM. It reads your emails, calendar, files, and Teams chats via Microsoft Graph — and keeps working after you close your laptop.

This means they're not really competing for the same use case. Claude Cowork is best when you need to work on local files, across arbitrary apps, or outside the Microsoft stack. Copilot Cowork is best when your work lives in M365 and you need IT-governed, auditable automation.

Side-by-side comparison

Dimension Claude Cowork (Anthropic) Copilot Cowork (Microsoft)
Execution location Local VM on your machine Microsoft cloud (M365 tenant)
Runs while you're away No — app must stay open Yes — cloud-native
Local file access Yes — folder-level mount No — cloud files only
M365 data (email, Teams, calendar) Via MCP connectors Yes — native via Graph
Computer Use (screen control) Yes — macOS only Not available
Third-party app connectors Yes — MCP + plugin marketplace M365 apps only (for now)
Audit logging / compliance export Not available Yes — via Purview
Per-user admin controls Org-wide on/off only Yes — security groups
DLP / sensitivity labels None Yes (known bypass incidents)
EU data residency US only M365 data yes; Claude inference excluded
Human-in-the-loop approvals Basic prompts before risky actions Risk-tiered: approve / approve & remember / reject
Session memory across chats Within Projects only Yes — cloud-persistent
Model powering it Claude Opus 4.6 (confirmed) Claude (version not disclosed)
Context window 200K–1M tokens (plan-dependent) 16K char input limit; rest undisclosed
Available to individuals Yes — starts at $20/mo Enterprise only (M365 Copilot required)
Current status Research preview (GA date TBD) Research preview via Frontier program

Governance — the biggest practical gap

This is where they diverge most sharply for organizations. Claude Cowork is explicit about it:

Anthropic's own documentation states: "Cowork activity is not captured in Audit Logs, Compliance API, or Data Exports. Do not use Cowork for regulated workloads." There are no per-user role controls and no compliance export. Session history stays on individual machines.

Copilot Cowork inherits the full M365 compliance stack — Purview audit logs, eDiscovery, DLP policy enforcement, Conditional Access via Entra ID. Agent 365 (available May 1 at $15/user/month) adds dedicated agent identities and agent behavior monitoring.

One important asterisk on Microsoft's governance story: Anthropic models are explicitly excluded from the EU Data Boundary. Even for EU tenants that opt in, data residency guarantees don't apply to Claude inference within Copilot. The hosting location of Claude model calls inside the Microsoft stack isn't publicly documented.

Pricing

Claude Cowork — Anthropic
Pro$20 / mo
Max 5×$100 / mo
Max 20×$200 / mo
Team Standard$25 / seat / mo
Team Premium$150 / seat / mo
EnterpriseCustom
Copilot Cowork — Microsoft
M365 Copilot add-on$30 / user / mo
Agent 365 standalone$15 / user / mo
M365 E7 bundle$99 / user / mo
Free / consumer tierNot available

Claude Cowork is accessible to anyone with a $20 Pro subscription. Copilot Cowork requires an enterprise M365 Copilot license — it's not available to individual users or SMBs outside enterprise agreements.

The strategic angle

Microsoft built Copilot Cowork because Anthropic's January 2026 launch of Claude Cowork triggered a roughly $285 billion SaaS market selloff in a single week. The response took less than two months. Microsoft's position is that combining Claude's agentic harness with M365's Work IQ context layer creates something neither company can build alone — the "multimodel advantage" pitch.

"Will it continue to use lower-end models or older models without telling you the way Copilot does? Microsoft has a tendency to launch a leading product and then let it sit for awhile. I'm curious about whether their pacing will change."

— Ethan Mollick, on Copilot Cowork at launch

This is a real tension. Anthropic iterates on Claude Cowork directly — it shipped Computer Use in roughly six weeks from launch. Microsoft has to integrate changes through enterprise compliance layers, multi-model orchestration, and the Frontier release cadence. Feature lag is baked into the structure.

The relationship is also financially entangled in both directions: Anthropic committed $30 billion in Azure compute; Microsoft invested $5 billion in Anthropic. These are not independent products from independent companies.

Who should use which

Use Claude Cowork if you're an individual, a team not standardized on M365, or you need to work across local files and third-party apps with maximum flexibility. Computer Use on macOS is unique to this product. Faster iteration, more connectors, no enterprise procurement needed.

Use Copilot Cowork if you're in an M365-heavy org, IT needs an audit trail, and your work lives in Outlook/Teams/SharePoint. The governance story is materially better. Don't expect the same feature velocity, and flag the EU data residency gap to your compliance team before enabling.

The real answer for enterprise power users is probably both. Copilot Cowork for governed, M365-native workflows. Claude Cowork on the side for everything that doesn't fit inside that boundary.

Sources