Microsoft Copilot Cowork: What It Is and How to Use It

Using Microsoft 365 context

Cowork draws on Work IQ when building a response. It can pull from Outlook emails, Teams messages, SharePoint files, OneDrive documents, calendar events, and meeting transcripts. The quality of output depends on the data it can reach, so poorly named files, duplicated content, outdated documents, and messy permissions all limit what it produces.

Review and approval

Before Cowork takes any sensitive action, like sending an email, posting in Teams, or scheduling a meeting, it stops and asks for your approval. The prompt shows the specific action and a risk level indicator for medium and high-risk steps. You can approve it once, skip future prompts for similar actions in the same conversation with the "Don't ask again" option, or cancel entirely.

An approved action executes immediately, so the review you do at this prompt is the one that counts.

Long-running and scheduled work

Cowork runs in the cloud, so a task keeps running after you step away, and you can pick it up later in the Microsoft 365 Copilot app on Windows, Mac, iOS, or Android. Delegate something in the morning, sit in two meetings, and come back to a finished document. Tasks run from a few minutes to half an hour depending on scope.

You can also set up scheduled prompts for recurring tasks, such as a Monday summary of the week ahead. Scheduled prompts appear in the Tasks view and can be paused, edited, or deleted. Microsoft currently supports up to five scheduled prompts per user.

What Can Copilot Cowork Do?

Cowork has 13 built-in skills: Word, Excel, PowerPoint, PDF, Email, Scheduling, Calendar Management, Meetings, Daily Briefing, Enterprise Search, Communications, Deep Research, and Adaptive Cards.

Cowork also supports plugins from the Microsoft 365 App Store that connect it to systems like Dynamics 365 and Fabric IQ. The plugin ecosystem is still early-stage, and specific connector availability changes regularly. Verify which plugins are GA before building a workflow around any particular one.

Here is what those built-in skills handle, grouped by the kind of work they cover.

Manage email workflows

Cowork can draft, reply to, forward, and send emails through Outlook. It can sort emails into folders, delete emails, respond inline, and create HTML newsletters. The most common uses are drafting follow-ups after meetings and turning long email threads into stakeholder summaries.

Schedule and manage meetings

Cowork can schedule meetings using natural language, move events, decline meetings with a message to the organizer, and create focus time blocks. It can prepare daily briefings and meeting intelligence for upcoming conversations. Calendar changes affect other people's schedules, so reviewing proposed changes before approving is not a formality.

Create and edit documents

Cowork can build Word documents, Excel spreadsheets, PowerPoint presentations, and PDFs from scratch, and it can revise a file you share with it. Either way, it saves the result as a new file in your OneDrive Cowork folder instead of changing the original in place. That is annoying if you expected in-place editing, but it is by design, not a bug.

Post and coordinate in Teams

Cowork posts to Teams channels and sends 1:1 or group direct messages, including formatted cards with structured data. Review messages before posting, especially in channels with external participants.

Search and organize work context

Cowork searches across your organization through Enterprise Search and pulls together information from multiple sources with the Deep Research skill. It can browse OneDrive and SharePoint folders and reorganize files into new or existing folders. One firm limit: Cowork cannot delete files or folders by design.

Copilot Cowork vs. Copilot Chat: Key Differences

Cowork sits inside a product map that now has several layers: Copilot Chat (included at no additional cost with eligible M365 plans), Copilot in individual apps, prebuilt agents like Researcher and Analyst, and Frontier agents like Cowork.

The clearest comparison is Cowork versus Copilot Chat, which is what most people mean by "standard Copilot." The table below shows where they differ.

Copilot Chat is still the right tool for contained, single-session tasks. Cowork is useful when work is multi-step and scattered across apps.

Copilot Cowork Use Cases by Role

Microsoft's documented launch scenarios focus on coordination-heavy work. The roles that fit best involve a lot of switching between Outlook, Teams, files, and calendar to prepare, communicate, and follow up.

Sales and customer success

A customer success manager can ask Cowork to prepare a briefing before a renewal meeting using recent emails, open action items, and related files, then draft a follow-up afterward with decisions and next steps. With the Dynamics 365 Sales plugin enabled, Cowork can also pull in account and pipeline context. Customer-facing messages should always be reviewed before sending, particularly for tone and relationship context that Cowork cannot read.

Project management

Cowork can turn Teams discussions, meeting notes, and project files into status updates and summaries. Without a dedicated PM plugin (monday.com is announced but not GA at the time of writing), it relies on native M365 data. Verify owners, deadlines, and project status before sharing any update that reaches leadership. A wrong deadline in a status report is the kind of thing Cowork will not catch on its own.

Operations and admin work

Recurring coordination is where Cowork helps most. Scheduling meetings, sending internal updates, organizing documents: these tasks repeat constantly. Scheduled prompts are built for exactly this. Set one up for a Friday morning status report and you have one less thing to remember each week.

HR and onboarding

Cowork can help draft onboarding documents, schedule training sessions, and organize policy materials. Sensitive HR decisions, legal wording, and policy interpretation need to stay with a human. There is no HR-specific plugin as of mid-2026.

Finance and reporting

Cowork can draft monthly updates, prepare basic spreadsheets, and organize budget-related documents. With the Dynamics 365 ERP plugin (when the right licenses are in place), it can pull financial data from the ERP system. Microsoft's documentation explicitly states that Cowork outputs should not be the sole basis for financial decisions. Anything touching external reporting or regulatory obligations needs careful human review before it leaves the building.

Executive assistance

Daily briefings, calendar management, meeting preparation, and follow-up communication are the clearest fit. Cowork handles the scheduling and drafting. Relationship management and judgment calls are still yours.

When Copilot Cowork Works Best

Organizations already deep in Microsoft 365 get the most out of this. Teams that route daily work through Outlook, Teams, and SharePoint are the natural fit. Teams on a mix of Notion, Slack, and non-Microsoft tools will see less until the plugin ecosystem catches up.

A few conditions where Cowork tends to perform well:

• The work is repetitive and follows a clear pattern, like meeting prep, weekly updates, or calendar cleanup.
• The task pulls from multiple M365 sources, where manual app-switching is the real bottleneck.
• The output is quick to review, like a draft email or internal summary, so the approval step adds little friction.

Copilot Cowork Limitations and Known Gaps

Cowork has documented limitations worth knowing before you build anything around it.

The design limits are official and stable. Cowork cannot access local files on your device. It cannot delete files or folders in OneDrive or SharePoint. It cannot read encrypted files, even if you have access to them. Attached files must be under 200 MB. These are deliberate constraints.

A few things will also degrade output quality in practice:

• Vague instructions produce generic results. Writing specific prompts is the fix, and I cover that in the best practices section.
• Outdated or disorganized data limits what Cowork can find. As I noted earlier, weak workspace hygiene shows up directly in the output.
• Poor permission setup can block data Cowork needs, or allow it to act on data that should be restricted. Cowork operates strictly within your existing M365 permissions and does not create new access paths.
• Tasks requiring judgment about organizational politics, legal exposure, relationship nuance, or financial risk are outside what Cowork should handle unsupervised.
• Preview instability is real. Frontier features change, and UI or behavior can shift without much warning.

As I mentioned in the documents section, Cowork creates new files instead of editing in place, so the OneDrive Cowork folder is worth tidying up now and then.

On the security side: in May 2026, the security firm PromptArmor disclosed a way to exfiltrate files through a malicious custom skill. A poisoned SKILL.md could use indirect prompt injection to slip past the approval step and pull OneDrive or SharePoint files out, and it worked even against the Claude Opus model Cowork was running. Microsoft had not published a formal advisory at the time of writing. Since Microsoft does not validate custom skills, the practical defense is not to load skills from sources you do not trust, and to check your /Documents/Cowork/skills/ folder now and then.

Copilot Cowork: Governance, Security, and Admin Setup

This section is mainly for IT administrators and decision-makers evaluating deployment. If you are exploring Cowork on your own, skip ahead to the best practices section.

Setting up Cowork involves several required steps. The Microsoft 365 Copilot license needs to be active for target users. An admin with AI Admin, Security Admin, or Office Apps Admin rights enrolls the tenant in the Frontier program through the M365 Admin Center at Copilot > Settings > Frontier. Anthropic then needs to be enabled as a subprocessor at Copilot > Settings > View all > AI providers > Anthropic.

For EU, EFTA, and UK tenants, Anthropic is off by default and enabling it means LLM inferencing may occur outside the EU data boundary. A related setting called Flex Routing has been on by default for EU and EFTA tenants since April 2026, and it can send some processing outside that boundary during peak demand, so check it before you deploy. Organizations in GCC, GCC High, and DoD environments cannot currently use Cowork because the Anthropic subprocessor lacks FedRAMP certification.

Once setup is complete, admins can also pre-deploy and pre-pin Cowork for specific users or the whole organization. Three availability settings exist: all licensed users (the default), specific users or groups, or blocked entirely. The security group approach works best for phased rollouts, since region-based scoping is not a supported admin option.

Cowork operates within Microsoft's Enterprise Data Protection framework. Organizational data is not used to train Anthropic or OpenAI models. All activity is logged through Microsoft Purview, and responses display the most restrictive sensitivity label from whatever data Cowork used. For larger rollouts, Agent 365 (generally available May 1, 2026) adds enterprise observability and governance.

There is no separate price for Cowork. It is included with the Microsoft 365 Copilot license covered above, which is a paid add-on to a qualifying plan, so that license is the only line item. The Microsoft 365 E7 suite bundles it with other tools, but that is one way to get Cowork, not a requirement.

Before any broad rollout, run a structured pilot with a focused group. Project managers, executive assistants, operations teams, and sales operations tend to have the clearest coordination workloads to measure against. Track time saved, actions that needed corrections, and any governance or permission issues that surface.

How to Use Copilot Cowork Effectively

The biggest factor in output quality is specificity. Think of it as briefing a colleague rather than typing into a search box.

Start with low-risk tasks

Internal summaries, calendar suggestions, draft emails, and meeting prep are the right starting point. Leave sensitive external communication, legal content, and finance approvals for later, after you have seen how Cowork performs in your environment.

Write outcome-focused prompts

The same principles behind good prompt engineering apply here. A prompt that works well specifies the outcome, the sources, the constraints, and the approval rule in one go:

Prepare a one-page briefing for tomorrow's customer meeting using recent emails, related files, and open action items. Do not send or share anything until I approve it.

The approval instruction at the end is the part most people leave out. It does not change Cowork's behavior, since it will ask anyway, but stating it explicitly tends to produce tighter, more bounded outputs.

Use custom skills for recurring work

Custom skills let you define reusable instructions that Cowork loads automatically when a task matches the description. A skill for weekly status updates, one for customer follow-ups, one for internal reports. You can create up to 50 per user, stored in OneDrive at /Documents/Cowork/skills/[skill-name]/SKILL.md.

The folder path is case-sensitive: skills must be lowercase and SKILL.md must be uppercase. A newly created skill can take around 30 seconds to sync. If it does not appear in the slash command menu, prompt Cowork to resync. Since Microsoft does not validate custom skills, review any shared skill before loading it.

Custom skill folder structure in OneDrive. Image by Author.

Review before approving

If this sounds repetitive, that is on purpose. Before approving any action, check names, dates, file references, recipients, and tone, especially for anything going outside your team or any change that affects other people's time.

Example Prompts for Copilot Cowork

The prompts below give Cowork clear outcomes, named sources, and explicit approval constraints. Use them as starting points.

Meeting preparation:

Prepare a briefing for my next customer meeting. Use recent emails, related Teams messages, and relevant files. Include key discussion points, open questions, risks, and suggested next steps. Show me the draft before sharing it.

Follow-up email:

Draft a follow-up email for the meeting I just had. Include decisions, action items, owners, and deadlines. Keep the tone professional and concise. Do not send it until I approve.

Project status update:

Create a weekly project status update using recent Teams messages and related files. Include progress, blockers, owners, and next steps. Highlight anything that needs leadership attention.

Calendar management:

Review my calendar for this week and suggest changes that would create two focus blocks. Do not reschedule anything until I approve.

Scheduled daily briefing:

Send me a daily briefing every morning at 9 AM. Summarize my email, today's calendar, and any open action items from recent meetings.

They share one structure: name the sources, describe the format, set an approval boundary. That, more than the exact wording, is what produces usable results.

Is Copilot Cowork Worth It for Your Business?

The case for Cowork is specific. If your team loses hours each week to email prep, meeting management, status updates, and document creation, and you run on Microsoft 365, Cowork targets a real coordination problem.

The case for caution is equally specific, and I have touched on most of it already. Cowork is a preview feature, its behavior can change, the plugin ecosystem is still thin, and the approval step only works if users actually read what Cowork is about to do before confirming.

My read: the most sensible starting point is a structured pilot with a small group on low-risk workflows, tracking the same measures I listed in the governance section. Expand only when you understand where Cowork helps and where it introduces risk.

Treating it as a supervised execution layer, where it handles the coordination mechanics and humans stay accountable for outcomes, is the right posture. Treating it as an autonomous coworker is how you end up with emails you did not mean to send.

Conclusion

Copilot Cowork is an early example of workplace AI moving from content assistance to action. For Microsoft 365-heavy organizations, it targets a real source of daily friction: the coordination work that fills the gap between knowing what needs to happen and actually making it happen.

The honest takeaway: Cowork can cut down that coordination work for the right workflows, but it needs clear instructions, careful review, and governance. Used with those safeguards, it is worth piloting. Used without them, it is a faster way to make mistakes. It is also moving fast, so treat whatever you learn from a pilot now as a snapshot, not a final verdict.

If you want to get more hands-on with the wider Copilot family, our Introduction to Microsoft Copilot course covers prompting and working with Copilot across Microsoft 365, and our Microsoft Copilot Studio tutorial walks through building agents step by step.