Copilot Cowork Is Pay-Per-Task — How to Control Spend

On June 16, 2026, Microsoft moved Copilot Cowork to general availability. It is the first M365 AI capability to introduce variable, per-task billing on top of a fixed license — and the most significant architectural shift in how Microsoft 365 Copilot delivers value since Copilot launched in 2023.

The distinction between regular Copilot and Cowork determines whether a task is free — included in the $30/user/mo license — or metered.

Regular Copilot is the assistant you work alongside. Cowork is the worker you hand a full task to — and it bills per task, not per seat.

Cowork charges for four things: the model it uses, the volume of data it processes, the number of actions it takes (each file created, email sent, or Teams post counts as an action), and how long the task runs. Microsoft's published illustrative ranges provide a planning baseline.

Illustrative ranges from Microsoft at the $0.01 pay-as-you-go rate. Actual costs vary with context volume, model selection, and number of files or messages created.

The practical decision rule: use regular Copilot — free with your license — for anything that ends in a chat response, a quick edit, or a single-document summary. Use Cowork when you need it to gather from multiple M365 sources, execute across several steps, and return a finished artifact — and when the task genuinely justifies the compute cost.

Typing /cost after a Cowork task completes shows exact credit consumption, making it straightforward to calibrate which workflows are worth the investment. For examples of how agentic M365 workflows translate to real-world ROI, see our Copilot agent case studies and the broader AI token economics framework.

Based on what we see across M365 deployments, three patterns emerge consistently when Cowork is enabled without governance in place.

Surprise bills before the first review cycle Cowork is off by default, but once enabled with no spending limits configured, credit charges accumulate immediately. Microsoft's Cost Management dashboard in the M365 Admin Center supports per-user spending caps, budget alerts, and hard limits that prevent overspending — but none of these are pre-configured. Organizations that enable Cowork as a feature flag without first setting thresholds typically encounter five-figure credit charges in the first month, most of which came from exploratory usage rather than high-value work.

Employees route free-Copilot tasks into Cowork Without user training, employees send tasks to Cowork that regular Copilot handles at no additional cost — inbox summaries, single-document edits, quick research questions. Each misdirected task burns credits unnecessarily. A clear "Cowork or Copilot" decision framework, communicated before rollout, eliminates the most common source of avoidable spend. The rule is simple: if the task produces a finished deliverable across multiple apps and data sources, it belongs in Cowork. If it ends in a chat answer or a single-document result, it belongs in regular Copilot.

No visibility into what data flows through each session Cowork inherits the user's existing M365 permissions — it can only access what that user can already access. But in an unscoped rollout, that still means access to the full breadth of a user's email, SharePoint, Teams messages, calendar, and file history. Without data scope governance aligned to your Purview policies and Agent 365 control framework, IT teams have limited visibility into what organizational data is being processed within each Cowork session.

Copilot Cowork's value proposition is real and measurable: autonomous multi-step work, grounded in your actual organizational data, with approval gates before sensitive actions. The organizations that capture that value without budget surprises do three things before enabling it: configure cost controls in the M365 Admin Center, define which workflows belong in Cowork vs. regular Copilot, and align data access scope to their existing governance posture.

The organizations that get it wrong enable Cowork as a feature flag, skip the governance layer, and discover the exposure at month-end.

At Seepath, we help M365 organizations deploy Cowork as a managed capability — not a feature toggle:

• Admin Center cost controls — spending limits, budget alerts, and per-user caps configured before first enablement
• Use case mapping — identifying which workflows genuinely justify Cowork investment vs. regular Copilot, and building the "Cowork or Copilot" decision framework for end users
• Governance alignment — scoping Cowork data access within your existing Purview policies and security posture

If your organization is evaluating Cowork as part of the Microsoft 365 E7 Frontier Suite upgrade, governance setup should be part of the readiness conversation — not a follow-on project after rollout.

Copilot Cowork doesn't expose your data or budget without warning — unless you enable it before deciding who can use it, for what, and up to what cost.

Request your Copilot Cowork Readiness Assessment →