Microsoft Copilot Cowork for MSPs: What it is, how it’s billed, and why you’re the gatekeeper

Microsoft has quietly shipped one of the biggest shifts in the Copilot story so far — and it lands squarely in the lap of Cloud Solution Providers.

Two new agentic experiences, Copilot Cowork and the Work IQ API, are now live under a new usage-based (consumption) billing model, measured in Copilot Credits. For partners, this is more than another SKU — it changes who controls access and who captures the upsell.

If you’re a Microsoft CSP with customers running Microsoft 365 Copilot, this is for you.

What is Copilot Cowork?

Copilot Cowork is Microsoft’s new agentic experience that carries out tasks on a user’s behalf across Microsoft 365. Instead of asking Copilot to draft something and copying the output, users describe what they need in natural language and Cowork does the work — sending emails, scheduling meetings, creating documents, posting in Teams and managing files.

It runs in the browser at m365.cloud.microsoft and in the Microsoft 365 Copilot desktop app. Under the hood, it’s designed for long-running, complex tasks grounded in Work IQ, Fabric and Dynamics 365 data.

Sitting alongside it is the Work IQ API — a workplace intelligence layer that continuously turns signals from Microsoft 365 and connected business systems into agent-ready context. It’s the plumbing that makes Cowork (and future agents) genuinely useful.

How it’s billed: pay-as-you-go in Copilot Credits

This is the part most customers will not have seen before from Microsoft Copilot.

• Cowork uses a usage-based billing model, measured in Copilot Credits.
• Activities like model responses, tool and skill calls, image generation and browser tasks all count toward consumption.
• Billing is pay-as-you-go by default.
• Customers can pre-purchase discounted credits via a Copilot Credit Pre-Purchase Plan (P3) or use existing prepaid capacity packs. Prepaid credits are consumed first, then usage continues on pay-as-you-go.

In plain English: it’s no longer a per-seat conversation. It’s a consumption conversation — closer to how Azure is sold.

How it’s licensed

A Microsoft 365 Copilot licence is required as the entry point.Anthropic must be enabled in the tenant, because Cowork uses Anthropic models as a subprocessor.Licences enable access; the actual AI work is billed on a pay-as-you-go basis.

The catch: only the CSP can switch it on

Here’s the moment that matters for MSPs.

When a CSP-managed customer opens the AI experiences enabled by usage-based billing screen in the Microsoft 365 admin centre, they don’t get a setup button. They get this message:

“Your organisation is managed by your solution provider. Copilot credit setup for organisations managed by a solution provider must be set up by your provider. Contact your provider to enable consumption-based AI services for your organisation.”

Translation: no provider setup = no Cowork, no Work IQ API, no new agent experiences.

If you’re the CSP, you are the gatekeeper. Full stop.

How to deploy Cowork for your customers

Once you’ve set up Copilot credits in Partner Center for the tenant, the admin path inside the customer’s tenant looks like this:

1. In the Microsoft 365 admin centre, go to Copilot → Cost Management → Get Started and activate the default spending policy to enable usage-based billing.
2. Control discoverability via Copilot → Settings → “AI experiences enabled by usage-based billing” to govern whether users see Cowork across Microsoft 365.
3. If Cowork is discoverable but billing isn’t enabled, end users can request access in-app, and admins review and approve based on policy, cost and compliance.

How to keep billing under control

The good news: this is not a runaway-cost story if you set it up properly.

The Cost Management dashboard lets you:

• Allocate credits and set policy-based access and limits.
• Set a monthly spending limit per policy, plus an optional per-user monthly limit so no single user can burn the lot.
• Use budgets, alerts and hard caps to track usage and prevent overspending. When a limited budget is hit, users lose access until credits reset on the first of the month.
• Define email alerts at chosen usage thresholds.
• Scope policies to specific groups, users or services.

There’s also a Cowork cost estimator available to model expected credit usage before rollout — handy for setting customer expectations before they switch it on.

Why this matters for MSPs

Three things are worth saying out loud:

• You become the gatekeeper. Your customers literally cannot enable this without you. That’s a conversation worth having proactively, not reactively.
• It opens a consumption-based revenue stream, not just per-seat Copilot. The economics look more like Azure than M365.
• It’s a natural upsell into the Copilot, Agent and Purview conversations you’re already having. Governance, spend control and compliance are now part of the AI pitch — and that plays to MSP strengths.

What to do next

Set up Copilot credits / consumption-based AI in Partner Center for tenants that need it.

Map which customers are ready for Cowork and Work IQ API use cases — start with those already on Microsoft 365 Copilot.

Build the spend guardrails first. Lead with monthly limits, per-user caps and alerts so the customer feels in control from day one.

Talk to Leader Cloud. We’ll help you scope, position and bill it across your base.

Talk to Leader Cloud

If you’d like a hand getting Copilot Cowork enabled for your customers — or just want to walk through the Partner Center setup with someone — our cloud team can help.