TL;DR<\/p>\n
June Availability: Microsoft released Copilot Cowork worldwide on June 16 for eligible Microsoft 365 Copilot customers. Completed Work: Cowork handles long-running tasks across tools and returns completed results rather than only drafts. Usage Billing: Copilot Credits vary with model use, retrieved context, tool calls, and runtime. Admin Controls: Administrators can keep Cowork off, restrict access, set budgets and alerts, and review usage. Benchmark Limits: Microsoft\u2019s adoption and savings figures remain first-party claims published when it released Cowork in June. <\/p>\n
Microsoft released Copilot Cowork<\/a> worldwide on June 16 for eligible Microsoft 365 customers after Copilot Cowork\u2019s preview period<\/a>, putting delegated Office work behind a usage meter.<\/p>\n Cowork\u2019s worldwide rollout carried forward its multi-model design. Copilot Cowork\u2019s scheduled tasks run in the cloud regardless of whether a laptop is open, and its Microsoft Graph connection keeps Microsoft 365 governance controls in the task flow.<\/p>\n Its cloud-based architecture enables long-running work across several tools. Customers can assign that work and receive a completed result instead of only a draft<\/a>.<\/p>\n Each task consumes Copilot Credits, Microsoft\u2019s usage unit for agent work, based on model use, retrieved context, tool calls, and runtime. Billing began with general availability, while qualifying customers in Microsoft\u2019s Frontier early-access program received a grace period before full charges applied. Delegating more work can save time, but it also creates a variable charge that administrators must govern.<\/p>\n Microsoft puts preview adoption at more than half of the Fortune 500, a figure that is not independently corroborated. Administrators retain the deployment decision: Cowork is off by default, with controls for access and spending, budgets, alerts, and usage reports at tenant, group, and user levels. Deployment remains a policy choice rather than an automatic consequence of buying Microsoft 365 Copilot.<\/p>\n Autonomy Comes With a Meter <\/p>\n When Microsoft released Cowork on June 16, customers needed an eligible Microsoft 365 Copilot user license. Each Copilot Credit cost $0.01 under the pay-as-you-go option<\/a>, and Microsoft also offered a prepaid P3 volume plan. Microsoft\u2019s terms applied at release; current terms may differ.<\/p>\n Model choice, retrieved context, tool use, and runtime can each raise consumption, so the unit price alone cannot predict the bill for a completed task. Administrators can limit who runs Cowork, set budgets and alerts, and inspect usage before expanding deployment.<\/p>\n Microsoft says internal comparison covered 125 runs across 12 prompts where\u00a0 Copilot Cowork produced 30% to 40% lower average cost<\/a> per prompt than Claude Cowork with the Microsoft 365 connector when both used Opus 4.8. Microsoft cautioned that actual costs vary with usage, configuration, and time, and no independent test corroborates its result.<\/p>\n Under Daniel Anderson\u2019s test conditions, GPT 5.5 would have cost 2.7 times as much as Sonnet<\/a> for equivalent work, while Opus would have cost roughly $0.80 more than Sonnet. Different configurations prevent that test from validating Microsoft\u2019s comparison.<\/p>\n A Cowork approval-control test<\/a> examined a separate permission boundary before general availability. Spending limits helpt to constrain cost, while access and approval controls constrain what Cowork may do with organizational data across tools. Staged deployment lets administrators measure consumption without granting broad access immediately.<\/p>\n Cloud Agents Compete on Where Work Runs <\/p>\n Copilot Cowork runs in Microsoft\u2019s cloud and works with Microsoft 365 data. Anthropic\u2019s Claude Cowork web and mobile rollout<\/a> added cross-device task access, while local file access and computer control still depend on the desktop app.<\/p>\n