It’s 8:40 on a Monday. You’ve got 137 unread emails, a 34-message thread from the client that started on Friday afternoon, and a meeting in twenty minutes that you’re fairly sure you agreed to but can’t quite remember why. This is the exact moment Copilot for Outlook is designed for — not the whole job of managing email, but the specific, grinding parts of it.
Copilot in Outlook is the assistant Microsoft built into the mailbox itself. It summarises long conversations, drafts replies in your tone, pulls action items out of a thread, and helps you prep for a meeting using whatever the attendees have already said to each other. What it doesn’t do is decide what matters. That judgement is still yours, and honestly, it’s the part that takes the real skill.
What you actually need before any of this works
Copilot in Outlook is not the free Copilot chatbot you’ve played with in a browser tab. It requires a Microsoft 365 Copilot licence attached to a work or school account — currently around $30 per user per month on an annual commitment — plus Outlook on the web or the desktop app. If your organisation runs Microsoft 365 Business or Enterprise, the admin has to assign the licence before the button even appears in the ribbon.
The plan structure confuses a lot of people, because there are now at least four different things called Copilot. If you’re trying to work out which one puts a summarise button inside your inbox, this breakdown of what each Microsoft Copilot plan actually costs is worth ten minutes before you buy anything.
The three jobs it genuinely handles well
1. Catching up on a thread you were copied into
This is the strongest feature by a distance. Open a long conversation, hit Summarise, and you get a short paragraph of what happened plus a list of open questions and decisions. On a 30 to 50 message thread with maybe four participants, it’s accurate more often than not, and it saves a solid ten minutes of scrolling.
Where it thins out: threads with heavy attachment traffic, or ones where half the context arrived in a separate call. Copilot only knows what’s in the email chain, so it will confidently summarise a decision without telling you the client reversed it by phone afterwards.
2. Drafting the reply you don’t want to write
Short replies to routine mail are where the drafting feature earns its keep. Asking for a three-sentence response that confirms a delivery date and asks for the invoice reference produces something usable 80% of the time. Longer, more political messages need more work — the same problem you’ll hit with Copilot in Word when drafting longer documents, where the first output is a starting point rather than a finished thing.
3. Turning a thread into a meeting
Copilot can look at a conversation and suggest a meeting, pull the relevant names, and draft an agenda from the points people raised. It’s not perfect — you’ll fiddle with the agenda — but it beats starting from a blank invite.
Where it stumbles, and how badly
Three failure modes show up repeatedly in day-to-day use:
- Invented commitments. Ask it to summarise what was agreed and it will occasionally produce a plausible-sounding deadline or deliverable that nobody wrote down. Always check dates and specific numbers against the original text.
- Default corporate tone. Out of the box, drafts read like someone who says “per my last email” unironically. Every reply needs a tone instruction or it sounds like a press release.
- Calendar and scheduling. Finding a slot across four calendars and writing the invite still involves more clicks than it should. The AI part works; the plumbing around it is clunky.
There’s also the habit of answering the wrong question. Ask it to “make this shorter” and you may get a version that drops the one sentence the recipient actually needed. It optimises for brevity, not for what your reader cares about.
Teaching it your voice is most of the work
The difference between Copilot being irritating and being genuinely useful in Outlook comes down to fifteen minutes of setup. Two features do the heavy lifting.
The first is personal context, in Settings under Copilot. You write a short description of your role, your audience, and how you write — “direct, no bullet points unless listing options, never use exclamation marks, address clients by first name.” Copilot folds that into every draft it produces from then on.
The second is coach by example, which lets you point at a sent email and say “write more like this one.” It’s the fastest way to get drafts that don’t need rewriting in your own accent. Most people skip both features, then conclude the drafting is mediocre. Fair conclusion, wrong cause.
The same principle applies across the suite. Copilot behaves noticeably better in Excel, where giving it a clean table range beats describing the problem in words, than it does when you leave it to infer structure. Feed it context, get better output.
Habits that separate a useful setup from a frustrating one
A few small practices that make the tool feel less like a novelty:
- Summarise before you read, not after. It’s a triage tool, not a review tool.
- Give tone instructions in the prompt itself: “one paragraph, apologetic but firm, no more than 90 words.”
- Draft, then edit. Treat the first output as a colleague’s rough version you’re going to fix.
- Keep a couple of strong sent emails as reference examples for coach by example.
- Never send a summary of a commercial negotiation without reading the source thread. Ever.
It’s also worth knowing how far the assistant reaches beyond the inbox. If email is the only place you’re using it, you’re paying for a lot of unused capability — this overview of what Copilot does across Word, Outlook and Teams covers where the rest of the licence actually goes.
The honest verdict on the money
At roughly $30 per user per month, Copilot for Outlook needs to save a licensed person about twenty minutes a week to break even on a straightforward hourly calculation. For anyone handling 50 or more emails a day — account managers, support leads, recruiters, anyone living in a shared inbox — the summarise and draft features clear that bar comfortably. For someone who sends fifteen emails a day and reads most of them in two minutes, it won’t.
The rollout pattern that seems to work: licence the heavy email users first, spend half an hour on personal context and coach by example with each of them, and let them report back after a month. The ones who set it up properly tend to keep it. The ones who clicked through onboarding and never touched the settings usually ask to have it removed.

