Copilot Cowork for Executive Assistants: 5 Workflows That Save 2 Hours a Day

Copilot Cowork has been sitting in the Microsoft 365 Frontier preview since March 9, quietly racking up search traffic — 27,100 people looked up “copilot cowork” in March alone — while almost nobody wrote about what it actually does for the people who would use it most. Executive assistants spend half their day triaging inboxes, scheduling across four time zones, and drafting the same kinds of emails over and over. Cowork was built to do all of that. Not as a better search bar. As a coworker that actually sends the email, moves the meeting, and posts the Teams update — with your approval, one step at a time.

The docs are written for IT admins. The news coverage is written for CIOs. This is the piece written for the EA who has to use it on Monday morning.

What Copilot Cowork actually is

Think of it as a second you — one that lives inside Microsoft 365, reads your calendar, knows who your exec’s people are, and can be told in plain English to “clear Tuesday afternoon for a heads-down writing block, then tell the two reschedules why it moved.”

The name is literal. Copilot used to chat about your work. Cowork actually does it. You describe an outcome, Cowork plans out the steps, executes them in the background, and pauses for your approval before sending anything sensitive. When the email goes out, it goes out from you. When the meeting moves, it moves on your calendar. The side panel shows every step — no black box, no mystery.

Under the hood it’s a hybrid model. Microsoft built the agent and the integrations; Anthropic’s Claude is the actual reasoning engine doing the planning. That’s why the language understanding is as good as it is — you can say “clean up my inbox, but leave anything from the board alone” and Cowork knows what “the board” means from your Work IQ (the Microsoft-ism for “everything you’ve emailed, met with, or stored across 365”).

Here’s what’s shipping as of today:

• Launched: March 9, 2026
• Available: Microsoft 365 Frontier preview (US, English), in your browser at m365.cloud.microsoft and in the Copilot desktop app for Windows and Mac
• 13 built-in skills ship by default: Word, Excel, PowerPoint, PDF, Email, Scheduling, Calendar Management, Meetings, Daily Briefing, Enterprise Search, Communications, Deep Research, and Adaptive Cards
• Custom skills: up to 20, stored in your OneDrive at /Documents/Cowork/skills/
• Pricing: bundled with Microsoft 365 Copilot at roughly $60/user/month (E5), or $99/user/month under the new E7 Frontier Worker Suite going GA May 1, 2026
• Requires: enrollment in the Frontier preview program (your IT admin toggles this on in Microsoft Admin Center → Copilot → Settings → Frontier)

That last line is the one most EA-targeted blogs skip. If Cowork doesn’t show up when you sign in, it’s not broken — your tenant probably isn’t Frontier-enrolled yet. Send your IT admin the Admin Center path above and ask nicely.

How to turn it on

Assuming the license is already there:

1. Go to m365.cloud.microsoft in your browser (or open the Copilot desktop app)
2. Sign in with your work account
3. In the left sidebar, click Agents
4. Find Cowork (Frontier) in the Agent store
5. Click Add
6. Cowork now appears permanently in your left nav under Agents

First-run experience is a simple chat. Type what you need, hit enter, watch it plan.

5 workflows that cover most of an EA’s day

I’m going to skip the “automate everything” fantasy and focus on five concrete tasks that real EAs repeat every week. Cowork does all five without custom setup. The prompts below are the exact words to type.

1. The 8:30 AM morning briefing

Every EA needs to know what the exec’s day looks like before the exec does. Cowork’s Daily Briefing skill pulls from your Outlook calendar, unread emails flagged as important, and any Teams mentions since yesterday, then drops a summary in your inbox or Teams — on a schedule.

The one-time setup prompt:

“Every weekday at 8:30 AM, send me a daily briefing with my first three meetings, any new emails from [exec’s name] marked important overnight, and anything I was @-mentioned in on Teams since yesterday evening. Deliver it to my inbox.”

Cowork sets up the scheduled prompt, runs it at 8:30 AM the next workday, and keeps running until you tell it to stop. The Scheduled tab in Cowork’s task view shows the next run time. You can edit the prompt any time the exec’s preferences change (“add anything from the CEO,” “ignore the HR newsletter”).

This replaces the 20 minutes most EAs spend at 7:30 AM building this by hand. It also replaces the one you’re using now with the separate apps you bolt together.

2. Cross-stakeholder scheduling in one sentence

Traditional scheduling means checking four calendars, finding the intersection, sending a proposed time, waiting for two reschedule requests, and finally locking it in after three emails. Cowork does the finding step natively because it’s already looking at the whole company’s free/busy data.

The prompt:

“Find 45 minutes next week for [exec name], [stakeholder 1], [stakeholder 2], and [stakeholder 3] to meet about the Q3 planning doc. Prefer Tuesday or Wednesday afternoon. Include a Teams link. Attach the doc from Alex’s OneDrive. Send the invite in my name, not yours.”

Cowork finds the slot. It drafts the invite with a subject line it pulls from the doc’s title. It pastes in a one-line agenda generated from the doc’s exec summary. It pauses. The Send button appears in your chat with a medium-risk indicator. You glance at it, tweak the subject line if you want, click Send.

You can lower the friction by toggling “skip this prompt for similar actions” for routine scheduling — so next Tuesday’s “schedule the weekly staff meeting” goes out without you clicking. Medium-risk approvals stay on for external invites.

3. Meeting follow-up that doesn’t feel AI-written

After a 45-minute meeting, the recap email is the task EAs most hate doing and most have to do anyway. Cowork’s Meetings skill combines the Teams transcript (if the meeting was recorded) with the Communications skill’s tone-matching to produce a follow-up that sounds like the exec.

The prompt:

“Draft a follow-up email from [exec name] to the attendees of the 2 PM meeting. Summarize the three decisions, list the five action items with owners, keep tone warm but direct. Don’t mention the video link. Then post a one-paragraph version to the [project channel] Teams channel.”

Cowork drafts both the email and the Teams post. The side panel shows the Email skill, then the Communications skill, both active. Two approval prompts appear — one for the email, one for the Teams post, each with the action-matching button label (“Send” and “Post”). You approve each separately. If the exec prefers different phrasing, say so in chat — “tighten the opening, drop ‘I wanted to reach out’” — and Cowork redrafts.

The time saved per meeting is small (maybe 10 minutes). The time saved per week is not, because most EAs do this for 8 to 15 meetings.

4. Vendor onboarding and contract filing in SharePoint

The thankless paperwork job. A new vendor comes in. Someone needs to create the SharePoint folder, move the contract PDF, name it correctly, notify finance, and log it in the tracking spreadsheet.

The prompt:

“The signed contract for [Vendor Name] just arrived in my inbox with subject [Contract - Vendor Name]. Create a new folder at /SharePoint/Contracts/2026/Vendor-Name. Move the PDF there with the filename ‘Vendor-Name-MSA-2026-04-24.pdf’. Add a row to the Vendor Tracker spreadsheet with the vendor name, contract date, amount, and renewal date pulled from the PDF. Then email the finance team at finance@acme.com with a short note and the SharePoint link.”

Cowork loads the PDF skill (to parse the contract), the Excel skill (to write to the tracker), the Email skill, and the file-organization capabilities. Each step shows in the side panel. You get one approval prompt for the email — not for the file ops, which are low-risk. Takes 90 seconds from prompt to finish.

This is the workflow that turned around two IT directors I spoke to. Not because it’s AI magic. Because it’s the first time their EAs didn’t have to context-switch between four apps to complete one piece of paperwork.

5. A weekly custom skill that runs itself

Cowork’s hidden power is that you can write your own skills using a plain Markdown file. Think of it as a recipe card that lives in OneDrive and tells Cowork how to handle a recurring task your way. You get 20 slots.

Create a file at Documents/Cowork/skills/weekly-exec-summary/SKILL.md in your OneDrive. The file contents can be as simple as:

# Weekly Exec Summary

When the user runs this skill, do the following:

1. Pull all meetings from [exec name]'s calendar for the past 7 days.
2. For each meeting with notes or a transcript, summarize the decisions and owners.
3. Pull emails from the past 7 days where [exec name] is sender or primary recipient with flag status "important".
4. Compile into a one-page Word doc with three sections: Decisions Made, Open Items, People to Follow Up With.
5. Save to /SharePoint/Exec Office/Weekly Briefs/ with filename "exec-weekly-YYYY-MM-DD.docx".
6. Post the doc link in the #exec-office Teams channel with a one-sentence summary.

Stop before posting and show me a preview.

Save it. Open a new Cowork conversation. Say “run the weekly exec summary skill.” Cowork finds the SKILL.md, loads it, and executes it. You can also schedule it — “run the weekly exec summary skill every Friday at 4 PM.”

That one skill replaces the whole Friday ritual of pulling a recap together. It gets shared across the EA team by copying the folder. The /skills command inside a conversation lists all your skills, including ones you’ve created — type it in and Cowork pulls them up in the side panel.

Maximum size per skill file is 1 MB, which is roughly 200,000 words of instructions. You will not run out of room.

What it can’t do

Every honest product writeup needs this section. Here’s what Cowork isn’t, today.

It’s not leaving the Microsoft tenant. Your third-party tools — Gmail (if you still use it), Notion, Asana, Salesforce outside Microsoft’s connector — are invisible to Cowork. If your exec lives in Notion, Cowork is half a product. This will likely expand as Microsoft adds connectors, but right now, if it’s not in 365, it’s not in Cowork.

It’s English-only and US-first. International tenants are getting it in waves. Other languages are on the roadmap but not shipped.

It asks for approval a lot at first. Every email. Every invite. Every Teams post. You can flip “skip similar prompts” for safe, repetitive tasks, but until you do, there’s a lot of clicking. The approval UX is a feature, not a bug — Microsoft is being careful about the agent hitting Send — but for an EA used to auto-sending, it takes a day to get used to.

It occasionally chooses the wrong tone. The Communications skill is built on Claude, which is strong but not psychic. First-time drafts will sometimes sound a notch more formal or a notch more casual than your exec’s voice. One correction in chat usually fixes it; after a few conversations it calibrates. Cowork does not permanently learn your exec’s voice across conversations — each new conversation starts with the base model. This will change as Microsoft adds memory; today, plan for occasional small tone fixes.

It isn’t cheap if you’re paying from scratch. If your org already has M365 Copilot at $30/user, Cowork is included in Frontier. If you’re starting from a base M365 plan, getting to Cowork means upgrading to E5 plus Copilot (~$60 combined) or the new E7 Frontier Worker Suite at $99/user when it goes GA May 1. That’s a real number. Worth it for a revenue-facing exec; harder to justify for a team that mostly schedules recurring stand-ups.

Copilot Cowork vs Claude Cowork — the version your IT team will ask about

A lot of EAs are going to hear “Cowork” from two different vendors and wonder what’s going on. Microsoft’s is the one integrated into 365. Anthropic has a separate product called Claude Cowork that runs as a desktop app on your own laptop and works with any file on your machine — but it doesn’t see your company’s calendar or email.

Here’s the real difference:

For an EA, Copilot Cowork is almost always the right answer because your exec’s world already lives in Outlook and Teams. Claude Cowork is better if you’re a solo consultant or a developer who mostly works with local files.

What this means for you

If you’re an executive assistant: Start with the morning briefing (workflow #1). It’s the lowest-risk, highest-frequency task, and the scheduled-prompt UI is the friendliest on-ramp to Cowork. Once the 8:30 briefing lands reliably for a week, add the meeting follow-up workflow. By week three you’ll have 8–10 hours a week back — not because Cowork is faster than you at any single task, but because it holds context across them. You’re not the one tab-switching between Outlook, the transcript, and the project channel anymore.

If you manage EAs or assistant teams: The /skills system is what makes this scale across your team. One EA writes a SKILL.md for the “VIP visitor logistics” workflow, shares the OneDrive folder, and suddenly every assistant in the org has the same playbook. This is the productivity-team dream: best practice as a file that travels. Budget a half day for a shared skills library — that’s where the compounding starts.

If you’re in IT and an EA just asked you to turn it on: Your admin path is Microsoft Admin Center → Copilot → Settings → Frontier. You need to verify Anthropic is enabled as a subprocessor in your tenant (Cowork won’t run without it), and you should decide your org’s stance on the new E7 Frontier Worker Suite before May 1 — the pricing jump from E5+Copilot to E7 is real.

If you’ve never used Copilot at all: Cowork is not the place to start — it’s the advanced version. Start with regular Microsoft 365 Copilot chat for a month, get fluent at describing tasks in natural language, and then graduate to Cowork when you want Copilot to actually do the thing, not just write the draft.

The bottom line: Cowork isn’t a productivity hack. It’s a quiet reorganization of how EA work gets done. The five workflows above cover maybe 40% of a typical EA’s week. The other 60% is judgment, relationships, and the reason your exec hired a human in the first place. Cowork isn’t coming for that part. It’s coming for the part you wish you didn’t have to do.

Who should use it

• EAs supporting a C-level exec where email + calendar + Teams load is dominant
• Chiefs of staff managing cross-functional meetings and follow-ups
• Operations managers handling vendor paperwork, contracts, and shared-doc trails
• Any Microsoft 365 power user in the Frontier program who’s tired of context-switching between 6 apps to complete 1 task

Probably skip if: your org isn’t on Microsoft 365, most of your work lives in Google Workspace or Notion, or you haven’t gotten comfortable with regular Copilot chat yet.

The bottom line

Microsoft shipped Copilot Cowork seven weeks ago and it’s been growing at about 903× its pre-launch search volume. The March spike to 27,100 monthly searches is what the /copilot cowork keyword looks like when IT directors start getting asked about it by their EA teams on Monday mornings. If your org is Frontier-enrolled, it’s waiting in your agent store. If it’s not yet, your licensing renewal conversation just got more interesting.

Try the morning briefing first. Give it three days. If at the end of day three you’re not missing that 20-minute manual slog, keep going. If you are, tell it to do what it was doing wrong and watch it fix itself. The learning curve is in plain English.

Sources:

• Copilot Cowork: A new way of getting work done — Microsoft 365 Blog
• Copilot Cowork: Now available in Frontier — Microsoft 365 Blog
• Cowork overview (Frontier) — Microsoft Learn
• Use Cowork (Frontier) — Microsoft Learn
• Get started with Cowork (Frontier) — Microsoft Support
• Cowork common questions (Frontier) — Microsoft Learn
• Creating Custom Skills for Copilot Cowork — Russ McKendrick
• How to create Custom Skills in Copilot Cowork — Rob Quickenden
• Claude Cowork vs. Copilot Cowork — Data Science Dojo
• Copilot Cowork — A Practical Guide to Getting Started — GadellNet
• Microsoft Copilot Cowork: The Complete Guide — A Guide to Cloud & AI