Copilot Cowork has a fourth billing meter now, and if your organisation hasn’t configured usage-based billing yet, access may already be suspended.
At a Glance
1. A Fourth Meter Just Went Live, and the Deadline Already Passed
Copilot Cowork credit tiers: Copilot Cowork went generally available on 16 June 2026. It runs agentic tasks, multi-step work that used to sit with a person, across Microsoft 365. Microsoft billed it as the next stage of Copilot: not a chat window, but something that goes and does the work.
What got less attention is the billing model underneath it. Cowork introduced Copilot Credits, a task-based consumption meter that sits on top of three billing structures IT teams already juggle: Agent 365 ($15/user/month standalone, or bundled into Microsoft 365 E7 at $99/user/month), Copilot Studio consumption, and Azure AI Foundry usage. Credits are the fourth line on that bill, and they are priced per task, not per seat.
Here is the part that should have every finance and IT leader checking their tenant today. Microsoft set 1 July 2026 as the date by which usage-based billing needed to be configured. Organisations that hadn’t set it up by then don’t get a grace period; they get suspended Cowork access. If your tenant crossed that deadline without a configured billing plan, your Cowork rollout has already stalled, not because of adoption, but because nobody actioned a billing admin task.
2. What Light, Medium, and Heavy Actually Cost
Microsoft sorts every Cowork task into one of three tiers based on credit consumption:
| Tier | Credits | Cost per task |
|---|---|---|
| Light tasks | roughly 100 to 300 credits | $1 to $3 |
| Medium tasks | roughly 400 to 700 credits | $4 to $7 |
| Heavy, multi-output tasks | 700 credits or more | $7 and climbing |
Under pay-as-you-go, each credit costs $0.01. A prepaid commitment tier (P3) is available for organisations that want a volume discount, but it requires forecasting consumption in advance, which is exactly where most IT teams are currently flying blind.
What decides which tier a task lands in? Four factors: the model the task runs on, how much context it pulls into the job, how many tools or connectors it calls, and how long it runs. A short summarisation task and a multi-step research-and-draft task that touches five connectors are not the same bill, even if a user perceives them as “asking Copilot to do something” in both cases.
The tenants that get burned by Copilot Credits won’t be the ones running too many tasks. They’ll be the ones who never built a way to see which tasks were expensive in the first place.
3. Where the Budget Actually Leaks
License sprawl used to mean seats nobody used. Consumption sprawl means tasks nobody tracked. The two problems rhyme, but consumption is faster and less visible. A seat sits there quietly until an audit finds it. A heavy task runs, bills, and is gone in seconds, with no obvious line item pointing back to which department, project, or employee triggered it.
Admins do get controls: spending limits and hard caps at the tenant, group, and individual user level, set through the Cost Management dashboard in the Microsoft 365 admin centre, with configurable alerts at chosen thresholds. That’s a real tool. But a cap is a backstop, not a forecast. By the time a hard cap trips, the department it stopped has already lost the task it needed mid-quarter.
4. Where TeamsFox Already Fits This Problem
TeamsFox customers already right-size Microsoft 365 licenses using the same discipline this new meter demands: visibility first, forecasting second, control third.
Our license right-sizing capability tracks assignment against actual usage and flags waste before it becomes a renewal surprise. That same tenant-wide visibility extends naturally to a consumption meter like Copilot Credits: track which teams, projects, or users are generating heavy-tier tasks, forecast monthly spend before the invoice lands, and catch a runaway agent workflow before it burns through a quarter’s credit allocation.
Customers already using TeamsFox for license right-sizing see 30% average license cost reduction and 60% less time spent on manual admin. The same tenant-wide visibility that finds unused licenses is the visibility that catches a credit-hungry agent workflow before finance does. Run this discipline before your next Copilot readiness review and the credit meter stops being a surprise.
5. Three Things to Check This Week
- Confirm your tenant has usage-based billing configured. If Cowork access has already paused, this is job one, not a nice-to-have.
- Set spending alerts at the group level, not just the tenant level. A single department running heavy research tasks can burn budget the rest of the org never sees.
- Ask which teams are using Cowork for light tasks that could just as easily run in standard Copilot, no credit meter attached. Not every job needs the agentic tier.
Conclusion
Copilot Cowork’s fourth meter is not a footnote. It is a live budget line, billed per task, that most finance teams have not modelled yet, and the 1 July configuration deadline means some organisations are already finding that out the hard way.
The organisations that handle this well will be the ones that treat Copilot Credits the way they should have always treated license spend: as something to forecast, not something to discover on an invoice. Tiered task costs, spending caps, and usage alerts are the tools Microsoft has given IT teams. Using them well takes the same visibility discipline TeamsFox customers already apply to license and storage spend.
This is not a new problem wearing a new name. It is the license sprawl problem, moved from annual renewals to per-task billing, and moving faster because of it.
If your tenant hit the 1 July deadline without a configured billing plan, or if nobody in your organisation can currently say which department burns the most Copilot Credits, that gap is worth closing this week, not at the next license review.
Frequently Asked Questions
What happens if my organisation hasn’t configured Copilot Credits billing?
Cowork access is suspended for tenants that hadn’t set up usage-based billing by 1 July 2026. Configuring billing in the Microsoft 365 admin centre restores access.
How much does a Copilot Cowork task cost?
Light tasks run $1 to $3, medium tasks $4 to $7, and heavy multi-output tasks $7 or more, based on Microsoft’s $0.01-per-credit pay-as-you-go rate.
Is Copilot Cowork Credit tiers the same as Agent 365 licensing?
No. Agent 365 is a per-seat governance licence ($15/user/month, or bundled into E7). Copilot Credits is a separate, task-based consumption meter that sits alongside it.
Can we cap Copilot Credit spending?
Yes. Admins can set spending limits and hard caps at the tenant, group, and user level through the Cost Management dashboard, with configurable usage alerts.
Does TeamsFox manage Copilot Credit consumption directly?
TeamsFox doesn’t have a dedicated Copilot Credits product today. Our existing license visibility and cost-forecasting capabilities extend naturally to this consumption model, the same way they already track and right-size license spend.
Ready to see this in your tenant? Run a free TeamsFox M365 analysis, no contract, no account changes. You will see your licence, storage, and governance exposure within 30 minutes.
About TeamsFox
TeamsFox is a Franco-German Microsoft 365 management and optimisation platform trusted in 20+ countries across Europe, MENA and Asia. TeamsFox customers see an average 30% reduction in license costs, 60% reduction in admin time, and 40% reduction in storage costs. Headquartered in Düsseldorf, Germany, TeamsFox gives IT and finance teams the tenant-wide visibility and control that native Microsoft tools and one-off scripts cannot sustain.