On 16 June 2026, Microsoft made Copilot Cowork generally available worldwide. If you use Microsoft 365 Copilot, this is one to pay attention to — not because of what it does (which is genuinely impressive), but because of how you pay for it. Cowork is the first piece of Copilot that bills on consumption rather than a flat monthly fee, and the way that bill behaves is worth understanding before it lands.
What Copilot Cowork actually is
Most of Copilot to date has been assistive — it drafts, summarises and answers inside Word, Excel, Outlook and Teams. Cowork is different. It's an agent that takes on complex, long-running, multi-step tasks and runs them end to end, returning a finished result rather than a draft. Think "compare four thousand files across two product versions" or "work through a stalled sales pipeline and tell me which deals are at risk and why" — the kind of job that used to eat a person's week.
It runs in the cloud (so it keeps working when your laptop is closed), stays inside your Microsoft 365 trust boundary, and requires a Microsoft 365 Copilot licence to use.
How the pricing works
This is the part to understand. Cowork does not sit under your flat per-user Copilot licence. It is billed on usage, measured in a unit Microsoft calls Copilot Credits. The cost of any given task is calculated from four things: the model it uses, how much of your organisation's context it has to retrieve, how many tools it calls, and how long it runs.
In practice Microsoft groups tasks into three rough tiers:
- Light — a few sources, limited reasoning, one output or fewer.
- Medium — multiple sources, structured reasoning, a couple of outputs.
- Heavy — broad aggregation, deep reasoning, many outputs.
There are two ways to pay: pay-as-you-go, priced at $0.01 per Copilot Credit, or P3, where you commit to a usage volume up front in exchange for a discount. Cowork is also off by default — an administrator has to switch it on and decide who gets access.
The 1 July deadline: billing for Cowork technically began at GA on 16 June. But tenants that used it during the Frontier preview (30 March–16 June) get a grace period and won't be billed until 1 July 2026. If that's you, free usage is about to become billable usage.
Why consumption pricing needs a plan
Usage-based pricing is fundamentally fair — you pay for what you actually use, and a genuinely useful heavy task is worth paying for. But it's also exactly the kind of bill that creeps quietly when nobody's watching it. A flat licence is predictable; a consumption meter is not, unless you put structure around it. The businesses that will be happy with Cowork in three months are the ones that set it up deliberately now.
My recommendation for Swiss businesses
Here's what I'm advising clients to do before they turn Cowork loose.
1. Ring-fence the cost in a dedicated Azure subscription
When you enable Cowork billing, you're asked to choose an Azure subscription to charge it to. So create a new subscription with its own valid payment method first — it then shows up as an option, and you point Cowork at it. The result: all Copilot consumption lands in one place, easy to watch in Azure Cost Management and simple to attribute to a budget, rather than disappearing into your general cloud spend. I set it up exactly this way for a regulated Swiss financial-services client, and it makes the monthly number painless to track.
2. Set the guardrails before you switch it on
The admin centre now has proper cost controls: spending limits at tenant, group and user level, customisable usage alerts, and usage reporting broken down by user, group and feature. Configure these first — not after the first surprising invoice.
3. Budget by who actually needs it
You don't need to enable Cowork for everyone on day one. Start with the handful of people whose work involves heavy, repetitive analysis, give them a sensible cap, and expand once you can see real usage and real value.
The Swiss compliance angle
Worth noting for anyone in a regulated environment: Cowork operates inside your existing Microsoft 365 controls. Prompts, responses and generated files inherit your sensitivity labels and are covered by audit logging, eDiscovery, Data Lifecycle Management and Insider Risk Management. That's reassuring — but it's not a substitute for deciding, deliberately, what data your agents are allowed to touch. The same nDSG and data-residency questions that apply to the rest of your M365 tenant apply here too.
What to do before 1 July
If you trialled Cowork under Frontier, your free ride ends on 1 July — so put the controls in place this week. If you haven't enabled it yet, you have a clean slate: set the budget and the guardrails first, then switch it on for a small group. Either way, the goal is the same — make the spend visible and capped before usage ramps, so you get the value without the surprise.
If you'd like a hand setting this up properly — the dedicated Azure subscription, the spending limits, the monitoring, and a sensible rollout plan — that's exactly the kind of work I do. The first 30 minutes is free.