On June 16, 2026, Microsoft moved Copilot Cowork out of preview and into general availability — and with it came a fundamental change in how enterprise AI gets priced. For months, hundreds of thousands of employees across the Fortune 500 had been delegating complex, multi-step tasks to Cowork at no extra charge. That era ended. Every task Cowork executes now draws from a pool of Copilot Credits, and those credits cost real money.
This is not a minor billing update. It is the first major consumption-based pricing model to land inside the Microsoft 365 stack — a stack that 400 million commercial users sit inside. Every enterprise IT leader, every CFO, and every COO with Microsoft licenses needs to understand what Cowork does, what each task actually costs, and what governance controls exist before a single user generates a surprise invoice.
What Copilot Cowork Actually Does
Before the pricing conversation, context matters. Most enterprise AI tools still operate as assistants — you prompt them, they respond, you take it from there. Cowork is different.
Cowork is an agentic system. You describe the outcome you want, and Cowork plans the steps, executes them across your Microsoft 365 environment, and hands you the finished deliverable. That means drafting and actually sending an email through Outlook. Building an Excel model grounded in your real data, not a generic template. Scheduling meetings by resolving actual calendar conflicts. Posting updates to Teams channels. Running recurring prompts on a schedule — for example, a weekly status report generated every Monday morning without you lifting a finger.
The technical underpinning is a multi-model architecture developed in collaboration with Anthropic. Microsoft claims this design keeps compute costs roughly 30 to 40 percent lower than comparable agent experiences. That efficiency gain is part of what makes usage-based pricing viable — but it also explains why lighter tasks stay affordable while heavy analytical work can run significantly higher.
The adoption numbers suggest this resonated quickly. According to Microsoft, more than half of the Fortune 500 was already using Cowork at the time of general availability. It was described internally as the fastest-growing preview feature Microsoft had ever shipped.
The Billing Model, Explained Plainly
Here is how the economics work, starting from the bottom up.
Layer one: you still need the base license. Copilot Cowork is not a standalone product. It requires a Microsoft 365 Copilot subscription, which runs $30 per user per month. That base license continues to cover everything you already have — Copilot Chat, the in-app experiences in Word, Excel, PowerPoint, and Outlook, built-in agents like Researcher and Analyst, and the Work IQ grounding that gives Copilot context from your organization's data. Cowork usage is not included in that license.
Layer two: Copilot Credits. Cowork consumption is billed in Copilot Credits, which are Microsoft's unified currency for usage-based AI. Credits are pooled at the tenant level, not per user. You can acquire them two ways: pay-as-you-go at $0.01 per credit (post-pay, no commitment), or through an annual pre-purchase plan that unlocks volume discounts ranging from 5 to 20 percent depending on the size of the commitment.
Layer three: task intensity drives cost. Not all tasks consume the same number of credits. Microsoft has published illustrative ranges tied to task complexity:
| Task Intensity | Example | Estimated Cost |
|---|---|---|
| Light | Weekly status update drafted from calendar + priorities, saved for review | 70–200 credits (~$0.70–$2.00) |
| Medium | Customer meeting briefing from emails, CRM data, calendar context, and a template | 400–600 credits (~$4.00–$6.00) |
| Heavy | Six months of product-usage data analyzed into a leadership-ready report |
These are illustrative estimates — actual consumption depends on the models Cowork selects, the orchestration overhead, how much context it processes, and which tools it invokes. But they provide a realistic planning anchor.
Who Is Affected Right Now
The billing transition has two different timelines, and if you have been running Cowork through Microsoft's Frontier program, you are already behind on this.
Organizations that had at least one user active in Cowork during the Frontier preview period had a grace period: no additional charges through June 30, 2026. That window closed on July 1. If your organization is in that group and has not yet configured billing policies, Cowork access may already be restricted or your tenant may be accruing charges without a budget in place.
For all other customers, billing began at general availability on June 16, 2026. Cowork is off by default for these tenants — but "off by default" does not mean "immune to surprise." The moment an admin enables Cowork, usage-based billing is live. If there are no spending limits configured, there is no automatic floor.
What IT Leaders Need to Do
The governance controls exist. The question is whether your team has set them up.
Microsoft built Cowork cost management into the Microsoft 365 admin center. From the Cost Management dashboard, administrators can enable or disable Cowork at the tenant level, allocate access to specific users or groups, set spending thresholds, configure budget alerts, and place hard caps that prevent overspend from escalating. Microsoft also offers a Customer Cowork Estimator — a calculator to model expected credit usage based on your organization's task profile before you turn the feature on.
Security and compliance controls extend to Cowork through Microsoft Purview. The same data governance tools your organization already uses for Microsoft 365 apply here. Cowork inherits the permissions of the user operating it — it can only access files and emails the user could already access. Sensitive actions like sending emails, posting in Teams, and scheduling meetings trigger a human approval prompt before Cowork proceeds. None of this happens silently.
The practical checklist for IT: verify your tenant's Cowork status (is it on?), check whether any Frontier preview usage generated charges, set up spending controls before broadly enabling access, and determine which user groups have legitimate high-value use cases versus which ones will generate noise.
What Finance and Operations Leaders Need to Budget
For CFOs and COOs, the question is less about the controls and more about the math.
At current pay-as-you-go rates, a power user who runs five medium-complexity Cowork tasks per week — meeting briefings, project kickoff documents, stakeholder communications — will consume roughly 2,000 to 3,000 credits per month, or about $20 to $30 on top of the base Copilot license. For a team of 50 knowledge workers with similar usage patterns, that adds up to $1,000 to $1,500 per month in consumption charges, in addition to the $1,500 per month already being paid for the base Copilot subscriptions.
The ROI math can work decisively in favor of Cowork. A medium-complexity briefing that would take a senior manager two hours to compile manually — pulling emails, cross-referencing CRM data, formatting a slide — costs roughly $5 to $6 in Cowork credits. At a fully-loaded cost of $100 per hour for that manager, the same task runs $200 or more. The challenge is that savings accrue in knowledge-worker time, which is notoriously hard to attribute directly to P&L. Organizations that have already built AI ROI measurement frameworks will close this calculation quickly. Those that have not will struggle to justify the line item.
Volume discounts on pre-purchase credit plans (5 to 20 percent off) become meaningful at scale. An enterprise committing to 500,000 credits annually can materially reduce per-task costs. The tradeoff is forecasting accuracy — buying too far ahead of actual usage leaves unused credits on the table.
The Broader Signal for Enterprise Leaders
Copilot Cowork's billing model is not an anomaly. It is a preview of where enterprise AI pricing is heading across the board.
The flat per-user SaaS model that has dominated software procurement for two decades is being replaced with consumption-based models tied to actual AI workloads. That creates three new operational requirements that most enterprise procurement functions are not built for.
First, forecasting AI usage is fundamentally different from forecasting seats. Seat counts are predictable. AI workload consumption is variable by task complexity, individual usage patterns, and organizational demand. Finance teams need new forecasting instruments.
Second, governance can no longer live only in IT. When AI spend scales with usage, business unit leaders need to understand their team's consumption patterns, not just whether access is provisioned. The CFO and the CIO need a shared view of where AI spend is going and what value it is generating.
Third, the line between "AI tool" and "AI worker" is dissolving. Cowork does not assist with work. It executes work. That distinction changes how organizations think about headcount planning, workflow design, and where human judgment genuinely needs to remain in the loop.
The organizations navigating this transition well are the ones that have already built FinOps-style disciplines around cloud spend and are applying them directly to AI consumption. The organizations struggling are the ones still waiting for a monthly invoice to tell them what AI is actually costing.
What to Do This Week
If you are in IT: check whether Cowork is enabled in your tenant, audit whether any Frontier preview charges are outstanding, and configure the cost management controls in the M365 admin center before broader enablement. The tools exist — they just need to be activated.
If you are in finance or operations: request a usage estimate from IT using Microsoft's Cowork Estimator, define which teams have the highest-value use cases for agentic delegation, and build a credit budget into Q3 planning. Model two scenarios — modest adoption (10 to 20 percent of Copilot users running 2 to 3 tasks per week) and broad adoption (50 percent of users at similar rates). The gap between those scenarios is likely $5,000 to $50,000 per month for a mid-sized enterprise.
The preview period is over. The free ride is done. The question now is whether your organization captures the value of Cowork on purpose — or pays for it without knowing why.
Sources:
