–> Auch auf deutsch verfügbar!
This article was translated from German with the help of AI.
Microsoft has officially made Copilot Cowork generally available. What used to be part of the Frontier preview is now a regular capability for Microsoft 365 Copilot customers. That does not mean every detail has fully left preview territory: according to Microsoft, individual capabilities such as use in the Edge browser and the model picker with GPT 5.5 remain Frontier-only for now.
The most important admin point comes right at the beginning: Copilot Cowork is off by default. Admins decide when Cowork is enabled in the tenant and which users get access. That is an important difference compared with topics such as Flex Routing, where Microsoft used a much stronger opt-out model.
Cowork is not just another chat experience. Microsoft positions it as an agentic system for longer, multi-step tasks across Microsoft 365. The user describes what should be done, and Cowork can turn that into actual work: preparing or sending emails, scheduling meetings, creating documents, posting Teams messages, organizing calendars, or researching information across company data.
The difference from Copilot Chat is therefore fairly clear: Copilot Chat primarily helps with thinking, summarizing, and writing. Cowork is intended to execute work.
What is new with GA? #
For general availability, Microsoft lists several points that matter for organizations.
Cowork is now available worldwide for Microsoft 365 Copilot customers. Microsoft also states that during preview, more than half of the Fortune 500 used Cowork.
Cowork is becoming more integrated into the Microsoft 365 Copilot app. Users can move from the Copilot experience into the Cowork experience and continue tasks there.
The ecosystem is also expanding. According to Microsoft, currently available partner plugins include Enosix, Harvey, LSEG, Miro, monday.com, Moody’s, Morningstar, S&P Global Energy, and TeamsMaestro. More integrations such as Adobe, Atlassian, Box, Canva, CB Insights, Databricks, MoneyForward, and Templafy are planned. Microsoft also mentions Fabric and Dynamics 365 Sales, Customer Service, and ERP apps in the context of GA availability. I would still verify the exact feature scope in the tenant, because parts of the documentation are still catching up.
For security and compliance, Microsoft points to existing Microsoft 365 controls such as Audit Log, Data Security Posture Management, eDiscovery, Insider Risk Management, and Communication Compliance. Data Lifecycle Management is planned from June 22, and DLP is expected to follow. Important for admins: according to Microsoft, sensitivity labels are inherited and displayed. That is especially relevant for generated documents and artifacts.
The new billing model #
The most important point for admins is probably pricing.
According to Microsoft, Copilot Cowork requires a Microsoft 365 Copilot User Subscription License. In addition, Cowork is billed based on usage. Billing uses Copilot Credits.
The price of a task depends on four factors: model usage, context retrieval, tool calls, and runtime. Microsoft describes three typical task sizes: light, medium, and heavy tasks. Light tasks use only a few knowledge sources and generate a small number of outputs. Medium tasks work with multiple sources and structured reasoning. Heavy tasks aggregate more broadly, use deeper reasoning steps, and generate more results.
For payment, Microsoft names two models: pay-as-you-go and P3. Pay-as-you-go is listed by Microsoft at US$0.01 per Copilot Credit. P3 is a commit model where customers commit to a usage volume in advance and receive a discount.
Billing for Copilot Cowork starts with GA. Tenants that had at least one Frontier user using Cowork between March 30 and June 16 receive a transition period and will only be charged from July 1, 2026.
Important: the general Copilot Studio billing documentation also describes Copilot Credits, but not necessarily the same mechanics as Cowork. For Cowork, the Cowork-specific pricing documentation is the relevant source.
What does this mean for governance? #
From an admin perspective, Cowork is more interesting than a normal chatbot because it can execute actions. Microsoft describes that users approve actions before they happen. Even so, the organization needs to understand which tasks users delegate to Cowork and which data is processed along the way.
This is not only about the initial approval. For medium and high risks, Cowork shows a risk-level indicator, provides a preview before confirmation, and offers the option in the conversation to skip future approvals for similar actions. That can make work smoother, but it is relevant from a governance perspective.
The cost model matters as well. With classic Microsoft 365 Copilot, the license per user is relatively predictable. Cowork adds variable usage costs to that model. That means not only technical enablement matters, but also cost control.
Microsoft mentions new cost-management capabilities: admins should be able to set spending limits, assign budgets, and analyze usage by tenant, group, user, and feature. A user-facing display of cost per task is planned after GA. I would still verify the exact admin path for enablement and budget control in the tenant before publication.
What should be viewed critically? #
Cowork brings three governance topics.
First: cost. Because billing is usage-based, consumption can vary significantly depending on user type, task complexity, and model choice. Without budgets, limits, and reporting, Cowork can become difficult to predict.
Second: actions. A system that connects email, calendar, Teams, files, and company data needs clear governance. Especially with plugins and external systems, organizations should verify which data flows where and which admin controls apply.
Third: expectation management. Cowork is designed for longer and more complex tasks. Such tasks can run for minutes or hours. That is a different user experience than Copilot Chat.
There are also concrete product limitations to know. According to Microsoft, Cowork cannot access local files, only OneDrive and SharePoint. It cannot delete files or folders in OneDrive or SharePoint. Cowork cannot read encrypted files, even if the user has access to them. Attachments are limited to 200 MB. Microsoft also states that Custom Skills are not validated by Microsoft.
For European organizations, there is another checkpoint: Cowork can use Anthropic models as a subprocessor. If you already looked closely at EU Data Boundary, model routing, and subprocessors in the context of Flex Routing, you should repeat that review here and not rely only on the GA announcement.
Why enable Cowork? #
The value is in work that is more than just an answer. Cowork can take on longer tasks, include multiple sources, create files, prepare communication, and coordinate processes across different Microsoft 365 apps.
That makes it especially interesting for recurring workflows, reporting, research, communication preparation, meeting preparation, project work, or larger file and information analyses.
If Copilot has often stopped at drafting so far, Cowork is intended to take the next step: not only suggest, but execute.
My recommendation #
I would not simply enable Copilot Cowork tenant-wide and wait to see what happens. The combination of agentic execution and usage-based billing is too relevant for that.
The good part: Cowork is off by default. Organizations therefore have the chance to introduce it deliberately. The sensible path is a controlled pilot: selected user groups, clear use cases, budget limits, cost monitoring, and a review after a few weeks. It is especially important to understand early which tasks create real value and which ones only consume credits.
Cowork can be a powerful step from “AI helps me think” to “AI works with me.” That is exactly why the rollout should be intentional.