Copilot Cowork Is GA
— Here’s What Actually Changed (Rapid Research Brief)

Executive Summary

Key Takeaways

• Copilot Cowork is not M365 Copilot. Cowork is an agentic system for complex, long-running, multi-tool tasks. M365 Copilot is real-time assistance within Office apps. They serve different use cases.
• Usage-based billing via Copilot Credits. Pricing is calculated from four inputs: model use, context retrieval, tool calls, and runtime. Requires the M365 Copilot USL ($30/user/month) as a prerequisite.
• Extensible via Skills, Plugins, and MCP. Cowork can be extended with custom skills, out-of-the-box plugins, and MCP servers for organizational integrations.
• Cloud-hosted with enterprise security. Tasks run in the cloud within the M365 trust boundary, with existing compliance policies enforced. No local storage, no data leakage.
• 30-40% cheaper than Claude Cowork with M365 connector. Microsoft’s testing showed Copilot Cowork cost advantages on average, with a new fine-tuned Cowork1 model coming soon.

Key Findings

1 What Copilot Cowork Actually Is (and Isn’t)

Copilot Cowork is an agentic system designed for complex, long-running, multi-tool tasks. You define the work and Cowork runs it end-to-end, returning a completed result — not a draft or recommendation. It is distinct from M365 Copilot (real-time in-app assistance) and from Copilot Chat (conversational Q&A). Key differentiators: cloud-hosted execution (tasks keep running even when your laptop is off), native Work IQ grounding in your organization’s data, enterprise-grade security within the M365 trust boundary, multi-model design, and usage-based billing. [Source 1, 2]

Health system implication: Cowork is the right tool for workflows like batch-processing clinical documentation, comparing formulary data across versions, generating prior authorization packets from EHR data, or auditing claims across thousands of records — tasks that are too complex for a single prompt but don’t require a full-time developer.

2 Pricing: Copilot Credits and the Four-Input Model

Copilot Cowork requires the M365 Copilot USL ($30/user/month) as a prerequisite. Cowork usage is then billed on a usage basis denominated in Copilot Credits. The price for each task is calculated from four inputs: model use (which model and how many tokens), context retrieval (Work IQ grounding), tool calls (skills, plugins, browser), and runtime (duration of execution). Microsoft’s testing showed Copilot Cowork was 30-40% cheaper per prompt than Claude Cowork with the M365 connector. A new fine-tuned model, Cowork1, will further reduce costs. [Source 2, 3]

Health system implication: The usage-based model means you pay for what you use, not what you might use. Admin controls allow setting credit limits per user/department. This is more predictable than per-seat enterprise licensing for occasional high-complexity tasks. Start with a small pilot group, track credit consumption, and scale based on ROI data.

3 Extensibility: Skills, Plugins, and MCP Support

April Dunnam walks through the extensibility model in detail. Skills are reusable instructions and playbooks for Cowork — essentially prompt templates that encode organizational knowledge. Plugins extend Cowork with external tools, MCP servers, and organizational integrations. Out-of-the-box plugins include browser use, branded PowerPoint templates, and more. MCP (Model Context Protocol) support allows Cowork to connect to any MCP-compatible server, dramatically expanding its tool surface. [Source 1, 3]

Health system implication: Skills are the mechanism for encoding institutional knowledge into Cowork. Build a library of health-system-specific skills: discharge summary generation, prior auth documentation, medication reconciliation, care gap analysis. Each skill encodes your clinical standards and compliance requirements. MCP support means Cowork can connect to EHR APIs, lab systems, and scheduling platforms.

4 Security and Admin Controls

Security is a first-class feature: Cowork operates within the M365 trust boundary, with protections that align to existing organizational policies and controls. Cloud hosting means files are not stored locally. Admin controls include the ability to manage which users have access, set credit limits, and monitor usage. Cowork inherits the same compliance certifications as M365 (HIPAA, SOC 2, etc.). [Source 1, 2]

Health system implication: The security model is the strongest argument for choosing Copilot Cowork over alternatives. HIPAA compliance is inherited from the M365 trust boundary. Data never leaves the tenant. Admin controls allow granular governance: limit which departments can use Cowork, set credit caps, and audit all usage. This addresses the compliance gap identified in the previous AI Learning System brief.

5 M365 Copilot vs. Copilot Cowork: When to Use Which

April Dunnam provides a clear decision framework: M365 Copilot is for real-time, in-context assistance within Office apps (drafting in Word, analyzing in Excel, summarizing in Teams). Copilot Cowork is for complex, multi-step, long-running agentic tasks that may span multiple tools and data sources. The key question: does this task require real-time human collaboration, or can it be delegated to an agent to run end-to-end? [Source 1, 3]

Health system implication: Train clinical staff to distinguish between these two modes. M365 Copilot for in-the-moment assistance (writing a note, analyzing lab results). Cowork for batch processes (auditing 500 claims, generating 50 discharge summaries, comparing two drug formularies). The workforce development program should teach both tools as complementary, not competing.

6 Copilot Cowork vs. Anthropic Cowork: The Competitive Landscape

April Dunnam compares the two: both are agentic systems, but key differences include pricing (Copilot Cowork is 30-40% cheaper per Microsoft’s testing), security model (M365 trust boundary vs. Anthropic’s infrastructure), and ecosystem integration (native M365/Work IQ vs. API-based connectors). The new Cowork1 fine-tuned model will further differentiate on cost. [Source 1, 2]

Health system implication: For organizations already on M365, Copilot Cowork is the path of least resistance for security and compliance. For organizations with multi-cloud strategies, the comparison matters. The key is to avoid vendor lock-in: build skills and agent workflows that are conceptually portable, even if the execution layer is Microsoft today.

Risks, Gaps & Uncertainty

• Usage cost unpredictability. While usage-based billing is flexible, it can also be unpredictable. Health systems need robust credit monitoring and alerting before scaling.
• Skill quality dependency. Cowork’s effectiveness depends on the quality of Skills and Plugins. Poorly designed skills will produce poor results at scale. Skill authoring is a new competency most organizations lack.
• M365 dependency. Cowork requires the M365 Copilot USL, which means the full M365 ecosystem. Organizations on other productivity suites are locked out.
• HIPAA nuances. While Cowork inherits M365 compliance, specific healthcare workflows (e.g., PHI handling in agentic tasks) need careful configuration and auditing.
• Rapid evolution. The product is GA but still evolving rapidly. Skills, plugins, and pricing may change. Training programs need to be designed for continuous adaptation.

Recommended Next Actions

Annotated References