Copilot Cowork went generally available on June 16, 2026, and the questions that followed were not the ones Microsoft’s launch materials anticipated. IT admins were not asking “how do I use it?” They were asking what it actually costs, who controls the spend before a surprise bill arrives, what happens when an action is taken without enough context, and whether the organization’s data stays within its own security boundary.
This FAQ draws from Microsoft’s official Cowork FAQ, the Copilot Credits Guide (June 2026), Microsoft’s partner GTM materials, and the community conversations happening in IT forums since launch. As a Microsoft CSP Direct Bill Partner and Solutions Partner, TrustedTech fields these questions from customers regularly. A few of the answers below go beyond what the documentation states, based on what we see when organizations actually deploy.
What Is Copilot Cowork?
Q. What exactly is Copilot Cowork?
Cowork is an agentic execution layer inside Microsoft 365 Copilot. You describe an outcome, and Cowork plans the work, executes it across your M365 environment, and delivers completed outputs: documents, emails, calendar updates, Teams posts, and research briefs. It runs autonomously in the cloud, including after you close your laptop.
The distinction from standard M365 Copilot is structural, not cosmetic. Copilot in the apps handles individual tasks within a single application in a single turn. Cowork takes an entire process end-to-end across multiple apps and data sources. Microsoft’s rule of thumb, drawn from their partner materials: one app for one file belongs in M365 Copilot; an entire multi-step process belongs in Cowork.
Q. What is the difference between Copilot Chat, M365 Copilot, and Copilot Cowork?
Three tiers of the same platform, each with a different scope and cost.
Copilot Chat is free for eligible Microsoft 365 users. Single-turn interactions: quick drafts, summaries, brainstorming, and Q&A. It does not ground deeply in your organizational data.
Microsoft 365 Copilot is the £24/user/month paid license. It embeds Copilot inside Word, Excel, Outlook, Teams, and PowerPoint, grounded in your emails, meetings, and files through Work IQ. This license is the prerequisite for everything else, including Cowork.
Copilot Cowork requires the M365 Copilot license and layers consumption-based billing on top. It handles complex, multi-step work spanning multiple apps, produces multiple deliverables in a single run, and operates over minutes to hours rather than seconds. For more on the base licensing distinction, see our breakdown of the difference between Copilot Chat and M365 Copilot.
Q. What tasks does Cowork actually perform?
The 13 built-in skills cover email (drafting, replying, forwarding, sending through Outlook), calendar management (scheduling, conflicts, briefings), document creation (Word, Excel, PowerPoint, PDF), Teams posting, enterprise search, deep research, and stakeholder communications. Each skill loads dynamically as Cowork needs it for a given task.
Microsoft’s Task Pack groups these tasks into three tiers. Lightweight tasks: calendar rebalancing, project archiving, document-to-deck conversion. Everyday workflows: automated weekly status emails, inbox intelligence briefs, project board creation from email and Teams context. Hard problems: out-of-office handoffs that span emails, meetings, and calendar; OneDrive audits producing an interactive HTML catalog; executive command centers; and cross-meeting pattern analysis surfacing recurring themes across 30 days of calls. The hard problems tier is where Cowork displaces the most manual time, and where the credit cost is easiest to justify.
Q. How is Cowork different from a Copilot Studio agent?
Related tools, different purposes. Cowork is a ready-to-use execution surface built into the M365 Copilot app; you describe a task in natural language, and it runs. Copilot Studio is where organizations build, configure, and publish custom agents for specific workflows, making them available to teams at scale.
The practical deployment sequence, per Microsoft’s partner guidance, is to prototype and validate a workflow in Cowork first. Once you know it works and is worth scaling, build it as a published Copilot Studio agent. Custom skills built via OneDrive SKILL.md files sit between the two: personal or team-level automation that lives inside Cowork without requiring a full Studio deployment.
Licensing and Pricing
Q. What license is required to use Copilot Cowork?
An active Microsoft 365 Copilot User Subscription License (USL) is required for each user. That’s the same £24/user/month seat covering Copilot Chat and Copilot in the core M365 apps. Cowork does not come with the base M365 E3 or E5 license. E7 bundles the Copilot USL with E5 at a package price, but E7 is not required; any M365 Copilot USL holder can access Cowork once an admin enables it. If you’re evaluating E7 as the path to Copilot licensing, our breakdown of Microsoft 365 E7 and the Frontier Suite covers the bundle math.
Q. How does Cowork billing work?
Two layers. The M365 Copilot USL is the fixed per-seat cost. Cowork execution is billed separately through Copilot Credits, a usage-based currency pooled at the tenant level. One credit costs £0.008 under pay-as-you-go, per Microsoft’s official Copilot Credits Guide.
Each task draws credits across four inputs: the AI model selected for the work; the volume of organizational context retrieved (emails, files, calendar, Teams messages); the number of tool calls made across apps; and the total runtime. A short, single-source task costs far less than a long, multi-source analysis producing several output files. Microsoft’s illustrative planning ranges, based on Anthropic Opus 4.8: light tasks (weekly status update, simple draft) run 70–200 credits, roughly £0.56–£1.60; medium tasks (customer meeting prep from multiple sources) run 400–600 credits, £3.20–£4.80; heavy tasks (6-month data analysis with leadership-ready outputs) run 1,500 or more credits, £12 and above. These are planning estimates, not guaranteed rates.
Q. Are Copilot Credits shared with other Microsoft services?
Yes, and this catches organizations off guard. Credits are a single pooled currency used across Cowork, Copilot Studio agents, Dynamics 365 agents, Power Platform workloads, and the Work IQ APIs. They pool at the tenant level. If your organization uses multiple of these services, size your credit budget based on total AI consumption across all of them, not on Cowork in isolation. The M365 Copilot license includes no bundled credit entitlements; every credit Cowork consumes is an incremental cost on top of the £24 seat.
Q. What is the difference between pay-as-you-go and the Prepaid Plan (P3)?
Pay-as-you-go charges £0.008 per credit, billed in arrears at month-end. No upfront commitment, no interruption if usage exceeds an informal estimate. For most organizations, this is the right starting point because it requires no prediction of future usage.
The Copilot Credit Pre-Purchase Plan (P3) is a one-year prepaid pool with volume discounts from 5% at 300,000 credits up to 20% at 300 million credits. The Microsoft Credits Guide is direct about the risk: unused P3 credits expire at the end of the annual term. Committing to prepaid before understanding actual consumption is a financial risk, not a savings strategy. Microsoft’s partner guidance suggests 60–90 days on a pay-as-you-go plan to establish actual consumption patterns before sizing any prepaid commitment.
Q. Can we buy Copilot Credits through our CSP partner?
Yes. Microsoft’s Copilot Credits Guide lists the CSP program as an official purchasing channel alongside direct Microsoft Online. Organizations already managing M365 licensing through a CSP can provision and manage credits through the same partner relationship, with the CSP handling provisioning, billing, and ongoing support.
Q. What happened to Frontier program customers at GA?
Cowork was free to Frontier participants from March 30 to June 16, 2026. Billing activated at GA on June 16. Tenants with active Cowork usage during the Frontier period have a grace period: no billing until July 1, 2026. After July 1, billing applies to all usage. Customers whose admins have not configured billing by then lose access to new Cowork tasks, though their existing task history stays accessible.
Admin Controls and Cost Management
Q. Is Cowork switched on by default?
No. Cowork is disabled by default in every tenant. Admins must explicitly enable it in the Microsoft 365 Admin Center (MAC) under Copilot > Cost Management and link an Azure subscription for billing. Nothing happens until an admin actively enables access and configures billing. This is a deliberate design choice, and it is the right framework for deployment: configure governance first, then open access.
Q. What spending controls exist?
Admins can set spending limits at three levels: the full tenant, specific user groups (a department, a team, or a single-user group for individual caps), and individual users within a group policy. Alongside hard limits, they can configure threshold alerts notifying designated recipients when spend crosses a percentage of the defined limit. Usage reporting is available per user, group, and feature. There is also a discoverability toggle that controls whether users can even see or request access to Cowork, independent of whether billing is configured.
The Cost Management workflow breaks into four steps: activate a default policy and set a billing method; configure spending policies at the relevant scope levels; purchase credits through PAYG or P3; and monitor usage trends to refine policies over time. All of this lives in the MAC, where admins already work.
Q. What happens when a user hits their credit limit?
They can submit a credit request from inside Cowork, which surfaces to an admin for approval. Tasks already in progress are not interrupted mid-execution; the limit applies to new tasks started after the cap is reached. Admins get alerts when usage approaches configured thresholds, not retroactively after the bill arrives.
Q. Can Cowork be disabled for specific users while staying on for others?
Yes. Admins can restrict access at the user level by adding individuals to a security group configured to exclude them from Cowork. Access can also be scoped differently at the group policy level, so different teams have different credit allocations and controls. Individual users can be excluded while the tenant-level access remains enabled.
Q. How do CSP partners configure Cowork on behalf of customers?
Two steps, both required. First, confirm the customer has an Azure subscription linked to the partner billing account; if not, create one through the Azure Portal or Partner Center. Second, configure usage-based billing in the customer’s M365 Admin Center by connecting that Azure subscription and setting up access controls, spending limits, and alerts. This requires Admin on Behalf Of (AOBO) permissions with GDAP (Granular Delegated Admin Permissions). Partners without GDAP in place need to establish that relationship before completing the billing setup on a customer’s behalf. In practice, this is one of the first things that stalls CSP customers who want to enable Cowork quickly: the GDAP prerequisite is not always in place even for long-standing partner relationships.
Security, Compliance, and Data
Q. Is our data safe when Cowork runs tasks?
Cowork operates entirely within your Microsoft 365 tenant and inherits your existing M365 security posture. Every action runs under the user’s M365 account permissions; Cowork cannot access data the user is not already permitted to see. Files stay in OneDrive and SharePoint. Sensitivity labels are inherited end-to-end. Prompts, responses, and generated artifacts flow through your existing M365 compliance controls. Microsoft’s commitment, stated in their customer materials: your data is not used to train or improve foundation models, and you are covered against AI security and copyright risks under the standard Microsoft 365 enterprise terms.
Q. What compliance features are available at GA?
At launch, Cowork compliance coverage includes audit logging, Data Security Posture Management (DSPM), eDiscovery, Insider Risk Management, Data Lifecycle Management (from June 22), and Communication Compliance policies. Data Loss Prevention (DLP) is coming shortly after GA. These controls apply to Cowork prompts, responses, and any files Cowork creates or modifies during task execution.
Q. Cowork uses Anthropic models. Does our data go to Anthropic?
At GA, Cowork runs on Anthropic Opus 4.8 and Sonnet 4.6. GPT-5.5 is available to Frontier customers, and Microsoft’s own Cowork 1 model, built for everyday tasks at a lower cost, will be released in the weeks following GA. Anthropic operates as a subprocessor to Microsoft under Microsoft’s standard Online Services terms. The data protection obligations that govern your M365 environment extend to Anthropic’s processing as a subprocessor. The multi-model design means Microsoft can route tasks to whichever model fits the work without the customer managing model selection directly.
Q. Can Cowork access files on a user’s local machine?
No. Cowork cannot access or edit files stored locally on a device. It works only with files in OneDrive and SharePoint. It also cannot delete files or folders from either service; it can read, create, and modify, but the delete action is explicitly blocked. Files attached directly to a conversation must be under 200 MB. Cowork cannot read encrypted files even when the user has access permissions to them.
Q. Can Cowork actions be undone?
Not in general. A sent email is sent. A scheduled meeting is on the calendar. A Teams post is posted. This is the most important thing to understand about the approval step: before taking a sensitive action, Cowork pauses, shows a preview, and asks for confirmation. Medium- and high-risk actions include a risk-level indicator. Users can approve, cancel, or opt to skip future prompts for that action type in the current conversation. The practical advice TrustedTech gives customers: train users to treat the approval prompt as an actual review moment, not a speed bump to click through. The irreversibility is by design, but it puts the weight on the approval gate being used seriously.
Skills, Plugins, and Extensibility
Q. What is a Cowork skill, and how is it different from a prompt?
A prompt tells Cowork what to do right now. A skill teaches Cowork how to do it whenever asked, without re-prompting. Skills are stored as SKILL.md files in a user’s OneDrive at Documents/Cowork/Skills/. Cowork discovers them automatically at the start of each conversation. They also compose: one skill can hand off to another, building multi-stage workflows that run automatically without the user having to orchestrate each step.
The 13 built-in skills cover five categories: documents (Word, Excel, PowerPoint, PDF, HTML), communication (Email, Communications), calendar (Scheduling, Calendar Management, Meetings, Daily Briefing), intelligence (Enterprise Search, Deep Research), and automation (Adaptive Cards, goal-setting, skill management). Users can add up to 50 custom skills. Microsoft does not validate custom skills; review their outputs carefully before acting on the results.
Q. What partner plugins are available at GA?
Nine partner plugins launched at GA: Enosix, Harvey, LSEG, Miro, monday.com, Moody’s, Morningstar, S&P Global Energy, and TeamsMaestro. Microsoft’s first-party Fabric IQ and Dynamics 365 plugins (Sales, Customer Service, ERP apps) are also GA. Eight more partner plugins are on the way: Adobe, Atlassian, Box, Canva, CB Insights, Databricks, MoneyForward, and Templafy.
What plugins actually unlock: Miro for visual outputs (flowcharts, project boards, frameworks), monday.com for project board creation from Cowork task context, Fabric IQ for grounding weekly status emails in live business metrics, TeamsMaestro for surfacing recurring themes across months of meeting transcripts. Tenant admins must approve plugins before users can install them. Treat that approval the same way you would an Entra ID app approval: check what data the plugin requests access to before enabling it for production use.
Q. What are the three paths for extending Cowork?
OneDrive SKILL.md files are the no-code path. Any user can create a custom skill by placing a SKILL.md file in their OneDrive Skills folder. Cowork discovers it automatically, scores it against a quality rubric, and makes it available in conversations. No admin involvement required, no app deployment. Suitable for personal workflows and small team patterns.
Copilot Studio is the low-code path for admins. Build skills using Power Automate flows or API connectors, publish them as named agents, and deploy them across the organization with governance controls. Suitable when a workflow needs to scale beyond one user or one team.
The Microsoft 365 Agents SDK is the pro-code path for developers. Build skills in .NET, JavaScript, or Python, register them in Copilot Studio, and make them available inside Cowork like any built-in skill. Suitable for integrations with line-of-business systems that don’t have a first-party connector.
Practical Deployment Questions
Q. Should we roll Cowork out to everyone at once?
No. Microsoft’s own partner guidance says start with a pilot group, measure ROI on specific workflows, and expand deliberately. In TrustedTech’s deployments, the organizations that see the strongest early results follow the same pattern: they pick two or three roles with recurring, time-consuming coordination tasks, enable Cowork for 10–20 users in those roles, set spending limits before anyone runs a task, and treat the first 30 days as data collection rather than production rollout. Broad deployment before that calibration step is how organizations end up with credit bills that don’t correspond to any visible time savings. See our full evaluation framework in when Copilot delivers ROI.
Q. What is the best first workflow to try in Cowork?
Microsoft’s Task Pack guidance is practical here: pick one workflow that already costs your team real time. A weekly status that someone manually assembles every Monday morning. A meeting prep brief someone spends 30 minutes building before each customer call. A recurring project report that requires pulling from a board, writing it up, and distributing it. Run that one workflow in Cowork. Review the output carefully. Refine the instruction if the output needs adjusting. If it saves time and the output is reliable, turn it into a scheduled skill so it runs automatically. The goal is not to maximize the number of tasks going through Cowork. It is to find the specific workflows where the credit cost is clearly less than the labor cost it displaces, and operate there first.
Q. How much does the state of our M365 environment matter?
More than most organizations expect. Cowork grounds every task in Work IQ, pulling context from emails, files, meetings, calendar, and organizational history. The quality of the output is directly proportional to the quality of that data. Clean SharePoint with sensible permissions produces accurate, useful briefings. A sprawling SharePoint with outdated files, overly broad sharing, and years of undisciplined content produces outputs that cannot be trusted at the same credit cost.
This is the most common reason Copilot underperforms in deployments TrustedTech has reviewed, and it applies to Cowork with more force because Cowork acts on what it finds rather than just surfacing it. The objection “we haven’t seen ROI from standard Copilot yet” almost always traces back to this issue. Enabling Cowork in the same unprepared environment adds consumption billing on top of an already underperforming foundation. TrustedTech’s Copilot Readiness Assessment addresses this before any usage spend is committed.
Q. What devices and platforms does Cowork support?
Cowork runs in the browser at m365.cloud.microsoft, in the Microsoft 365 Copilot desktop app for Windows and Mac, and in the Microsoft 365 Copilot mobile app for iOS and Android. Voice input works in browser but depends on the specific browser; not all browsers support it. Files must be in OneDrive or SharePoint; Cowork cannot reach locally stored files on any device.
Q. Does Cowork keep running if I close my laptop?
Yes. Because Cowork runs in the cloud, tasks continue after the user closes their device or moves to something else. A 45-minute analysis runs to completion in the background. Files produced during the task save to OneDrive. If Cowork needs input mid-task, it pauses and marks the task as “Needs user input” until the user responds. If the connection drops, Cowork reconnects automatically and picks up where it left off; no work is lost.
The Bottom Line
The most persistent confusion about Copilot Cowork is treating it as a more capable, more expensive version of M365 Copilot. It is a different kind of tool. Copilot in the apps is fast, responsive, and handles single tasks within a single application. Cowork is slower by design, executes autonomously across the full M365 environment, and produces multi-step deliverables that would otherwise take real blocks of time. The credit cost only makes sense against workflows where that tradeoff holds, and only in environments where the underlying data is clean enough to make the outputs reliable.
The organizations that get value from Cowork quickly are the ones that scope access by role, set spending controls before enabling anything, start with one or two workflows that already cost meaningful time, and measure the first 30 days before expanding. That is not a unique insight about Cowork. It is how every successful enterprise AI deployment works.
If you have questions about licensing prerequisites, credit budgeting, CSP setup, or whether your M365 environment is ready to support Cowork, TrustedTech’s Copilot Readiness Assessment is the right first step, before any usage spend is committed.
Microsoft 365 Cost Optimization
How to Reduce Microsoft 365 Costs by 20% or More
The Complete Playbook for Reducing M365 Spend. Everything IT leaders and procurement teams need to cut Microsoft 365 costs without cutting capability.
- License right-sizing strategies
- SKU comparison and downgrades
- CSP vs. direct pricing analysis
- Governance and audit frameworks
- Copilot and add-on cost controls
- Renewal negotiation tactics
