Microsoft Copilot Cowork is a currently-in-preview extension of Microsoft 365 Copilot. Microsoft Learn describes Cowork as an "action-taking assistant" — that is, a Copilot that does not only answer but actually carries out actions inside Microsoft 365 apps.
Important framing: An earlier version of this article described Cowork as a "shared AI session" or a "many-to-one Copilot in Teams meetings". That was wrong. Microsoft positions Cowork as an action-taking assistant, not as a shared collaborative session. Cowork is also in preview, so scope, availability and licensing can change. We stick strictly to what is officially documented.
What Cowork actually does, per Microsoft
The officially documented Cowork capabilities fall into six categories:
- Sending emails through Outlook
- Scheduling meetings with the right participants
- Creating documents in Word and other Office apps
- Posting in Microsoft Teams
- Searching across the Microsoft 365 content the user can access
- Running prompts on a schedule — Cowork acts at the configured time on its own
The common pattern: Cowork does something. Classic Copilot answers a question; Cowork creates the document, sends the email, posts the update.
What Cowork is not
To keep expectations realistic, a few clarifications:
- Cowork is not a shared, live Copilot session where multiple people see the same prompt thread together.
- Cowork is not a meeting bot that moderates Teams meetings in real time.
- Cowork does not replace Copilot Chat or the Copilot features built into Office apps — it complements them with the action-taking and scheduling layer.
If you are looking for collaborative prompting, look at Loop components, shared Pages or the Copilot features built into Teams. Cowork is a different class of capability.
Action-taking scenarios
Sending an email from a brief
An account manager says: "Send the customer Beispiel AG a short status email covering the three most important open items from our last meeting." Cowork drafts the email, surfaces it for approval and sends it after confirmation.
Scheduling a meeting
"Schedule a 30-minute status meeting with the project team next week, preferably Tuesday or Wednesday afternoon." Cowork checks the listed people's availability, proposes slots and sends the invite.
Creating and filing a document
"Create a one-page executive summary of our last quarterly review and place it in the 'Leadership' library." Cowork pulls the sources, generates the summary and stores it at the specified location.
Posting in Teams
"Post today's pipeline status with the three biggest open opportunities to the 'Sales DACH' channel." Cowork drafts the post, formats it and posts after approval.
Scheduled prompts
Cowork runs defined prompts at fixed times — for example, a weekly overview every Monday. Our dedicated deep dive is in Scheduled prompts & autonomous actions in Microsoft 365 Copilot Cowork.
Cowork vs. classic Microsoft 365 Copilot
| Aspect | Classic Copilot | Cowork (preview) |
|---|---|---|
| Mode | Reactive (responds to prompt) | Active, takes action |
| Trigger | Human asks | Human commissions — Cowork executes |
| Output | Text or content answer | An action in Microsoft 365 (email, meeting, document, post) |
| Timing | Synchronous, in the moment | Synchronous or scheduled |
| Confirmation | Not required | Recommended for outward-facing actions |
The two are complementary: classic Copilot for content and knowledge work, Cowork for the subsequent execution.
Security, compliance and governance
Even in preview, the Microsoft 365 Copilot principles apply:
- Permissions: Cowork can only access data the running user is entitled to see. There is no privilege escalation.
- Audit trail: Cowork actions — sent emails, scheduled meetings, created documents, Teams posts — are recorded in the Microsoft 365 audit log.
- Admin control: IT admins configure Cowork through the existing Copilot admin tools in the Microsoft 365 admin center.
- Data processing: Content stays within the tenant's compliance boundary.
- Confirmation before sending: For outward-facing actions, we recommend requiring a human approval step during the preview.
Swiss organizations with stricter compliance requirements (FINMA, FADP, sector-specific obligations) should evaluate Cowork in a clearly bounded pilot for as long as the feature is in preview.
Prerequisites
Cowork — as of the preview — uses the regular Microsoft 365 Copilot prerequisites:
- Microsoft 365 Copilot licenses for the participating users
- Copilot features enabled in the tenant
- A configured Outlook, Teams and SharePoint setup so Cowork can act in those surfaces
Licensing and activation details change frequently during the preview — for the current requirements, Microsoft Learn is the canonical source.
A realistic rollout path
- 1Check availability: Clarify whether Cowork is enabled in your tenant.
- 2Pick a small set of action-taking use cases: e.g. the weekly status email or a scheduled quarterly meeting.
- 3Pilot group with a confirmation step: Early adopters validate every outward-facing action before it runs.
- 4Set governance guardrails: Which actions are allowed in which context?
- 5Document lessons learned: Use preview experience to decide how broadly Cowork should be rolled out post-GA.
How CNEXT can help
As a Microsoft Partner, we accompany Swiss organizations through an honest, early evaluation of Copilot Cowork:
- Fact-check & use-case workshop: Which Cowork actions are realistically usable for you today?
- Governance setup: Defining the guardrails for outward-facing, autonomous actions.
- Pilot support: Hands-on guidance during the preview, with clearly measurable success criteria.
- Training & enablement: We train end users and admins on what Cowork can actually do today — without marketing promises.
Cowork is an important building block in Microsoft's agentic Copilot strategy. Once you understand the feature realistically — as an action-taking assistant in preview — you can evaluate first use cases now, instead of waiting for a "shared AI session" Microsoft never actually announced.