Copilot Cowork Billing: How to Control Usage Costs Before They Spiral

Your first full quarter of Copilot Cowork billing is in, and the number may not be what you expected. Microsoft’s usage-based credit model means every agentic task your team runs has a variable cost, from $0.70 for a quick status update to $15 or more for deep data analysis. Without spending limits configured, a team of 20 active users can generate a $4,000 monthly bill that nobody approved.

The good news: Microsoft built real admin controls for this. The bad news: most SMBs haven’t configured them yet. This post walks through how the billing actually works, what realistic costs look like, and exactly which controls to set in your M365 admin center before the next invoice surprises you.

How Credit-Based Billing Works

Copilot Cowork uses a consumption model rather than the flat per-user fee you’re used to with standard Copilot licenses. Every task Cowork executes consumes credits at $0.01 per credit. The number of credits varies based on the complexity of the task, which AI model is called, how much context Cowork pulls from your M365 environment, and how many tool calls are required to complete the work.

That last variable is the one that catches people off guard. When a user asks Cowork to “put together a quarterly review deck from our latest financials,” the agent doesn’t just generate slides. It searches SharePoint for the relevant documents, reads through multiple files, pulls data into a structured format, generates the presentation, and may iterate on formatting. Each of those steps consumes credits, and the total adds up fast.

Microsoft offers two billing options:

• Pay-as-you-go charges your Azure billing account at the end of each billing cycle based on actual consumption. There’s no upfront commitment, but there’s also no discount and no natural cap on spending.
• Prepaid credit plans let you purchase blocks of credits in advance at a reduced rate. You get cost predictability and volume savings, but unused credits expire at the end of the commitment period.

For most SMBs, pay-as-you-go is the default because it’s what you land on if you don’t actively choose otherwise. That’s also the option most likely to produce bill shock.

What Tasks Actually Cost

The per-credit price is simple. The hard part is predicting how many credits a given task will consume. Microsoft publishes ranges, but the actual consumption depends on your data environment and the specificity of the request.

Here’s what we’ve seen across client environments:

Light tasks (70-200 credits, roughly $0.70-$2.00):

• Summarizing an email thread
• Drafting a short reply based on context
• Looking up a specific document in SharePoint
• Creating a daily briefing from your inbox and calendar

Medium tasks (400-600 credits, roughly $4.00-$6.00):

• Compiling a meeting agenda from multiple Teams conversations
• Researching a topic across your M365 data and producing a one-page brief
• Scheduling a multi-attendee meeting across complex calendars
• Generating a formatted report from existing spreadsheet data

Heavy tasks (1,500+ credits, $15.00 and up):

• Deep cross-environment analysis pulling from SharePoint, Teams, email, and OneDrive
• Multi-step research tasks that involve reading dozens of documents and synthesizing findings
• Complex document generation that requires iterating on structure and pulling data from multiple sources
• Running scenarios against financial data in Excel with multiple variables

The math gets real quickly. If five members of your leadership team each run two medium tasks and one heavy task per day, that’s roughly $70/day, or about $1,500/month, just from five users. Scale that to 20 active users and you’re approaching $4,000-$6,000/month depending on usage patterns. That’s on top of your existing M365 licensing costs.

This isn’t a reason to avoid Cowork. The productivity value is real for the right tasks. But it does mean you need to manage it like any other variable-cost service.

The Admin Controls You Should Configure Today

Microsoft provides granular spending controls in the M365 admin center. The problem is that none of them are turned on by default. Until you configure them, every licensed user can run unlimited agentic tasks with no cap.

Tenant-level spending limits

This is your most important guardrail. In the M365 admin center under Billing > Cost Management, you can set a monthly spending cap for Cowork credits across your entire organization. When the tenant hits the limit, Cowork stops executing new tasks until the next billing cycle or until an admin raises the cap.

Set this based on what you actually budgeted for AI usage, not on a number that feels high enough to never trigger. The whole point is to create a circuit breaker. If you’re not sure where to start, set it at 150% of your current monthly spend for the first two months, then adjust down once you have usage data.

Group and per-user limits

Below the tenant cap, you can assign spending limits to security groups or individual users. This is where governance gets practical. Your executive team may need higher limits for complex research tasks, while your operations staff may only need light scheduling and email assistance.

Create two or three tiers based on actual role needs:

• Standard users (email, scheduling, simple document tasks): $20-30/user/month
• Power users (research, reporting, multi-step workflows): $75-100/user/month
• Unrestricted (approved executives or roles with a clear business case): tenant limit only

Assign users to the appropriate tier through security groups, which makes it easy to adjust as you learn actual usage patterns.

Threshold alerts

Even with caps in place, you want early warning before someone hits their limit. Microsoft supports threshold alerts that notify admins when spending reaches a percentage of the configured limit, such as 50%, 75%, and 90%. Configure these to go to whoever manages your M365 environment, whether that’s an internal admin or your managed IT provider.

These alerts turn an invisible cost into a visible one. Without them, the first sign of overspending is the invoice.

Who Gets Access to Expensive Tasks

Spending controls handle the budget side, but there’s a governance question underneath: who in your organization should be running agentic tasks at all, and how do you decide?

This connects to the broader AI governance framework that every business using AI tools needs. For Cowork specifically, consider three questions:

Which roles benefit from agentic automation? Not every job needs an AI agent. Identify the roles where Cowork actually saves meaningful time, such as executives who spend hours on email triage, project managers who compile status reports manually, or finance teams who pull data from multiple sources for reporting. Give those roles access first.

What tasks justify the cost? A $15 deep-research task that replaces two hours of manual work is a good investment. The same task used to answer a question someone could have found in a five-second SharePoint search is waste. Help your team understand the cost model so they make reasonable decisions about when to use Cowork and when to use regular Copilot Chat, which is included in your M365 Copilot license at no per-task cost.

Who approves changes to access tiers? As teams discover more uses for Cowork, requests for higher spending limits will come in. Decide now whether that approval runs through IT, through a department head, or through finance. Having a process prevents ad hoc limit increases that quietly inflate the budget.

Document these decisions in a short internal policy. It doesn’t need to be long. One page covering who has access, what the spending tiers are, how to request changes, and who monitors the dashboard is enough. This is the same kind of governance discipline we covered in our guide on building an AI usage policy for businesses adopting AI tools across the organization.

Why Your MSP Should Be Managing This

Microsoft’s Cost Management dashboard is genuinely useful, with trend charts, per-user breakdowns, and forecasting based on current consumption rates. The problem is that most SMB admins don’t have time to check it regularly, and the controls described above require someone who understands both the M365 admin center and your organization’s AI usage patterns.

This is the kind of ongoing operational work that fits naturally into a managed IT engagement. Your MSP can configure the initial spending controls, monitor the dashboard as part of regular tenant management, adjust limits based on actual usage data, and flag anomalies before they turn into budget surprises. They can also evaluate whether a prepaid credit plan would save you money based on your consumption history, since that decision requires enough data to forecast accurately.

If your IT provider isn’t already talking to you about Cowork cost management, ask them about it. If they don’t know what the M365 Cost Management dashboard is, that’s a signal about how closely they’re managing your environment.

For businesses across Dallas-Fort Worth and our other Texas and Oklahoma markets, this is a conversation we’re having with clients right now. The organizations that set these controls in Q3 are the ones who won’t be surprised by their Q4 invoices.