Microsoft Copilot Cowork — Complete Use-Cases Guide

The hub for this series — Microsoft Copilot Cowork — The Complete Guide — covers what Cowork is and how it works. This spoke is the by-role use-case reference.

How to read this page

Each role section has:

• The pain point — the recurring work this role wants Cowork to handle
• Sample Cowork prompt — copy-paste-ready
• What Cowork does — the steps it runs across apps
• Realistic time saved — based on a typical week
• Watch-out — what to brief the user on before they try it

💡 One assumption throughout: these scenarios assume the data lives in your Microsoft 365 — Outlook, Teams, SharePoint, OneDrive, calendar, meeting transcripts — or in an approved Cowork plugin or custom skill. If a system is external (Salesforce, ServiceNow, an HR or expense platform, Entra admin reports), Cowork needs a connecting plugin, a custom skill, or an exported file first.

The four Cowork personas — and where these roles fit

Microsoft groups Cowork users into four personas, each with a different mix of light, medium, and heavy tasks — it’s the same lens the pricing spoke uses to estimate cost. Here’s how the seven roles below map onto them:

The mapping isn’t rigid — plenty of people wear two hats — but it’s a useful way to picture who runs which kind of task, and therefore where your Cowork credits go. To put a number on it, run your team through the Cowork Cost Calculator.

🧑‍💻 IT Admin

IT Administration

The pain point: Status reporting. The data lives in Entra, the discussion lives in Teams, the write-up lives in your head — and someone wants it by Friday.

A second one I lean on for the weekly ops review:

Realistic time saved: A weekly security or ops status that used to mean an hour of report-pulling and writing becomes ten minutes of review.

Watch-out: Cowork only sees what you can see — it won’t surface sign-in data you don’t already have rights to. Always read the numbers yourself before they go to a security DL.

More IT plays worth a try — each tagged with its task tier:

• Daily sign-in anomaly sweep (Snack) — “From this morning’s exported Entra sign-in report, flag anything unusual — failed-MFA spikes, sign-ins from new locations, or risky users — and give me a short list to check.” (Needs the report exported, or an approved Entra/Graph plugin.)
• Weekly patch + ticket digest (Meal) — “Pull this week’s patch-status export and the related support tickets, and give me a one-page digest: what’s patched, what’s outstanding, and the ticket themes worth raising at the ops review.”
• Incident timeline reconstruction (Feast) — “For [incident], rebuild the timeline from my email, Teams, and the ticket export — who was involved, what changed when, and the open follow-ups — into a single write-up I can share.”

💼 Sales

Sales & Account Management

The pain point: Walking into a call cold. The context is there — emails, the last proposal, the support history — it’s just scattered across four places and you have twenty minutes.

And to close the loop after the meeting:

More sales plays worth a try — each tagged with its task tier:

• Monday account sweep (Meal) — “Every Monday, look across my accounts — recent emails, meetings, and open threads — and give me the three things that need my attention this week, with a suggested next step for each.”
• 1:1 prep on one account (Meal) — “I have a 1:1 about [account] tomorrow. Pull our recent history — emails, meetings, open actions — into a one-page picture so I walk in current.”
• Find the best place to grow (Feast) — “Look across my accounts and suggest where there’s room to expand, with the signal behind each suggestion.” (Needs your CRM connected as a plugin, or an exported account list — see the assumption above.)

Realistic time saved: Pre-call research that’s normally 30–45 minutes of digging becomes a one-page brief you review and tidy in 10–15.

Watch-out: Cowork drafts the follow-up; you still own the relationship. Read every customer-facing word before it sends — that’s exactly what the checkpoint is for.

👥 HR

Human Resources

The pain point: Coordination work that spans systems — onboarding, reviews, feedback — where a missed step is the thing people remember.

For the sensitive, theme-finding work:

More HR plays worth a try — each tagged with its task tier:

• New-hire welcome pack (Snack) — “Draft a warm welcome email and first-week schedule for [name] starting Monday, from our standard onboarding checklist.”
• Onboarding coordinator (Meal) — “Walk our onboarding checklist for [name], check what’s already done across email and SharePoint, and tell me what’s still open — then draft the bits that are ready.”
• Review-cycle theme map (Feast) — “Pull this round of performance reviews into anonymised themes — strengths, common gaps, and where managers disagree — without naming anyone.”

Realistic time saved: Onboarding prep that’s normally scattered across five systems becomes one coordinated pass you sign off.

Watch-out: Performance and review content is sensitive. Keep the “flag before sharing” checkpoint on, and make sure the output is anonymised before it leaves your hands.

💰 Finance

Finance & Operations

The pain point: Month-end. Pulling actuals, matching them to budget, finding the variances worth a comment — accurate, repetitive, and slow by hand.

And the monthly expense reconciliation:

More finance plays worth a try — each tagged with its task tier:

• Month-end status line (Snack) — “Give me a two-line read on where we are against budget this month, from the latest actuals in [file].”
• Variance pack with commentary (Meal) — “Build the Q2 variance report from the approved budget and the actuals file — flag anything over 10% and draft a short note on each.”
• Spend-drift review (Feast) — “Look across the last two quarters of spend and tell me where costs are drifting, with the signal behind each flag.” (Needs the data in Excel or a connected source — see the assumption above.)

Realistic time saved: Variance reporting that can eat half a day becomes a solid first draft you refine.

Watch-out: Numbers are only as good as the files Cowork reaches. Confirm it pulled the approved budget, not a working copy, before anyone makes a decision on it.

📢 Marketing

Marketing & Communications

The pain point: Producing a lot of on-brand output fast — posts, summaries, talking points — without losing the voice.

For staying ahead of the market:

More marketing plays worth a try — each tagged with its task tier:

• Monday standup brief (Snack) — “Pull my week’s progress, blockers, and what’s next into a short standup update — from my calendar, sent mail, and Teams.”
• Campaign board from a brief (Meal) — “Turn this campaign brief into a working board — workstreams, owners, and key dates — so we’re not building it from a blank page.”
• Launch kit in one pass (Feast) — “From our approved messaging, draft the launch kit: a customer email, a blog draft, three social posts, and a one-page sales sheet — all on-message. Show me each for review.”
• Messaging-drift audit (Feast) — “Check every asset in [folder] against our approved messaging and flag anywhere the wording has drifted — without changing anything.”

Realistic time saved: A competitor round-up plus talking points goes from an afternoon of work to a draft you refine in 15–20 minutes.

Watch-out: Brand tone is yours to approve. Cowork drafts; you sign off the voice every time.

🏢 Executive

Leadership & Executive

The pain point: Protecting your time and walking in prepared — calendar triage and briefing prep that never quite fit into the day.

And before the big meeting:

More executive plays worth a try — each tagged with its task tier:

• Daily clear-down (Snack) — “Triage my inbox from overnight — what actually needs me today, and what can wait or be delegated?”
• Pre-1:1 brief (Meal) — “Before my 1:1 with [name], pull our recent threads, open actions, and anything they flagged into a one-page picture.”
• Board-pack reader (Feast) — “Read the board pack for Thursday and give me the decisions I’m being asked to make, the numbers behind each, and the three questions I should push on.”

Realistic time saved: Calendar triage and board prep — the two things that always slip — get handed off and come back as a draft.

Watch-out: Cowork will propose reschedules; it won’t send them without your nod. Keep the checkpoint on so nothing leaves your calendar by surprise.

🤝 Customer-facing (Solution Engineers, CSAs, Account Managers)

Customer-facing roles

This is my own role, so I’ll be honest: it’s the one that felt Cowork’s value the fastest. The work already bookends every customer call — prep before, follow-up after — and it’s already cross-app and cross-time. That’s exactly the shape Cowork is built for.

The pain point: Every customer session needs a prep pass (who, what’s the history, what did we last promise) and a follow-up pass (recap, action items, the doc you said you’d send). Both are real work, both are repetitive, and both happen on days that are already full.

Then, after the session:

More customer-facing plays worth a try — each tagged with its task tier:

• Pre-call refresher (Snack) — “Two-minute version: where did we leave things with [account], and what did I promise to send?”
• Session prep brief (Meal) — “I have a session with [account] on [topic] on Thursday — pull our history, the last deck, and the latest from Microsoft Learn into a one-page brief.”
• Follow-up kit (Feast) — “From today’s session transcript: draft the recap email, the action list, and the one-pager I promised — show me each before anything goes to the customer.”

Realistic time saved: The prep-and-follow-up that wraps around every customer call is the part I now delegate — easily an hour back on a heavy meeting day.

Watch-out: Anything customer-facing gets the checkpoint, every time — Cowork never auto-sends to a customer. I keep my prep tasks read-first for the same reason: I want to see the brief before I trust it, not after.

Common patterns across all roles

Three patterns repeat across every role’s best Cowork use:

1. Outcome-first prompts (not process prompts)
2. Multi-app coordination Cowork handles the stitching you used to do by hand
3. Pre-approval checkpoints for anything sensitive

Other Cowork spokes

• Cowork: How to use it step by step
• Cowork: Prompts to try
• Cowork: Pricing and cost management
• Cowork: Skills and plugins
• Cowork: Admin enablement and governance
• Cowork: On mobile