Copilot Cowork Costs: 10 Habits to Keep Copilot Credits Under Control

Microsoft 365 Copilot Cowork went generally available on 16 June, and the free ride ended with it. The grace period for early adopters closed on 1 July, and every task Cowork runs now consumes Copilot Credits from your tenant. If Cowork suddenly stopped working for your team this month, it is almost certainly because nobody configured usage-based billing before the deadline.

That changes the conversation. During the preview the question was what Cowork could do, which we covered in our practical guide to Cowork. Now the question is how to get real value from it without a bill nobody signed off. The good news is that most of the answer comes down to working habits rather than technical configuration.

Key takeaways

• Cowork bills per task in Copilot Credits. Microsoft's planning guide puts most tasks between 100 and 700 credits, which is roughly 60p to £5 a task at UK rates.
• Four things drive the cost of a task: the model used, the context retrieved, the tools called and how long the run takes. Your team can influence all four.
• Credits are pooled at tenant level and shared with Copilot Studio, Dynamics 365 and Power Platform, so check what you already have before paying twice.
• There are three ways to buy credits: a pay as you go meter priced in US dollars at $0.01 each, monthly capacity packs of 25,000 credits at £153.80 on the UK price list or an annual prepaid plan discounted up to 20 per cent. Committed credits expire, so measure before you commit.
• Admins get spending policies, alerts and hard caps in the Microsoft 365 admin centre. Set them before wide rollout, not after the first awkward invoice.

How the 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 in Copilot Credits, because a two-minute summary and a forty-minute research job cost very different amounts to run.

Every task draws credits based on four things: 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 groups tasks into light (roughly 100 to 300 credits), medium (roughly 400 to 700) and heavy (700 plus). On UK pricing that puts a typical task somewhere between about 60p and £5 in credits, with heavy multi-output jobs going beyond that. Not frightening on its own, but it adds up fast across a firm.

One detail worth knowing: Copilot Credits are pooled at tenant level and shared across Cowork, Copilot Studio, Dynamics 365 agents and Power Platform AI features. One balance, governed centrally.

Ten habits that keep the bill sensible

1. Use Chat for questions, Cowork for work

If the task is a quick answer, a short draft or a simple summary, use Copilot Chat. It is covered by the licence you already pay for. Save Cowork for work you would genuinely hand to a colleague. Asking when this quarter's VAT return is due belongs in Chat. Pulling together a first draft of a client's year-end letter from last year's file and this year's notes is a Cowork job. Treating Cowork as a chatbot is the fastest way to burn credits on work that was already free.

2. Check the credits you already have

Because credits are a shared tenant currency, organisations that already license Copilot Studio capacity may have credits sitting in their environment that Cowork can draw on. Check the Microsoft 365 admin centre before connecting pay as you go billing. Paying for new capacity while an existing pool sits unused is an easy mistake to make and an easy one to avoid.

3. Pick the right way to buy credits

There are three purchase routes and the right one depends on how predictable your usage is.

Pay as you go is metered at $0.01 per credit. Microsoft quotes this meter in US dollars and bills it through your Azure subscription in pounds at Microsoft's exchange rates, so there is no fixed sterling rate to quote. No commitment, billed monthly in arrears, and the right starting point while you learn your usage.

Capacity packs are £153.80 per tenant per month for 25,000 credits on Microsoft's UK price list, which works out at about 0.6p per credit and roughly 20 per cent cheaper than the meter. As a rule of thumb a pack pays for itself once you use around 20,000 credits a month. The catch is that unused credits do not roll over, so a pack sized to your peak rather than your baseline is money lost every quiet month.

The Pre-Purchase Plan, known as P3, is a one-year prepaid pool with volume discounts of up to 20 per cent. Same catch: unused credits expire at the end of the term, and a discount you cannot consume is not a discount.

The sensible pattern for most firms is to start on pay as you go, measure real consumption for a couple of months, then cover the steady baseline with packs or P3 and leave pay as you go running as the overage safety net. Prepaid credits are consumed first and anything beyond them rolls to the meter automatically, so tasks do not stop mid-run. Prices are Microsoft's list at the time of writing and your agreement may differ, so check before you commit.

4. Scope the task before you hand it over

Cowork usage scales with the work. More sources means more retrieval, more outputs means more generation and longer runs mean more spend. "Summarise the Henderson audit planning meeting and draft the follow-up email, using the transcript in this folder" costs a fraction of "find everything we have on Henderson 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.

5. Don't reach for the heaviest model by default

Where the model selector is available, the model you pick is one of the biggest cost levers in Cowork. A meeting recap does not need the same horsepower as a multi-source risk analysis. Let Cowork choose automatically for routine work and save the heavyweight models for tasks that genuinely deserve them. We compared the current options in our GPT-5.6 piece.

6. Ask for 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. Approve the plan, then let it build. Once a run starts, context gets retrieved, tools get called and the meter keeps moving. 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 to see 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 task once, check the cost, multiply by how often you would run it each month and you have a real budget number instead of a guess.

8. Only switch on what the task needs

Before running work, 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 also a sensible order for where the work should happen. If the job can be done with your Microsoft 365 context, keep it there. If Cowork needs to reach an outside system and that system has an API or MCP connection, a plugin or connector is the cleaner and cheaper route. Browser automation, which lets Cowork drive 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, and every browser run is slower and heavier than the same work done natively. Useful when the work genuinely lives in a web page, wasteful as a default.

9. Stop bad runs early

If Cowork starts using 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. For professional services firms this is where the compounding value sits. 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 your team will run the same job three or more times, it belongs in a skill rather than a prompt someone rewrites from memory each time. We covered how skills and plugins scale across a firm in our Cowork, Agent 365 and E7 explainer.

For IT teams and practice managers

A few things belong on the checklist before wide 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 stopped working at the start of July. Once billing is on, 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.

Beyond the controls, roll out like you mean it. Start with a small pilot group working on real scenarios. Teach people to scope tasks, because that one habit saves more than anything else on this list. Review the usage reports weekly for the first month, gather feedback and expand deliberately. Microsoft publishes solid adoption resources for Cowork, including champion guidance and starter scenarios, and they are worth using rather than reinventing.

At IQIT we help UK firms get real value from Copilot, from hands-on training to pilots that prove where Cowork pays for itself before you commit budget. If you want these habits trained into your team rather than left to chance, get in touch.