Usage-based billing for Microsoft 365 Copilot Cowork is live, and the deadline to have it configured, July 1, 2026, isn’t far off. If you’ve already read through what changed and why, this is the part that actually matters operationally: how do you turn this on in a way that controls cost without strangling the value Cowork is supposed to deliver? 

The honest answer is that Microsoft built genuinely solid controls for this. The problem isn’t that the guardrails don’t exist. It’s that none of them are on by default, and the order you configure them in matters.

Copilot Cowork Spending Limits: 2026 Admin Setup Guide 

To control Microsoft 365 Copilot Cowork spending, go to the Microsoft 365 admin center, select Copilot, then Cost Management, and create a spending policy scoped to a pilot group with a monthly per-user credit limit, alert thresholds, and deliberate model selection, before enabling access broadly.

The rest of this guide walks through each setting in the order that prevents the most common cost overruns. 

Why Sequencing Matters Here 

Microsoft built real cost controls into Cowork’s Cost Management dashboard, documented in Microsoft Learn’s guidance on managing usage-based billing. The risk isn’t that the guardrails don’t exist. It’s that none of them are active by default, and most rollout problems trace back to enabling broad access before configuring limits, rather than the reverse. 

Cowork itself is off by default in every tenant. No task runs until an admin enables usage-based billing and activates a spending policy, per Microsoft Learn’s Cowork admin governance documentation. 

Step 1: Enable Usage-Based Billing and Choose a Payment Model

Navigate to Microsoft 365 admin center → Copilot → Cost Management → Get Started. 

If you’re billing at meaningful scale, connect an Azure subscription during this step – that’s what actually carries the billing relationship. 

Step 2: Build a Scoped Spending Policy 

This is the step most likely to be skipped under deadline pressure, and the one with the most direct cost impact. A spending policy defines who can use Cowork and how much they can spend. Two scoping options: 

Within the policy, configure: 

• Monthly spending limit per user: Optional in the console, but explicitly recommended by Microsoft. Without it, one heavy user can consume an entire team’s credit pool. 

• Group and tenant-level caps: Prevent one department’s heavy month from absorbing budget meant for the wider organization. 

• Alert thresholds: Set the percentage of budget that triggers notification, and choose recipients. Alerts repeat weekly once triggered until the month resets or the limit is adjusted, functioning as an ongoing signal rather than a single notice. 

Step 3: Route Tasks to the Right Model 

Model use is one of the four direct inputs into a task’s credit cost. At GA, Cowork supports Anthropic’s Opus 4.8 and Sonnet 4.6, with a Microsoft-built cost-optimized model (Cowork 1) arriving soon, and GPT-5.5 available to Frontier customers. 

This single habit – not defaulting every task to the most capable model – has more impact on monthly credit consumption than almost any other configuration choice. 

Step 4: Govern Plugins and Connectors Deliberately 

Plugins extend what Cowork can reach: Miro, Monday.com, Box, Fabric IQ, Templafy, and others. Each plugin call is a tool-call cost input. Admins control which plugins are available and to whom – enable only what your pilot group’s actual workflows require, and expand deliberately as use cases prove out, rather than turning on the full catalog by default. 

Step 5: Monitor the Consumption Tab Weekly 

The Cost Management dashboard has two views: 

• Overview tab: Real-time snapshot of total credit usage and remaining capacity. 

• Consumption tab: Usage broken down by user, group, and feature. This is where to look for unexpectedly expensive task types (often a sign that a task is pulling more context or making more tool calls than necessary) and whether spending limits reflect real usage rather than an initial guess. 

Check this weekly for the first four to six weeks of any rollout. 

Learn more about usage-based billing and cost management for Copilot Credit here.  

Rollout Checklist 

1. Enable usage-based billing; start with Pay As You Go

2. Connect Azure billing if managing spend centrally

3. Create a spending policy scoped to a pilot group, not all users

4. Set a per-user monthly limit, plus group and tenant caps

5. Configure alert thresholds and recipients

6. Enable only the plugins the pilot group needs

7. Default routine tasks to lighter models; reserve frontier models for complex work

8. Review the Consumption tab weekly for the first 4–6 weeks

9. Expand access based on observed data, not assumption

The Two Failure Modes to Avoid 

Configuring too late. Teams that enable broad access to drive adoption, then look for cost controls after the first invoice raises questions, are reconstructing governance under pressure instead of setting it up calmly in advance. 

Configuring too conservatively. Spending limits set far below actual organizational need don’t reduce risk – they suppress the workflows Cowork was deployed to improve. The goal is usage that maps to measurable outcomes, not minimized usage for its own sake. Getting that balance right depends on which workflows in your organization are actually worth delegating, which is harder to determine from a generic checklist than from a review of your real tenant data. 

Get a guided walkthrough of your tenant 

Quisitive is a Microsoft Frontier Partner, and we’re offering existing and prospective clients a guided session to walk through Cowork’s Cost Management setup directly in your tenant: spending policies, model selection, plugin governance, and a usage review tailored to how your teams actually work.

Rather than configuring this from a generic checklist, we’ll help you set guardrails calibrated to your organization’s real workflows, so Cowork drives measurable value from week one instead of an unmanaged cost line.