Copilot Cowork reached general availability on 16 June 2026, moving out of Microsoft's Frontier early-access program and into full release. If you have been watching Cowork from the sidelines, or already using it through Frontier, this is the point at which it becomes part of the standard Copilot picture.
What General Availability Means
General availability changes two things: it opens Cowork up to eligible Copilot customers more broadly, and it switches on usage-based billing. While Cowork was in Frontier, its task work was free. Now it is billed on usage, measured in Copilot Credits, a different shape of cost from the flat per-user licence most people are used to, which may be one of the first things people notice. This billing model applies to Cowork and the Work IQ API today, with more agents and services expected to follow over time. If you are new to Cowork itself, our introduction to Copilot Cowork covers what it is and how it works.
If you were already running Cowork through Frontier, you may have noticed that the task work has not been billed yet. That is thanks to a grace period, and exactly who gets it comes down to Frontier history. Tenants with at least one user active in Cowork between 30 March and 16 June 2026 are not billed until 1 July 2026. So if you were on Frontier, you have a short window to make deliberate decisions about billing and guardrails before charges begin, and it is worth using.
What's New in This Release
Billing is not the only thing general availability brought, though. A few other additions are worth knowing about, even at a glance:
- Partner plugins. Cowork can now connect to a set of partner services, including monday.com and Miro today, with others such as Adobe and Atlassian on the way. These let Cowork draw on information from tools beyond Microsoft 365.
- Browsing through Edge (in preview). Still part of the Frontier early-access program rather than general availability, this lets Cowork use a local Edge browser, where enabled and within your organisation's policies, to gather information from the web as part of a task.
- Model choice. A model picker lets you balance the quality of a task against what it costs to run. At general availability the choices are Anthropic's Opus 4.8 and Sonnet 4.6, with some options, such as GPT-5.5, available only in Frontier.
If your interest is in what more Cowork can now do, the items above give you the shape of it.
How Copilot Cowork Billing Works
The first thing to understand is that your existing Microsoft 365 Copilot licence does not change. That per-user seat still covers Copilot Chat and Copilot inside Word, Excel, PowerPoint, Outlook and Teams, and it remains the predictable, flat part of the bill. It is also the entry point, because a user needs that Copilot licence before Cowork can be enabled for them.
What is new sits on top of the seat. Cowork's longer, multi-step task work is the part that carries a usage cost, and it flexes with how much your team hands to it. Spend tracks effort: occasional light tasks barely move the needle, while heavy, all-day use of long multi-output jobs adds up to real consumption.
Microsoft prices each Cowork task from four inputs: the model it uses, how much organisational context it retrieves, how many tool calls it makes, and how long it runs. Add those together and you get the number of credits a task consumes. Under pay-as-you-go, each Copilot Credit is priced at USD $0.01.
Each Cowork task is priced from four inputs: the model used, context retrieved, tool calls and runtime.
As a rough sense of scale, Microsoft's general-availability guidance described three common task shapes observed during Frontier. Treat the figures below as illustrative estimates rather than fixed billing tiers, because the actual credits a task uses will vary with the model and the work involved.
| Task shape | What it looks like | Illustrative cost (PayGo) |
|---|---|---|
| Light | A small number of knowledge sources, limited reasoning, one or fewer outputs | Roughly USD $1 to $3 |
| Medium | Multiple sources, structured reasoning, two or more outputs | Roughly USD $4 to $7 |
| Heavy | Broad aggregation, deep reasoning, many outputs | Roughly USD $7 and above |
These ranges assume a high-end model. Choosing a lighter model lowers the cost, and Microsoft has signalled that cost will drift down over time as model costs come down and Cowork gets better at matching the right model to each task.
The Three Ways to Pay
When you enable usage-based billing, you choose how your organisation is billed for Copilot Credit usage. There are three approaches, and the right one depends on how settled and predictable your usage is.
| Option | How it works | Suits you when |
|---|---|---|
| Pay-as-you-go (PayGo) | You are billed for credits as you use them, at USD $0.01 per credit, with no upfront commitment. | Usage is new or variable and you want to observe real consumption before committing. |
| Prepaid (P3) | You commit to a volume of credits in advance, in exchange for a volume discount. | Usage is predictable and you can forecast an annual number with confidence. |
| Hybrid | Prepaid (P3) credits are consumed first, and any usage beyond them rolls automatically to pay-as-you-go. | You have a reliable baseline of usage plus occasional bursts above it. |
A useful way to think about it is that PayGo gives you flexibility, P3 gives you a discount for predictability, and Hybrid lets you size a prepaid floor while keeping headroom for the months that run hot.
Is Usage-Based Pricing Worth It?
It is fair to ask whether usage-based pricing is worth it. It helps to separate two things Cowork delivers. The first is the obvious one: the work it performs. The second is easier to overlook but matters more at enterprise scale: Cowork runs inside your security and governance perimeter, grounded in your Microsoft 365 data behind enterprise authentication, isolated to your tenant, and governed by Purview, data-loss prevention, data-residency and admin spending controls. That second layer is what an enterprise relies on, and how much it matters depends on what your organisation needs.
What an Admin Needs to Do Before Billing Starts
Cowork is gated by usage-based billing, which means that until an administrator sets it up, there is nothing for users to consume. The setup is a guided flow in the Microsoft 365 admin centre, and it is worth doing carefully, because one of the choices is difficult to reverse later (more on that below).
You will need the Global Administrator or Billing Administrator role to complete these steps.
1. Make Cowork discoverable. In the Microsoft 365 admin centre, go to Copilot > Settings and turn on the setting for AI experiences enabled by usage-based billing. This is off by default and controls whether users can see Cowork.
2. Open Cost Management and go to Configuration. Go to Copilot > Cost Management and open the Configuration tab. This is where you set up usage-based billing for your organisation and turn Cowork on.
3. Choose how you want to pay. Decide whether you want to buy prepaid credits or set up a spending policy on pay-as-you-go (or draw on existing capacity you already hold). You also select the default subscription for your organisation here. If you do not have an Azure subscription, you can create one from here, or the system can create one for you using the billing account already linked to your tenant.
4. Set your credits. What you do here depends on which option you chose. For pay-as-you-go, you set a monthly spending limit for the policy, which is the credit allowance it can consume each month. You can run without a cap, but for a first rollout we generally suggest setting a deliberate limit so spend cannot run away while you learn your real usage. For prepaid (P3), you instead buy a volume of credits up front through the Prepaid Credits option, which shows the price for the number of credits you select, so you can see the cost and any volume discount before you commit.
5. Scope who can use it. Decide whether the policy covers all users or specific groups. Starting with a pilot group of the people who will actually work closely with Cowork is a sensible way to observe representative consumption before opening it more broadly.
A note worth flagging before you commit: once a billing method is set for a spending policy and the policy is created, Microsoft does not allow that billing method to be changed. To switch it later, you have to delete the policy and create a new one. It is a good reason to decide your starting approach deliberately rather than adjusting it after the fact.
How to Measure and Control Spend
Setting up billing is only half the picture. The other half is the visibility and the guardrails that keep usage-based pricing comfortable rather than nerve-wracking, and this is where the Cost Management dashboard earns its place.
Consumption reporting. On the Consumption tab, you can review usage three ways. The Users view shows each user's credit limit, usage, last activity and session count. The Groups view shows usage and limits per group. The Agents and services view breaks usage down by service, including Cowork and the Work IQ API. Together these give you clear accountability for where credits are going.
Budgets, caps and alerts. Limits can be set at three levels: the whole tenant, specific groups, and individual users. This means you can tailor allowances to how teams actually work, giving a heavier team or individual more headroom while keeping lighter usage to a smaller allocation. Alerts can be set at chosen thresholds so nothing comes as a surprise. When a cap is reached, metered services pause until credits renew at the start of the next month. If that happens partway through a task, the task does not simply fail: the user can request additional credits from inside Cowork for an administrator to review.
Per-task visibility for users. The people doing the work can also see what a task costs, rather than discovering it on an invoice. Typing /cost in the task window after a run returns the Copilot Credits the session has used so far. It makes a useful budgeting habit: run a representative task once, read its cost, then multiply by how often you expect to run it in a month to turn a guess into a defensible figure.
Sizing usage before you commit. If you would like to model likely spend before turning anything on, Microsoft provides a Customer Cowork Estimator. It lets you estimate credit usage for your organisation by mapping your people to common task patterns, the light, medium and heavy shapes described earlier, so you can put a realistic range around a month of usage. You can download it here: Customer Cowork Estimator (Microsoft, .xlsx). The estimator is a planning aid rather than a guarantee, and the most reliable number is always your own observed usage.
Model Choice Is a Cost Lever
The model a task runs on is one of the four inputs to its credit cost, and it is the one users control most directly. The picker offers a default orchestrator (Auto) alongside a lighter everyday model and a heavier model for complex work, with a further option available in Frontier. Because the picker's labels describe what each model is good at, not what it costs, the lowest-cost choice is not always obvious.
The gap is real. The same task can cost meaningfully more on a heavier model than on a lighter one, sometimes several times more, for output of similar quality. The option that reads as the safe, middle-of-the-road choice can turn out to be the most expensive of the lot.
A sensible default is to leave the picker on Auto for everyday work, which tends toward the lower-cost end, lean on the lighter model for routine tasks, and save the heavyweight model for the genuinely complex, high-stakes work that warrants it.
Knowing When to Reach for Cowork
Now that Cowork's task work carries a cost, a small discipline pays off: matching the tool to the job. The same request can often be handled in more than one place, and Cowork is not always the right one. Reaching for a lighter tool when a quick answer will do keeps credit spend where it belongs, on the work that genuinely needs an agent.
A simple way to think about the three options:
| Tool | What it is | Reach for it when |
|---|---|---|
| Copilot Chat | Fast, reactive AI grounded in your data, included in the Copilot seat | You need a quick answer, a draft, a summary, or a single piece of research in one sitting |
| Copilot Cowork | An agent that executes whole multi-step processes across your Microsoft 365 apps, billed on usage | You need an end-to-end deliverable that spans several apps, files or sources |
| Microsoft Scout | An always-on agent that works proactively in the background (newer, and rolling out through Frontier) | You want ongoing work tracked and moved along day after day without being asked |
The practical takeaway is that Chat covers a great deal of everyday work at no extra cost, so Cowork is best saved for the multi-step jobs that earn their credits. Used that way, the usage-based model rewards deliberate use rather than punishing it.
A Practical Starting Point
At this stage, most organisations cannot yet predict their usage. If that is you, a pragmatic approach is to start on pay-as-you-go with a sensible monthly cap and a pilot group of people who will actually work closely with Cowork, run for a month, and let the Consumption tab tell you what your real baseline looks like.
Once that baseline is visible, the right commitment becomes much clearer. If usage is steady and predictable, prepaid (P3) earns its discount, provided your usage is high enough to clear the minimum credit volume prepaid requires you to commit to. If you see a reliable floor with occasional spikes above it, a hybrid setup lets you capture the discount on the baseline while keeping pay-as-you-go headroom for the busy months. The point is to let real data drive the commitment, rather than committing before you can see the pattern.
Where Hypergen Fits
Moving to usage-based billing is less a technical change than a governance one. The configuration takes minutes; the part that determines whether Cowork stays comfortable is the thinking behind it, which spending model fits your usage, what caps and alerts make sense, and how you read consumption once people start running real tasks.
In why we're now recommending Microsoft Copilot, we set out how Cowork is much of the reason we started recommending Microsoft 365 Copilot to Australian mid-market organisations. Usage-based billing simply adds a cost-governance step to getting that value.
If you would like to get more from Cowork itself, we run a half-day Copilot Cowork training course in Melbourne, Sydney and Adelaide.
Working out how to roll out Copilot Cowork billing?
We help Australian organisations choose the right spending model, set sensible caps and alerts, and read consumption once people start running real tasks.
Pricing and billing details are accurate as of June 2026 and reflect Microsoft's published figures. Dollar amounts are Microsoft's listed USD rates, so confirm Australian pricing against your own Microsoft agreement. These details change over time, so treat them as a snapshot rather than a fixed quote.