Copilot Cowork Costs: Ten Habits That Keep Copilot Credits Under Control

Microsoft 365 Copilot Cowork went generally available on 16 June, and the free period went with it. The grace window for early adopters closed on 1 July, and every task Cowork runs now draws Copilot Credits from your tenant. If Cowork abruptly stopped working for your team this month, the likeliest explanation is that nobody configured usage-based billing before that deadline.

The conversation has moved on as a result. During the preview the question was what Cowork could actually do, which we covered in our look at Cowork as AI-supported task completion. The question now is how to get real value from it without a bill nobody agreed to. Most of the answer sits in working habits rather than admin settings, which is good news, because habits can be trained.

How Cowork billing actually works

Cowork sits on top of a Microsoft 365 Copilot licence. The licence covers Copilot Chat and Copilot inside Word, Excel, Outlook and Teams. Cowork’s multi-step task work is billed separately, per task, in Copilot Credits, because a two-minute summary and a forty-minute research job cost very different amounts to run.

Four things decide what a task draws: which model does the work, how much of your Microsoft 365 context it retrieves, which tools it calls along the way and how long the run takes. Microsoft’s planning guidance groups tasks into light at roughly 100 to 300 credits, medium at roughly 300 to 700 and heavy above that. At the metered rate of $0.01 a credit that puts a typical task between about $1 and $7, call it 75p to just over £5, with heavy multi-output jobs going further. Not alarming on its own. Across a firm running dozens of tasks a day, it adds up quickly.

One structural detail matters before anything else. Copilot Credits are pooled at tenant level and shared across Cowork, Copilot Studio, Dynamics 365 agents and Power Platform AI features. One balance, spent from several directions, governed centrally. What each of those workloads draws is set out on our Copilot Credits reference page. It is the same consumption question we raised in our first look at Copilot Studio workflows and billing, now arriving in everyday task work.

Ten habits that keep the bill sensible

1. Use Chat for questions and Cowork for work

If the job is a quick answer, a short draft or a simple summary, it belongs in Copilot Chat, which is covered by the licence you already pay for. Save Cowork for work you would genuinely hand to a colleague. Asking when the quarter’s VAT return is due is a Chat question. Building a first draft of a client’s year-end letter from last year’s file and this year’s notes is a Cowork task. Treating Cowork as a chatbot is the fastest way to pay per task for answers that were already free.

2. Check the credits you already hold

Because credits are a shared tenant currency, an organisation that already licenses Copilot Studio capacity may have credits sitting in the environment that Cowork can draw on. Look in the Microsoft 365 admin centre before connecting pay as you go billing. Buying new capacity while an existing pool sits unused is an easy mistake and an entirely avoidable one.

3. Buy credits the right way round

There are three purchase routes: the pay as you go meter, the monthly Copilot Credit Pack and the one-year Pre-Purchase Plan with its tiered discounts. The current prices, the discount tiers and the rules on expiry are kept up to date on our Copilot Credits reference page, so they are not repeated here.

The pattern that works for most firms is to start on the meter, measure real consumption for a couple of months, then cover the steady baseline with a pack or the Pre-Purchase Plan and leave pay as you go running as the overflow. Prepaid credits are consumed first and anything beyond them rolls to the meter automatically, so tasks do not stop mid-run. Committed credits that expire unconsumed are not a discount at all, so size any commitment to a quiet month rather than a busy one.

4. Scope the task before you hand it over

Cowork usage scales with the work you give it. More sources means more retrieval, more outputs means more generation and longer runs mean more spend. “Summarise the audit planning meeting for the Harrison year end and draft the follow-up email, using the transcript in this folder” costs a fraction of “find everything we have on Harrison and tell me what matters”. Same business goal, very different workload. Point Cowork at the exact files, name the outputs you want and keep the brief tight. Nothing else on this list saves as much as this habit.

5. Do not reach for the heaviest model by default

Where the model selector is available, the model is one of the biggest cost levers in Cowork. A meeting recap does not need the same horsepower as a multi-source risk analysis. Leave routine work on Auto and save the heavyweight models for tasks that earn them. The judgement is the one we set out in our guide to the Copilot model picker, and the options have just improved again with GPT-5.6 arriving across Copilot.

6. Approve the plan before the build

Before Cowork produces anything substantial, a board pack, a fee proposal, a management accounts commentary, ask it to show the structure, sources and assumptions first. Sign off the plan, then let it build. Once a run starts, context gets retrieved, tools get called and the meter moves. A polished version of the wrong document costs exactly the same as the right one.

7. Make /cost a habit

Type /cost in any Cowork task window and it shows the credits that task has consumed so far. Ask everyone with access to do it after every task for a fortnight and you will learn quickly what drives spend in your firm. Drafting is cheap. Deep research, deck building and long multi-step runs are not. Run a job once, check the cost, multiply by how often you would run it in a month and you have a budget built on evidence rather than guesswork. Cowork now also has an effort selector next to the model picker, and how hard the agent works is the other half of this habit.

8. Switch on only what the task needs

Before a run, check which sources, skills and plugins are enabled for the session. If the task needs three files, do not point Cowork at an entire SharePoint site.

There is a sensible order for where the work should happen too. If the job can be done from your Microsoft 365 context, keep it there. If Cowork has to reach an outside system that offers an API or MCP connection, a connector is the cleaner and cheaper route. Browser automation, where Cowork drives Microsoft Edge through web pages, is the last resort for portals and older systems with no connector at all. It is off by default for good reason. Every browser run is slower and heavier than the same work done natively, so treat it as a tool for work that genuinely lives in a web page rather than a default.

9. Stop bad runs early

If Cowork starts pulling the wrong files or building the wrong thing, do not politely wait for it to finish. Steer it mid-run, tighten the scope or stop it and rerun with a better brief. The most expensive output in Cowork is a beautifully finished version of the wrong work.

10. Turn repeat work into skills

Skills let you package instructions, context and process once, then reuse them without rewriting a long brief every time. This is where the compounding value sits for professional services firms. Month-end reporting packs, meeting preparation, proposal first drafts and client onboarding all follow a repeatable shape. Build the skill once and every future run is cheaper, faster and more consistent. A decent rule of thumb: if the team will run the same job three or more times, it belongs in a skill rather than a prompt someone retypes from memory.

The admin side, before wide rollout

A few things belong on the checklist before broad access. Usage-based billing has to be configured in the Microsoft 365 admin centre or Cowork simply will not run, which is why some tenants found it dead at the start of July. Once billing is live, the Cost Management dashboard gives you spending policies, limits and alerts at tenant, group and individual level, plus hard caps so nothing runs away quietly. Users who hit a limit can request more credits through an approval queue rather than being silently blocked. If the next thing on the meter is a Copilot Studio agent rather than Cowork, the three numbers to check before it goes live cover the same controls from the agent side.

Then roll out like you mean it. Start with a small pilot group on real scenarios. Teach people to scope tasks, because that habit saves more than every control in the dashboard combined. Review the usage reports weekly for the first month, look at what people actually ran and expand deliberately. If more autonomous agent work is on the roadmap, the same credits question follows you there, and our look at what Scout and Autopilots mean for professional services covers where that is heading.

Cost control in Cowork is mostly a set of trained habits, and building them is a working-habits job, from task scoping to spending policies. If agents are in scope and you want the credit consumption modelled before anything is committed, our Copilot Studio agents work starts there. You can also book a free consultation and we will start from the tasks your team actually runs.

Sources checked

Last checked: 30 July 2026.

• Copilot Cowork is now generally available
• Choose a model for Copilot Cowork
• Microsoft 365 Copilot overview