
Copilot Cowork bills on top of the Microsoft 365 Copilot licence, in Copilot Credits that cost $0.01 each on pay-as-you-go, or less through P3, where you commit to a usage volume in advance in exchange for a discount. You cap the spend with spending policies in the Microsoft 365 admin center, under Copilot > Cost Management: a monthly limit for each policy, an optional monthly limit for each user inside it, and email alerts at a threshold you choose. Microsoft set the price in its general availability announcement of 16 June 2026, and documents the policies on Microsoft Learn under managing AI experiences enabled by usage-based billing.
Cowork is off by default. Microsoft's announcement says it "requires the Microsoft 365 Copilot User Subscription License (USL)", and users are then billed for the tasks they run. Before anyone can use it, an admin has to enable usage-based billing and place the user in a spending policy that selects Cowork, according to Microsoft Learn's page on managing Copilot Cowork for your organization.
A task has no fixed price. In Microsoft's announcement, "the price for each task is calculated from four inputs: model use, context retrieval, tool calls, and runtime." The November 2026 Copilot Credits Guide names the same four as cost buckets (models, runtime, context and tools), and Microsoft Learn counts model responses, tool and skill calls, image generation and browser tasks toward your consumption. Users see what each task costs, in credits, as they run it.
For planning, the guide gives estimated credits for representative task types and calls them "rough planning estimates". Its method sizes your Cowork users by persona, estimates how many light, medium and heavy prompts each persona runs, and applies an average price per prompt. Microsoft's Copilot Credit Estimator, linked from the Learn page on managing Copilot Cowork, runs that model for you, and the guide says its estimators "do not guarantee final costs". The estimates in Microsoft's announcement assume Anthropic Opus 4.8. Where several models are available, users manage cost per task through the model picker, and an admin can restrict the models Cowork offers a policy's users with a model template.
Pay-as-you-go is $0.01 per Copilot Credit with no commitment, and the Azure subscription you connect as the billing method is billed for the credits used. The Copilot Credits Guide says credits "are pooled at the tenant level", and your total cost is the sum of the credits consumed across every supported experience.
P3, the Copilot Credit Pre-Purchase Plan, is "a one-year pay-upfront purchase option" in the guide's words. It comes in nine tiers, from 300,000 credits at a 5% discount to 300,000,000 credits at 20%, and unused credits expire at the end of the annual term. Microsoft Learn's page on Copilot Credit P3 adds that plans renew by default at the end of the one-year term and that "All purchases are final". P3 "is layered on top of pay-as-you-go", so when the prepaid credits run out, usage continues on a pay-as-you-go basis.
| Pay-as-you-go | P3 pre-purchase plan | |
|---|---|---|
| Price | $0.01 per Copilot Credit | From 300,000 credits at a 5% discount to 300,000,000 credits at 20% |
| Billing method | The Azure subscription you connect as the billing method | Pay-upfront purchase option |
| Commitment | No commitment | A usage volume you commit to for a year |
| Unused credits | Your total cost is the sum of the credits consumed | Unused credits expire at the end of the annual term |
| Credits run out | Billed for the credits used | Usage continues on a pay-as-you-go basis |
Start on pay-as-you-go. A P3 tier is a usage volume you commit to for a year, and Cowork's credits per task depend on your own mix of models, context, tools and runtime, so size P3 from your own pay-as-you-go usage in the Cost Management dashboard. Buy too much and the unused credits expire; buy too little and the rest bills at pay-as-you-go.
Microsoft's announcement lists "spending limits at the tenant, group, and user levels". On Microsoft Learn, each level is a setting of a spending policy, created in the Microsoft 365 admin center under Copilot > Cost Management, on the Configuration tab:
A policy's monthly limit can be left unlimited. With a limit set, "When users hit the limit, they lose access to agents and services for the rest of the month until credits reset on the first of the month", and the policy always spends prepaid credits before moving to pay-as-you-go (Microsoft Learn). Spending policies "don't reserve or allocate Copilot Credits to users or groups", so a group's limit caps what that group can spend from the tenant's pool and sets nothing aside for it.
From those two limits you can work out the most one policy can bill in a month. The ceiling is our arithmetic from Microsoft Learn's documented limits: the lower of the policy's monthly limit and the number of people in the policy times the per-user limit, at $0.01 a credit on pay-as-you-go (Microsoft, 16 June 2026). A policy with neither limit set has no ceiling. Microsoft Learn also says consumption and limits are evaluated asynchronously, so a user might start one or more tasks after reaching a limit before enforcement takes effect.
Alerts warn you before a limit stops anyone. On each policy you choose who gets an email when usage reaches a threshold, set as a credit amount or a percentage, and Microsoft Learn's page on setting up usage-based billing for Copilot Credits says the emails "continue daily until the monthly usage period resets or you adjust the spending policy." A policy with a per-user limit can also email each user at a threshold percentage you set, separately from the admin alerts.
A Global administrator or a Billing administrator activates usage-based billing and sets billing methods, according to the same set-up page. AI administrators and License administrators can edit spending policies, limits and alerts, but they can't create spending policies, and reader roles such as AI Reader and Global Reader see the consumption dashboards without changing anything.
"A low credit limit doesn't block access," Microsoft Learn warns in its page on access controls for Copilot Cowork. A spending policy is what grants access, so anyone in the scope of a policy that selects Cowork can use it, and "A policy with a limit of one credit still grants access." To keep someone out of Cowork, remove them from every spending policy that includes it.
A user who reaches their own limit loses access to agents and services until credits reset on the first of the month. They can request more credits from inside Cowork, and Microsoft Learn says they "don't default to other policies", so the system keeps them on their assigned policy. When a policy reaches its monthly limit, the users it covers lose access the same way for the rest of the month. When P3 credits run out, usage continues on pay-as-you-go.
A user in several policies for the same service gets one of them in full, chosen by the highest per-user limit, then the largest overall policy limit, then the most recently created policy, and Microsoft Learn says settings from the other policies aren't combined. A user who moves to another group comes under the new group's policy, and the credits they used under the old one still count against the new limit, so moving a user between groups doesn't reset their consumption.
On a Copilot Cowork rollout, we set the spending limits and approvals, agree spending policies per group, agree those limits with your finance team before rollout, and roll Cowork out one team at a time.
A Copilot Credit is the unit Microsoft bills Copilot Cowork in, priced at $0.01 on pay-as-you-go according to Microsoft's announcement of 16 June 2026. Each task uses a number of credits set by its model use, context retrieval, tool calls and runtime, and the Copilot Credits Guide says credits are pooled at the tenant level, so all of an organisation's usage draws on one pool.
No. Microsoft's announcement says Cowork requires the Microsoft 365 Copilot User Subscription License, and users are then billed on a usage basis for the tasks they run, in Copilot Credits. According to Microsoft Learn, an admin also has to enable usage-based billing and put each user in a spending policy that selects Cowork before that user can open it.
It depends on the task. Microsoft prices each task from its model use, context retrieval, tool calls and runtime, and its Copilot Credits Guide gives only rough planning estimates for representative task types. For a budget, Microsoft's Copilot Credit Estimator models your users by persona, their light, medium and heavy prompts and an average price per prompt, and the guide says its estimators do not guarantee final costs.
According to Microsoft Learn, a per-user limit must be at least 2,000 credits per user per month. The per-user limit itself is optional, though Microsoft recommends one to stop a single person from spending all available credits, and the policy's own monthly limit has to meet the required minimum for the users it covers.
No. Microsoft Learn says cancel and exchange operations aren't supported for Copilot Credit Pre-Purchase Plans and that all purchases are final, and the Copilot Credits Guide says unused credits expire at the end of the annual term. Plans also renew by default at the end of the one-year term, according to Microsoft Learn, so turn automatic renewal off if you do not want a second year.
No. Microsoft Learn says a spending policy is an access control as well as a budget, and that a policy with a limit of one credit still grants access to everyone in its scope. To keep a user out of Cowork, remove them from every spending policy that selects it. Limits are also enforced asynchronously, so a user might start a task after reaching a limit.
Planning a Copilot Cowork rollout? Book a discovery call, tell us which team goes first and which systems its work touches, and a senior partner scopes the connectors, plugins and spending limits with you.