Copilot Cowork Pricing: Tread Carefully

Microsoft Copilot Cowork Is Now Generally Available

What’s Happened

Microsoft has announced the general availability of Copilot Cowork — an agentic AI capability within Microsoft 365 that can execute complex, long-running, multi-tool tasks on behalf of users.

This represents a shift from AI assistance to AI execution — where work is completed end-to-end rather than simply drafted or recommended.

While now generally available, rollout and enablement remain controlled at tenant level, allowing organisations to adopt deliberately.

How the Billing Works (And Why It Matters)

Copilot Cowork uses a seat + consumption billing model:

Microsoft 365 Copilot licence required — your existing per-user monthly fee (~$30/user/month)
Usage billed additionally via Copilot Credits — based on tasks actually run
Charges based on model use, context retrieval, tool calls, and runtime

Microsoft has indicated pricing in the region of ~$0.01 per credit on a pay-as-you-go basis, with a pre-committed option (P3) available at a discount. Costs vary based on task complexity.

Task Complexity

Tasks can broadly be grouped into three types. These are indicative ranges, not formal fixed tiers — actual credit consumption will vary:

Task Type	Description	Est. Credits	Est. Cost (PayGo)
Light	Few sources, limited reasoning, one or fewer outputs	~100–300 credits	~$1–$3
Medium	Multiple sources, structured reasoning, two or more outputs	~400–700 credits	~$4–$7
Heavy	Broad aggregation, deep reasoning, many outputs	700+ credits	~$7+

Credit ranges assume Anthropic Opus 4.8. Microsoft’s upcoming Cowork 1 model is designed to handle everyday tasks at substantially lower cost.

The Four User Personas — And What It Could Cost

Microsoft has defined four user personas with distinct usage patterns. To illustrate potential spend, consider a hypothetical organisation of 100 users:

Persona	Count
Knowledge Workers	35
Customer-Facing Knowledge Workers	35
Technical Workers	15
Managers / Senior Leaders	15

A note on cost estimates

These figures are SAM Club modelling examples based on our understanding of Microsoft’s published pricing. Microsoft has confirmed the credit price (~$0.01/credit) and indicative credit ranges per task type, but has not published official per-persona task volumes. Actual costs will vary depending on how frequently users run Cowork tasks, which task types they use, and which model is selected. All figures are in USD — UK organisations should apply the prevailing exchange rate. We recommend using Microsoft’s own Customer Cowork Estimator to model your specific scenario. Pricing is correct at time of publication — check Microsoft’s current rate card before making budgeting decisions.

Illustrative cost ranges — SAM Club modelling examples only

Applying Microsoft’s published credit pricing and indicative credit ranges, annual Cowork costs for a 100-user organisation — and scaled to 1,000 users — could fall broadly in the following ranges:

Usage Scenario	Typical Pattern	Est. Annual Cost (100 users, USD)	Est. Annual Cost (1,000 users, USD)
Conservative	Mostly light tasks, occasional medium (~5 light + 2 medium/user/week)	~$17,000–$33,000	~$165k–$330k
Moderate	Mixed usage across all task types (~5 light + 5 medium + 1 heavy/user/week)	~$67,000–$133,000	~$665k–$1.3M
Heavy	Power usage, daily tasks across all types (~10 light + 8 medium + 3 heavy/user/week)	~$250,000–$415,000+	~$2.5M–$4.2M+

⚠️	These are Cowork consumption costs only — on top of M365 Copilot licence fees (~$30/user/month) and your underlying M365 licence. All figures in USD.

Use Microsoft’s Customer Cowork Estimator to model your own organisation’s scenario before enabling Cowork for any users.

What Guardrails Are Available?

Microsoft has shipped cost management controls at general availability:

Off by default — admins must actively enable Cowork per tenant and per user
Spend controls — spending limits at tenant, group, and user levels
Alerts and reporting — customisable usage alerts and usage reporting across all levels
Cost dashboards — visibility into what each task costs, with user-level credit requests
Pay-as-you-go or pre-committed pricing — flexibility or commitment discounts via P3

These controls are helpful — but they only work if someone is actively managing them.

⚠️ Our Advice: Tread Carefully

The arrival of consumption-based billing for AI features is a watershed moment for Microsoft 365. The SAM Club’s position is clear:

1. Pilot first

Cowork is off by default — use that to your advantage. Do not enable it broadly. Start with a defined pilot group, measure usage and value, then expand deliberately.

2. Set spending limits before you go live

Use the tenant, group, and user-level spending caps in the admin centre. Treat them like a corporate card limit — set them conservatively and review regularly.

3. Define who uses it and for what

Build an AI usage policy that sets out which roles have access to Cowork, what task types are appropriate, and what requires approval or is out of scope.

4. Measure value

Consumption billing only makes sense if you are tracking the return. Define what value looks like before you approve spend — time saved, errors reduced, outputs generated.

5. Optimise model choices

Cowork currently runs on Anthropic models (Opus 4.8 and Sonnet 4.6), with Microsoft’s own Cowork 1 arriving soon at lower cost. Model choice will be a meaningful cost lever as the ecosystem matures.

6. Review your existing Copilot licences first

If M365 Copilot licences are underused in your organisation, adding Cowork spend on top compounds the problem. Ensure you’re extracting value from what you already have.

UK, Ireland & Jersey: Data Residency — What You Need to Know

For clients in the UK, Republic of Ireland, and Jersey, the question of where your data goes when Cowork processes it is not straightforward — and it matters. The position is broadly similar across all three jurisdictions but with important nuances for each.

Your data storage — stays in your region

Copilot Cowork follows the same data residency model as Microsoft 365 Copilot. Your data — prompts, responses, and generated files — is stored in the same region as your M365 tenant. For UK, Irish, and Jersey-provisioned tenants, data at rest remains in that region. That part is not the concern.

Anthropic model processing — this is the issue for all three

When Cowork uses Anthropic models (Opus 4.8 or Sonnet 4.6) to process your tasks, that processing falls outside the EU and UK Data Boundary — for all three jurisdictions. Microsoft’s own documentation confirms that Anthropic models are explicitly out of scope for EU Data Boundary and in-country LLM processing commitments. Your organisational data — including content drawn from emails, files, and meetings — may be processed in the United States.

Jurisdiction	Governing Law	Anthropic Default	EU Data Boundary
United Kingdom	UK GDPR / Data Protection Act 2018	Off by default	Anthropic processing outside boundary
Republic of Ireland	EU GDPR (EU member state)	Off by default	Anthropic processing outside boundary
Jersey (Channel Islands)	Data Protection (Jersey) Law 2018 — GDPR-equivalent, EU adequacy status	Likely off by default — confirm with Microsoft	Outside EU Data Boundary. Seek specific advice.

Notes by jurisdiction

United Kingdom: UK GDPR applies. Anthropic is disabled by default for UK tenants. Enabling Cowork effectively requires enabling Anthropic processing outside the UK Data Boundary. Organisations should assess this against their UK GDPR obligations and any sector-specific requirements before proceeding.

Republic of Ireland: As an EU member state, full EU GDPR applies and Ireland falls within the EU Data Boundary framework. Anthropic is disabled by default. The DPC (Data Protection Commission) in Dublin is one of the EU’s most active regulators — Irish organisations in particular should ensure any decision to enable Anthropic processing is documented and assessed for GDPR compliance, especially regarding international data transfers.

Jersey: Jersey is a Crown Dependency and is neither part of the UK nor the EU. It operates under its own Data Protection (Jersey) Law 2018, which is broadly equivalent to GDPR and holds EU adequacy status. Jersey organisations are not covered by the EU Data Boundary framework directly, but the same underlying data transfer concerns apply — Anthropic processing outside the EU/UK is likely to require assessment under Jersey’s own international transfer rules. Jersey organisations should seek specific local compliance advice, particularly given the prominence of financial services in the island.

Microsoft’s contractual protections still apply

Across all three jurisdictions, Anthropic operates under Microsoft’s subprocessor framework. Microsoft’s Product Terms, Data Protection Addendum, and Enterprise Data Protection commitments remain in effect. Data is not unprotected — but the geographic boundary of processing is not guaranteed to remain within the EU, UK, or EEA.

Flex Routing — a separate but related issue

Separately, Microsoft’s Flex Routing feature can route standard Copilot LLM processing outside the EU Data Boundary during periods of high demand. This is independent of the Anthropic subprocessor question and affects UK and Irish tenants. Jersey tenants should also be aware of this. Admins should check and consider disabling Flex Routing in the Microsoft 365 admin centre if data boundary compliance is a requirement.

Action required before enabling Cowork — UK, Ireland & Jersey

1. Check the Anthropic subprocessor toggle in the Microsoft 365 admin centre — understand what you are enabling before switching it on.

1. Review and consider disabling Flex Routing (Settings → Organisation profile → Data location).

1. Assess whether your sector has specific data residency or processing obligations. Financial services, legal, healthcare, and public sector organisations should seek specific compliance advice before proceeding. Jersey financial services firms should consult with their compliance teams given JFSC expectations.

1. Document your decision — whether you enable or decline Anthropic processing, record the rationale as part of your AI governance and data protection records.

For further detail, refer to Microsoft’s official guidance: Data, Privacy and Security for Microsoft 365 Copilot and Anthropic as a subprocessor for Microsoft Online Services.

Billing Grace Period

Frontier preview customers (30 March – 16 June 2026) will not be billed until 1 July 2026. If this applies to your organisation, use this window now to put spend controls and governance in place.

More Information

Please contact us if you have any questions regarding Cowork or licensing in general.

Microsoft Copilot Cowork – Tread Carefully