Microsoft made Copilot Cowork generally available worldwide on June 16. If you run IT or finance for a mid-market organization, this release changes two things at once: what your people can hand to Copilot, and what it costs you.
Most of Copilot has worked as an assistant: you ask, it drafts, and you finish the work. Cowork finishes the work itself. You describe a task and it runs the whole thing across Microsoft 365, then hands back a completed result. It drafts and sends email through Outlook, schedules and reschedules meetings, builds Word docs, Excel models, and PowerPoint decks, posts in Teams, searches across your tenant, and runs recurring prompts on a schedule. Tasks run in the cloud, so they keep going after a user closes the laptop.
That capability comes with two things your team has not dealt with from Microsoft before: a usage-based billing model your finance lead will want to plan for, and a set of admin decisions that land on IT before a single user touches it.
Cowork takes on complex, long-running, multi-tool tasks and hands back a finished output, not a recommendation. Microsoft cited a few examples from its preview program. One team compared nearly 4,000 files across two product versions, a job that would have taken weeks by hand. One sales lead pointed Cowork at a stalled pipeline and got back a ranked list of at-risk deals, each with the specific follow-up that had gone cold.
A few design choices sit behind that. Cowork grounds each task in your business context through Microsoft's Work IQ engine, so the output reflects your data instead of a generic guess. It runs inside your existing Microsoft 365 trust boundary. It uses more than one underlying model, so the system matches each task to the right one.
You stay in control the whole time. Before Cowork takes a sensitive action like sending an email or posting to a channel, it pauses and asks for your approval, with a risk indicator on medium- and high-risk steps. You can interrupt, steer, pause, or cancel while it works.
Bring this to your finance lead before you go further. Cowork requires the Microsoft 365 Copilot license you may already hold, and then bills on top of it based on usage.
Cowork bills in Copilot Credits, and each task's cost depends on four inputs: the models it uses, how much context it pulls, how many tool calls it makes, and how long it runs. Microsoft sorts real-world usage into light, medium, and heavy tasks, and a heavy task costs far more than a light one. Pay-as-you-go runs at $0.01 per Copilot Credit. Organizations that commit to a usage volume in advance can take a discounted rate through Microsoft's P3 option.
Your Microsoft 365 Copilot subscription is a fixed per-user, per-month cost. Cowork adds variable spend on top, and it moves with how much your teams use it. Set the controls before adoption ramps and you pay for value delivered. Skip that step and you find out the cost on next month's invoice.
Microsoft ships Cowork turned off. Your admins decide when to enable it, who gets access, and how much each person can spend. That gives you room to put structure in place before usage starts, rather than cleaning up after it.
The cost controls available at general availability are worth using on day one:
One transition note. Tenants that had at least one user in Microsoft's Frontier preview between March 30 and June 16 get a grace period and pay nothing for Cowork usage until July 1, 2026. If that applies to you, the window is short. Set your budgets before billing starts.
Cowork's prompts, responses, and generated files run through the Microsoft 365 controls you already operate. Sensitivity labels carry through end to end. At general availability, the protected surface covered audit logging, Data Security Posture Management, eDiscovery, Insider Risk Management, and Communication Compliance policies, with Data Lifecycle Management added on June 22 and Data Loss Prevention support to follow. The governance you built for Microsoft 365 extends to Cowork. You don't stand up a separate control plane for it.
Work through this before you enable it across the org:
This takes a plan, not heroics. Building that plan now costs far less than reverse-engineering it from an invoice in August.
We spend our days on the part most teams find painful: getting Microsoft AI into production with the licensing, governance, and cost controls right the first time. For Cowork, that means modeling your likely consumption against real workloads, structuring the licensing and budgets so spend stays predictable, setting the security and compliance surface to your standards, and rolling it out to the teams where it pays off first.
If Cowork is on your radar, or your CFO has already asked what those Copilot Credits will cost, let's get ahead of it together.