Independent field guide

Get real work done with Microsoft Copilot Cowork

A working reference for the agent that acts across your Microsoft 365 — what it actually does, where it helps, and the prompts to start with. Every claim cited to a primary source.

Last verified 2026-06-038 primary sources citedIndependently maintained

Every claim here is cited to Microsoft's own documentation and carries the “last verified” date shown above.

Start a conversation →

What it is

Microsoft 365 Copilot Cowork is an agentic AI assistant built into Microsoft 365. You describe the outcome you want; it breaks the request into a multi-step plan, carries out the work across your apps — Outlook, Teams, Word, Excel, and more — and pauses for your approval before any consequential action.

Last verified 2026-06-02

Executes, not just answers

Cowork executes work rather than just answering questions. You describe the outcome you want and it sends emails, schedules meetings, creates documents, posts in Teams, and manages your calendar on your behalf. [source]

Works across Microsoft 365

It acts across your whole Microsoft 365 environment: Outlook email and calendar, Teams channels and chats, Word/Excel/PowerPoint/PDF documents, and your files in OneDrive and SharePoint. [source]

Plans, then works steps

It is agentic: it breaks a request into a multi-step plan, works through the steps one by one in the background, shows each step in the conversation, and can pause to ask clarifying questions. [source]

You approve sensitive actions

You approve each sensitive action before it happens. Before sending an email, posting in Teams, or modifying a file, Cowork shows a preview and an approval prompt with a risk-level indicator for medium- and high-risk actions; you can approve once, skip future prompts for similar actions, or cancel. [source]

Grounded in your content

It can search and ground its work across your organization's content, run deep research that synthesizes multiple sources with citations, and run prompts on a schedule so recurring tasks happen automatically. [source]

Prerelease Frontier preview

Cowork is a prerelease feature available through Microsoft's Frontier preview program, launched in March 2026; capabilities and availability may change while it is in development. [source]

How to run a Cowork session

Last verified 2026-06-03

A repeatable way to hand real work to Cowork — five moves, each grounded in Microsoft’s documentation.

    1

    Start with the outcome, not the steps

    You describe the result you want in one request, and Cowork turns it into a multi-step plan — so you don't have to script the steps yourself.

    The Cowork home page has a chat input where you type or speak your request (up to 250,000 characters). Describe the outcome; you can start from a suggested prompt such as "Catch me up" or "Research a company" (these are examples, not a fixed list). [source]

    Try: Catch me up on what I missed this week and draft replies to anything urgent — don't send them yet.

    2

    Let it plan and work

    Cowork breaks your request into steps and works through them in the background, with checkpoints you can follow.

    When you hand off a task, Cowork turns your request into a plan and executes it with clear checkpoints so you can confirm progress or make changes. [source]

    Try: Hand off the goal, then watch the plan build and the checkpoints appear as it works.

    3

    Steer while it runs

    You stay in control mid-run instead of waiting for a result that went the wrong way.

    Queue a message to redirect (it's processed in order, and Cowork adjusts its approach). Pause to review — a soft pause finishes the current step, a hard pause stops immediately. Resume to continue, or Cancel to change direction. Cowork also pauses to ask clarifying questions when a request is ambiguous. [source]

    Try: Actually, focus only on the Henderson account and skip the internal threads.

    4

    Approve sensitive actions deliberately

    Cowork acts on your behalf, so each approval is a real decision — rubber-stamping defeats the safeguard.

    Before sending an email, posting in Teams, or scheduling, Cowork shows a preview of the exact content and a risk level for higher-impact actions. Review recipients, content, and parameters before you approve; avoid a blanket "Approve All" unless you've checked each item. [source]

    Try: Review the drafted email's recipients and body, then approve the send.

    5

    Make good sessions repeatable with Skills

    When a session works well, capture it so recurring work runs the same way without re-explaining it each time.

    A Skill is a reusable set of instructions — preferred structure, tone, and process — saved as a SKILL.md file in OneDrive /Documents/Cowork/skills/ (up to 50), so Cowork follows your approach instead of starting from scratch. [source]

    Try: Save a "Weekly status roll-up" skill describing the sections, tone, and which sources to pull from.

Examples

Last verified 2026-06-02

Each goal below is outcome-first — the steps show how Cowork breaks it into a plan, the way the framework above describes.

Executive

Clean up the week and protect focus time

Have Cowork review your Outlook calendar, flag conflicts and low-value meetings, then accept, decline, or reschedule them and add focus blocks once you approve, including a note to organizers when it declines. [source]

How Cowork breaks it down:

  1. CALRead your Outlook calendar for the week
  2. CALFlag conflicts and low-value meetings for your review in Calendar
  3. OUTDecline or reschedule the meetings you approve, with a note to each organizer in Outlook
  4. CALAdd focus blocks to the freed-up time in Calendar

Result: A cleaned-up week with protected focus blocks on your calendar.

Sales

Build the customer-meeting packet end to end

Ask Cowork to pull inputs from email, meetings, and files, schedule prep time, and produce a client-ready deck, a briefing document, and a draft customer status email with the latest files attached. [source]

How Cowork breaks it down:

  1. RESPull inputs from email, meetings, and the latest files in Research
  2. CALSchedule prep time on your calendar
  3. PPTProduce a client-ready pitch deck in PowerPoint
  4. DOCWrite a briefing document for the meeting in Word
  5. OUTDraft a customer status email with the latest files attached in Outlook

Result: A meeting packet: deck, briefing doc, and a draft customer email ready in Outlook.

Operations

Organize and reorganize project files

Tell Cowork to create SharePoint and OneDrive folders and move your existing files into them, so a scattered project workspace gets a clean structure without manual drag-and-drop. [source]

How Cowork breaks it down:

  1. ODReview your scattered project files in OneDrive
  2. SPCreate a clean folder structure in SharePoint and OneDrive
  3. ODMove your existing files into the new folders in OneDrive

Result: A reorganized project workspace with files sorted into clean folders.

Finance

Turn raw data into a reviewed workbook

Have Cowork process data, run the calculations, and build an Excel workbook with labeled tabs and supporting analysis you can check before it goes anywhere. [source]

How Cowork breaks it down:

  1. XLSProcess the raw data you provide in Excel
  2. XLSRun the calculations and supporting analysis in Excel
  3. XLSBuild a workbook with clearly labeled tabs for your review in Excel

Result: An Excel workbook with labeled tabs and analysis, ready for you to check.

HR

Draft and post a company announcement

Ask Cowork to write a policy announcement, post the update in the right Teams channel, and send a matching HTML newsletter by email, with you approving each send. [source]

How Cowork breaks it down:

  1. DOCWrite the policy announcement in Word
  2. TMSPost the update in the right Teams channel once you approve
  3. OUTSend a matching HTML newsletter by email after your approval in Outlook

Result: A policy announcement posted in Teams and emailed as a newsletter, each send approved.

Legal

Compile a research memo with sources

Have Cowork run deep research across web and work sources, organize findings with citations, and produce a structured memo with clear assumptions for you to review before anything is acted on. [source]

How Cowork breaks it down:

  1. RESRun deep research across web and work sources
  2. RESOrganize the findings with citations and clear assumptions in Research
  3. DOCProduce a structured research memo for your review in Word

Result: A structured research memo with cited sources, ready to review.

Support

Triage the inbox into folders

Tell Cowork to sort incoming email into folders, delete the noise, and draft inline replies to the threads that need a response, so your inbox is managed instead of just summarized. [source]

How Cowork breaks it down:

  1. OUTSort incoming email into folders in Outlook
  2. OUTDelete the noise from your inbox in Outlook
  3. OUTDraft inline replies to the threads that need a response in Outlook

Result: A triaged inbox with noise cleared and replies drafted for the threads that matter.

Engineering

Schedule a check-in in plain language

Say "set up a 30-minute check-in with Alex tomorrow at 2 PM" and Cowork creates the calendar event, adds the attendee, and can attach a prep document. [source]

How Cowork breaks it down:

  1. CALCreate a 30-minute check-in event for tomorrow at 2 PM in Calendar
  2. CALAdd Alex as an attendee in Calendar
  3. DOCAttach a prep document to the invite in Word

Result: A scheduled check-in with Alex invited and a prep doc attached.

Marketing

Stand up a launch plan and its assets

Delegate a launch workflow: Cowork builds a competitive comparison in Excel, distills it into a value-proposition document, and generates a customer pitch deck, plus milestones and owners. [source]

How Cowork breaks it down:

  1. XLSBuild a competitive comparison in Excel
  2. DOCDistill it into a value-proposition document in Word
  3. PPTGenerate a customer pitch deck in PowerPoint
  4. DOCLay out launch milestones and owners in Word

Result: A launch kit: competitive comparison, value-prop doc, pitch deck, and a milestone plan.

Drop-in assets

Last verified 2026-06-02

Prompts

Drop these straight into the Cowork chat.

Weekly status from my sent mailWhen: Friday wrap-up or before a manager 1:1, when you want a status you actually sent, not a guess.
Review the emails I sent and the Teams messages I posted in the last 7 days. Draft a concise weekly status update grouped by project, with what shipped, what's in progress, and what's blocked. Keep it under 250 words. Show me the draft before doing anything with it.
Triage my inbox into foldersWhen: Monday morning or after time off, when the inbox is overwhelming and you want it organized but not sent on your behalf.
Sort my unread email into the right folders: file newsletters and notifications, flag anything that needs a reply from me, and draft inline replies for the threads I clearly need to respond to. Don't send anything—leave the replies as drafts for me to review.
Draft and schedule a stakeholder updateWhen: Recurring exec or client updates where you want the synthesis done but keep the send under your control.
Draft a stakeholder update on [PROJECT] covering progress, risks, and next steps, grounded in our recent emails, meetings, and files. Format it as a clean email to [RECIPIENTS]. Show me the preview; once I approve, schedule it to send at [TIME].
Build a deck from a documentWhen: You have a written doc or memo and need a presentable deck without rebuilding it slide by slide.
Turn the attached document into a PowerPoint deck: a title slide, one slide per major section with 3-5 bullets each, and a closing next-steps slide. Keep the language plain and outcome-focused. Save it to my OneDrive and show me the result before sharing.
Clean up my calendar for the weekWhen: Sunday or Monday, when the week is overbooked and you want focus time protected.
Review my calendar for next week. Flag conflicts and low-value or optional meetings, and propose declines, reschedules, and 2-hour focus blocks. Tell me your reasoning, then apply only the changes I approve. Include a brief, polite note to organizers when you decline.
Deep research a companyWhen: Prepping for a sales call, partnership, or diligence and you need cited, organized inputs fast.
Research [COMPANY] across web and our internal sources, prioritizing primary financial data (earnings, filings) and recent news. Produce: (1) an executive summary formatted for email, (2) a structured memo with stated assumptions and citations, and (3) an Excel workbook with labeled tabs. Flag anything you're unsure about.
Meeting recap to my teamWhen: Right after a meeting, to get decisions and owners captured while they're fresh.
From the notes I'm attaching, draft a meeting recap email to [TEAM]: decisions made, action items with owners, and the next meeting date. Post the same summary in our [CHANNEL] Teams channel. Show me both before sending or posting.
Turn meeting notes into a formatted reportWhen: You captured messy notes and need a clean, shareable document out of them.
Take my rough meeting notes (attached) and turn them into a formatted Word report with an overview, key points, decisions, and action items. Use clear headings. Save it to my OneDrive and show me the draft.
Reorganize a messy project folderWhen: A project workspace has become a flat dumping ground and you want structure without manual sorting.
Look at my files for [PROJECT] in OneDrive/SharePoint. Propose a folder structure (by phase or document type), then create the folders and move files into them once I approve. Tell me about any files you're unsure where to place.
Daily briefing for tomorrowWhen: End of day, to walk into tomorrow already oriented.
Give me a briefing for tomorrow: my meetings with short context and any prep needed, the emails or messages awaiting my reply, and my top open action items. Keep it scannable.

Task setups

Recurring scheduled prompts — set them once.

Monday 8am Teams activity summaryWhen: You manage a busy channel and want a weekly digest without scrolling back through it.
Scheduled prompt: "Every Monday at 8 AM, summarize last week's activity in my [PROJECT] Teams channel—key decisions, open questions, and anything addressed to me—and send it to me as a message." Set this from the Scheduled tab in Tasks, or just state the cadence in chat.
Daily 9am briefingWhen: You want a consistent start-of-day orientation that arrives automatically.
Scheduled prompt: "Send me a daily briefing every morning at 9 AM covering today's meetings, prep needed, and emails awaiting my reply." Cowork sets up the schedule from your plain-language request; manage it later from the Scheduled tab.
Friday weekly status draftWhen: You file a recurring status and want the first draft waiting for you each Friday.
Scheduled prompt: "Every Friday at 3 PM, draft my weekly status from the emails I sent and Teams messages I posted this week, grouped by project, and leave it as a draft for me to review." Drafts only—no auto-send.
Monthly stale-file sweepWhen: You want lightweight, recurring data hygiene to keep org search results accurate.
Scheduled prompt: "On the first of each month, list files in my [PROJECT] SharePoint folder that haven't been touched in 90+ days and suggest which to archive." Review and approve any moves yourself.

Templates

Checklists and skeletons to work from.

Approve-with-confidence checklistWhen: Any action that sends, posts, or shares something outside your own drafts—especially external email and public Teams posts.
Before you click approve on a Cowork action, take five seconds:
1. Recipient/destination correct? (right person, right channel, internal vs. external)
2. Read the actual preview—not just the summary.
3. Facts and numbers traceable to a real source?
4. Tone and sensitivity right for who'll see it?
5. Reversible if wrong? If not, slow down.
This isn't red tape—it's how you get good results and avoid sending the wrong thing.
First 5 tasks to try with CoworkWhen: First week with Cowork, or onboarding a teammate to it.
Start low-stakes to learn how Cowork behaves:
1. "Give me a daily briefing for tomorrow." (read-only, no approvals)
2. "Triage my inbox into folders and draft replies—don't send."
3. "Turn these meeting notes into a formatted Word report."
4. "Clean up my calendar for next week—propose changes, I'll approve."
5. "Draft a stakeholder update on [PROJECT] and show me the preview."
Notice where it nails it and where you have to steer—that calibrates how much to delegate.
Delegation-readiness checkWhen: Deciding whether a given task is a good fit for Cowork versus doing it yourself.
Before you hand a task to Cowork, ask:
- Is the outcome clear enough to describe in one or two sentences?
- Are the inputs (files, recipients, dates) available and named?
- Are my Microsoft 365 permissions correct for everything this touches? (Cowork inherits them.)
- Is this reversible, or does it need a careful approval pass?
- Who's accountable for the result—me. If yes to clarity and ownership, delegate it.
Good-prompt skeletonWhen: Any time a quick one-liner prompt isn't producing what you wanted.
Outcome: what "done" looks like.
Inputs: which files, people, threads, or data to use.
Format: email / Word / Excel / deck / Teams post, and length or structure.
Constraints: tone, recipients, what NOT to do (e.g., "don't send").
Approval: "show me before you send/post/share."
Fill these five lines and Cowork has what it needs to act accurately.
Custom skill / plugin vetting noteWhen: Before adopting any non-built-in skill or plugin for real work.
Before trusting a custom skill (SKILL.md in OneDrive) or a third-party plugin:
- Microsoft does NOT validate these—quality is on the author.
- Run it on a sample task and inspect the output closely.
- Confirm it only touches data it should.
- Note who owns/maintains it and when it was last updated.
Document the result so your team isn't re-vetting the same skill twice.

Concerns & fixes

Last verified 2026-06-02

Cowork can misread ambiguous or broad instructions and take actions that don't match what you meant.
Front-load specifics (recipients, format, scope) and use the approval preview to catch a wrong action before it executes. [source]
Outputs can contain inaccurate information, especially when the underlying organizational data is incomplete or outdated.
Treat results as drafts, spot-check facts against source documents, and clean up stale or duplicate content in SharePoint/OneDrive before relying on org-wide search. [source]
Complex, multi-step tasks with many dependencies don't always complete as expected.
Break large jobs into smaller delegations, watch the step-by-step progress in the conversation, and pause if a dependency looks wrong. [source]
Review burden: because Cowork acts rather than just answers, each approval is a real decision, and rubber-stamping defeats the safeguard.
Reserve "don't ask again" for genuinely low-risk, repetitive actions, and actually read the preview for anything that leaves your control (external email, public posts). [source]
It is a prerelease Frontier feature, so behavior, availability, and capabilities can change and may be unstable.
Pilot on low-stakes work first, keep a human in the loop on anything consequential, and revisit your prompts and scheduled tasks as the product evolves. [source]
The hard part is organizational readiness, not the technology: governance, accountability, and data hygiene determine whether Cowork is safe to scale.
Confirm Microsoft 365 permissions are correct (Cowork inherits them), decide who is accountable for approved actions, and tidy data before broad rollout. [source]
Blanket "Approve All" or rubber-stamping approvals undoes the safeguard — Cowork can then send or post something you never actually checked.
Approve actions one at a time, reviewing each preview (recipients, content, parameters); reserve "Approve All" for batches you've already verified. [source]
Cowork is easy to confuse with other agentic Copilot features (Agent Mode in Word/Excel/PowerPoint, Researcher, Analyst, Copilot Studio agents) — guidance for those doesn't necessarily apply.
Treat Cowork as its own surface: the Frontier feature that delegates multi-step work across your apps with per-action approvals. Don't apply Agent Mode or Researcher/Analyst instructions to it. [source]

Get your team to value in days

Want your team getting real value from Cowork in days, not months? We help you pick the right first tasks, build the prompt library, and set the guardrails.

Start a conversation →