Copilot Cowork reached general availability on 16 June 2026, and it changes the shape of the Microsoft 365 Copilot bill. Everything before it was a fixed per-user licence: predictable, budgetable, boring in the best way. Cowork is metered. Every task consumes Copilot Credits, and the cost of a task depends on what the task turns out to require. In admin communities the reaction has been consistent, and one line sums it up: left unmanaged, Cowork alone will balloon costs. The concern is legitimate, and Microsoft has shipped the controls to address it. The catch is that the controls only help if they are configured before enablement, not after the first surprising invoice.
The good news is that Microsoft made the safe path the default: Cowork is off by default at GA, and an admin has to enable it deliberately. That makes this one of the rare Microsoft 365 rollouts where IT genuinely gets to set the guardrails first. This guide covers what Cowork is, how the metering works, and the checklist Frontrow works through with clients before switching it on.
What Cowork does that chat-based Copilot doesn't
Microsoft 365 Copilot as most users know it is conversational: prompt in, response out, human in the loop at every step. Cowork is different in kind. A user hands it a piece of work, a brief with inputs and an expected output, and Cowork executes it as a long-running task in the cloud: planning, using multiple tools and files, iterating, and coming back with completed work product rather than a draft paragraph. Think building the first cut of a report pack from source spreadsheets, or working through a folder of documents against a checklist.
That difference is exactly why the billing model changed. A chat exchange is a bounded unit of work. An autonomous task is not: one task might run briefly and touch two files, another might retrieve broad organisational context, call a dozen tools and run for a long time. Microsoft prices that variability through consumption, and Cowork requires the Microsoft 365 Copilot user subscription licence as its entry point, with credit consumption billed on top.
How the metering actually works
Cowork usage is denominated in Copilot Credits. Under pay-as-you-go, a credit is priced at US$0.01 (Microsoft lists consumption pricing in US dollars; checked August 2026). There is also a prepaid commitment option that discounts credits bought in advance. What a given task costs in credits is driven by four factors: the model the task uses, how much organisational context it retrieves, how many tool calls it makes, and how long it runs.
The honest implication: nobody can tell you in advance what 'a month of Cowork' costs for your organisation, because the unit of consumption is the task and tasks vary. Two teams with identical headcount can produce very different bills. Forecasting comes after measurement, which is why the sequence below puts limits and a contained pilot ahead of broad enablement. One transitional detail worth knowing: tenants that had users in the Frontier preview program (30 March to 16 June 2026) had billing suspended until 1 July 2026, so their first metered month is July. If early invoices looked low, that grace period is part of the reason.
The pre-enablement checklist
Cowork's admin controls live in the Microsoft 365 admin center, under the cost management area for Copilot Credits alongside the enablement settings. Before turning Cowork on for anyone, work through these in order:
- 1Confirm licensing. Cowork sits on top of the Microsoft 365 Copilot licence, so the population that can use it is at most your Copilot-licensed population. Decide which of those users are in scope now.
- 2Choose the billing model. Pay-as-you-go is the sensible starting point for a pilot: no commitment, and the meter teaches you your consumption profile. Consider prepaid commitment only once a few months of real usage data exist to size it against.
- 3Set a tenant-level spending cap. Decide the maximum the organisation is prepared to spend on Cowork this quarter and set the hard cap to match. A cap that pauses tasks at the limit is recoverable; an uncapped surprise is a harder conversation.
- 4Set group and user limits. Monthly spending limits can be applied per billing policy and per user, which stops one enthusiastic user or team consuming the entire allocation. A modest per-user monthly limit is a reasonable pilot default, then adjust against observed usage.
- 5Configure alerts before caps are reached. Set notification thresholds (for example at 50 and 80 per cent of budget) so finance and IT hear about a consumption trend with time to act, rather than discovering it when tasks stop.
- 6Scope the pilot group. Enable Cowork for a named group, never tenant-wide on day one. More on choosing that group below.
- 7Decide the credit-request process. Users can request more credits from inside Cowork when they hit a limit. Decide now who receives those requests, who approves, and on what basis, or the limits become a queue of ad hoc exceptions.
- 8Book the review. Put a 30-day review in the calendar before enablement: consumption by user, group and feature, cost per completed task, and a decision on whether to expand, hold or tighten.
Who should get it first
The right pilot cohort is not the most senior people or the loudest requesters. It is 10 to 20 users who share three characteristics: they already use Microsoft 365 Copilot regularly (so the licence prerequisite is met and the behaviour change is incremental), their work contains genuinely delegable tasks with a repeatable shape (report assembly, document review, data tidy-ups), and they will tolerate rough edges and report honestly. A pilot built from finance analysts and operations coordinators usually teaches more than one built from executives.
Just as important is deciding what the pilot is measuring. Credits consumed per completed task, and whether the task output was actually used, are the two numbers that determine whether Cowork earns a wider rollout. An organisation already tracking Copilot adoption has a head start here: unused Copilot licences and unmeasured Cowork credits are the same disease in two forms.
Monitoring consumption once it's live
After enablement, the cost management dashboard in the Microsoft 365 admin center becomes the operational surface: usage reporting broken down by user, group and feature, budget tracking against the limits you set, and the alert stream. Three habits keep it healthy:
- Weekly during the pilot, skim consumption by user and feature. Outliers appear fast, and they are usually either the best learning in the pilot or a runaway pattern worth a conversation.
- Reconcile the first full invoice against the dashboard's numbers. Confirm the caps behaved the way you expected, and that the billing model (pay-as-you-go versus any prepaid pool) is being drawn down the way you assumed.
- Treat limit increases as decisions, not reflexes. When a team hits its cap doing valuable work, raising the limit is easy to justify with the dashboard open. Without it, every request is a guess.