Financial implications of Cowork
Billing structure
Copilot Cowork requires an active Microsoft 365 Copilot user subscription license, and then usage is billed based on Copilot Credits. This can be done through pay as you go at $0.01 per credit without commitment, or through a P3 annual commitment with a lower rate per credit. A prepaid Copilot Credit Capacity Pack is also available, with 25,000 credits per month for $200.
The cost of each task depends on four inputs. The model used, the volume of retrieved context, tool calls, and runtime.
Task categories. Light, Medium, and Heavy
Microsoft derived three task patterns from Frontier program data. They are not fixed boxes, but indicative calculations for budget planning.
| Category
|
Characteristics
|
| Light |
Small number of knowledge sources, limited reasoning, one output or less |
| Medium |
More sources, structured reasoning, two or more outputs |
| Heavy |
Broad context aggregation, deep reasoning, many outputs |
These categories are complemented by four user personas with estimated monthly consumption. The estimates are based on Frontier program data as of May 27, 2026, and assume the Anthropic Opus 4.8 model.
| Persona |
Light |
Medium |
Heavy |
Total prompts |
Estimated consumption in credits per month |
Estimated price at $0.01 per credit |
| Corporate Knowledge Worker |
22 |
11 |
5 |
38 |
~20 750 |
~$207,50 |
| Customer-Facing Knowledge Worker |
17 |
13 |
5 |
35 |
~21 125 |
~$211,25 |
| Technical Worker |
12 |
9 |
14 |
35 |
~41 000 |
~$410,00 |
| Managers and Senior Leaders |
13 |
6 |
3 |
22 |
~12 125 |
~$121,25 |
Source. Microsoft CustomerCoworkEstimator, aka.ms/CustomerCoworkEstimator
Why the Technical Worker persona is the most expensive
The Technical Worker persona does not have significantly more prompts. It has 35 per month, fewer than the Corporate Knowledge Worker with 38. But 14 of them are heavy. At the same time, $350 of the total $410 monthly cost comes from heavy tasks. The calculation is 14 heavy prompts times roughly $25, which equals $350. That is about 85 percent of total cost from one category. Fourteen heavy tasks across 21 working days is less than one per day. Even so, it is a conservative baseline that an active technical worker will probably exceed.
The asymmetry. Opus 4.8 included in chat vs. $25 for a heavy Cowork task
This asymmetry matters. The same model, Opus 4.8, is included in Copilot Chat. Delegating a heavy task to Cowork on the same model costs roughly $25, which equals 2,500 credits at $0.01 per credit. What changed is not the model. What changed is who is doing the work, how the work is orchestrated, which tools are needed, and how long it runs.
Scheduled tasks. The number the estimate does not show
The estimator models only interactive prompts. These are tasks that a user starts manually. It does not model scheduled tasks. Yet automation is one of Cowork’s key capabilities. A daily morning briefing, preparation 30 minutes before every meeting, a weekly pipeline summary, or a monthly competitive intelligence report. These tasks run regardless of whether the user is at the computer, and they consume credits at the same rate as interactive tasks.
Example. Daily email summary with suggested replies. For a leader who receives hundreds of emails per day, Cowork aggregates a high volume of data, evaluates priorities, and proposes context aware replies across threads. That is a heavy task at roughly $25 per run. With 22 working days per month, the calculation is 22 times $25, which equals $550 per month from a single automation. That is 4.5 times the entire modeled monthly cost for the Managers and Senior Leaders persona, which is $121.25.
In model scenarios that also include scheduled tasks, real consumption can be significantly higher than the baseline estimate. This is not an official Microsoft forecast. It is a practical warning that scheduled tasks can change the economics of the entire deployment.
Copilot Studio as another usage layer
Copilot Cowork is not the only usage layer. Organizations running Copilot Studio agents must also consider additional items that consume credits.
| Component
|
Price
|
| Tool call, such as prompt, flow, connector, MCP, or REST API |
5 credits per call |
| Agent flow actions |
13 credits per 100 actions, or 0.13 per action |
| Autonomous trigger, such as a scheduled or event based run without a human in the loop |
25 credits per run |
| Work IQ API for custom agents, from June 16 |
$0.20 to $1.50 per query |
Note. Native Work IQ grounding inside a Cowork task is included in the task price. Work IQ API is charged only for custom builds outside Cowork.
The Cowork estimator and the Copilot Studio estimator at microsoft.github.io/copilot-studio-estimator model different things. Organizations running both, which means any serious AI deployment on Microsoft, need both to understand the full bill.
Estimate vs. reality. What to tell the CFO
The right approach is not to take an average persona, multiply it by all users, and send the result to leadership. Example. 100,000 users in one persona produces a number above $20 million per month. That will trigger a predictable reaction, such as freezing the rollout or scheduling a crisis meeting, but it is real math applied to an unrealistic input.
A proper estimate must reflect the real distribution of roles. Use all four personas in the estimator, not one. Add a line for scheduled tasks. Then pressure test the estimate against the value actually delivered.