Copilot in Outlook: thread summary and meeting prep

If reply drafting is Copilot in Outlook's showpiece, summarisation is what people quietly use ten times a day. The Summary by Copilot button at the top of a thread collapses forty messages into a paragraph with citations; the meeting prep brief in the calendar tells you what a meeting is about before you walk in. Both have shipped, both work, and both are trusted a little more than they should be. This guide explains what each actually reads, what the citations mean, and where the summaries mislead.

Summary by Copilot

Open a thread and a Summary by Copilot bar appears above it. Click it and Copilot produces a short summary of the conversation — who asked for what, what was decided, what's open — with numbered citations that jump to the message each point came from.

What it does well:

• Long, drifting threads. The classic "thirty replies, subject line no longer relevant" chain. Copilot pulls out the two decisions and the one unresolved question, and the citations let you verify each in a click.
• Threads you were added to late. Instead of scrolling to the bottom and reading upward, you get the story.
• Threads with attachments named in the mail. It'll note that a document was shared, though it doesn't summarise the attachment's content from the thread view.

The citations are the important part. Each numbered marker links to a specific message; hovering shows the source. A summary with citations is checkable; a summary you don't check is a rumour. Train people to click at least the citations on anything they're about to act on.

Where summaries mislead

Recency and emphasis. Copilot doesn't reliably weight the latest position in a thread over earlier ones. If someone proposed X, three people objected, and the proposer then withdrew, the summary can still lead with "the team proposed X."

Tone is flattened. An angry thread becomes "the customer raised concerns." That's polite and it loses information you need.

It reads the thread as Outlook has it. Messages you deleted, forks where someone replied only to a subset, and messages held in quarantine aren't there. The summary is of your copy of the conversation.

Attachments aren't read. The thread summary reads mail bodies. To understand a document that was attached, open it and use Copilot there, or ask Copilot Chat about the file.

Very short threads get padded. A two-message thread produces a summary longer than the thread. That's not useful; the feature is for long conversations.

Meeting prep: the "Prepare" brief

In the Outlook calendar (and in the Teams calendar), Copilot can generate a pre-meeting brief — sometimes surfaced as Prepare, sometimes as a summary card on the meeting — that draws together the invitation body, the related email threads, files attached or linked to the invite, and, for recurring meetings, the previous occurrence's recap if one exists. Microsoft's more recent iteration sends the brief proactively for meetings that have enough context, rather than waiting to be asked.

What it contains, when it works:

• The meeting's purpose as stated in the invite (or inferred from the subject and thread).
• Recent related email — usually threads with the same subject or the same participants.
• Files attached to the invite or referenced in those threads.
• For recurring meetings with Teams recap enabled, the last meeting's notes and open action items.

That last point is the one worth caring about: for a weekly project meeting, "here's what you agreed last week and what's still open" is genuinely valuable and takes zero effort.

Where meeting prep falls short

Context is inferred, not known. "Related" email is a heuristic. For meetings with generic subjects ("Sync," "Catch-up"), the brief is thin or picks up the wrong threads.

External meetings. If the substance lives in the other party's mail and files, Copilot sees only your side.

No Teams recap, no history. The "last time we agreed" section depends on the previous meeting having been transcribed and recapped in Teams. Meetings without transcription produce briefs without history.

It's not an agenda. The brief describes context; it doesn't propose an agenda unless you ask Copilot in the invite body to draft one — which it can, and which is a separate, useful prompt.

What Copilot reads, in plain terms

For both features, Copilot reads what the user can already read: their mailbox, their calendar, files they have access to, and — through the Microsoft Graph — recent related items. It doesn't read other people's mailboxes and it doesn't bypass any permission. Summaries and briefs are generated on request (or, for proactive briefs, shortly before the meeting) and the interactions are logged in the audit log like other Copilot activity. Nothing here needs a separate privacy review beyond the tenant's Copilot review.

Requirements

A Microsoft 365 Copilot licence and a supported Outlook client (new Outlook, web, Mac, mobile; classic Outlook on a current channel). Summaries work on the primary mailbox; shared-mailbox support has been rolling out in stages and is worth confirming for teams that live in shared inboxes. Meeting prep needs the meeting to be a proper calendar item with attendees — it does nothing useful for a blocked-out "focus time."

The one rule

Summaries and briefs are navigation, not truth. They tell you where to look and what to expect; the message and the document are still the record. Users who click the citations get the full benefit with none of the risk. Users who forward the summary as if it were the decision eventually get burned, usually on the one thread that mattered.