Before this clicks, catching up on a thread that's been running for three days means scrolling. Reply, quoted reply, quoted-quoted reply, someone's Outlook signature with a stock photo of a handshake, another reply. The actual decision is buried somewhere around message twenty-two, and you find it by reading backwards from the bottom because that's usually where the "okay, going with option B" lives, if anyone actually said it out loud.
Copilot's thread summary in Outlook exists to skip that. Not to replace reading the thread, to tell you whether you need to.
The mental model
Think of it less like a transcription and more like a court reporter reading back the decision, not the debate. Copilot isn't ranking every message by importance or picking a "best" reply. It's condensing the whole reply chain down to who said what and what's still open, the same move a colleague makes when they walk over and ask "so where did we land on this," and you give them the four-sentence version instead of forwarding the thread.
That framing matters because it sets the right expectation. You're not getting a neutral index of every point raised. You're getting the practical residue: decisions made, questions still hanging, who owes who a reply.
The syntax
There isn't a formula here, but there is a consistent shape to how you invoke it.
Default, one click: open the thread, hit "Summarize" (sometimes labelled "Summary by Copilot") at the top of the message list. Copilot scans the full thread and drops a summary above the messages, with numbered citations, click one and it jumps you to the actual email that claim came from. That citation link is the part worth using deliberately, because it's your fastest way to verify anything the summary tells you.
Narrower, via the chat pane: if you've pinned Copilot chat to the nav bar, you don't need a full Copilot license to ask it questions scoped to the open thread. "What's outstanding for me in this thread" gets you a different cut than the default summary, it filters for action items addressed to you specifically, not just a general recap.
Since-you-last-looked: ask what's changed since a point in time ("what's new since yesterday afternoon") and Copilot filters the thread to just the delta, useful for a thread you've already partially read and don't want to re-summarize from message one.
Three prompts, same underlying mechanism, different filter applied on top of it.
A real thread, not a toy example
Say a vendor contract renegotiation has been running across forty-some messages: legal weighing in on a liability clause, procurement pushing back on payment terms, the vendor's account rep proposing a compromise nobody from your side has actually agreed to yet, and a side-thread about a meeting time that somehow ballooned to eight replies of its own.
Run the summary. What comes back isn't "everyone discussed the contract." It's closer to: legal flagged the liability clause as blocking, procurement countered on Net 30 vs Net 45, the vendor proposed splitting the difference on payment terms but that proposal hasn't been confirmed by anyone on your side, and the meeting time is still unresolved between two options. Four lines. The forty messages compress because most of them were restating positions, not adding new ones, and Copilot's job is finding the actual state changes.
That last point is the summary's real value: it tells you what's still open, which is usually the thing you actually need before you reply, not a recap of what's already settled.
What it doesn't do
Copilot can miscount how many messages actually matter in a very long or very branchy thread, and it can misread context when the same word means different things in different sub-threads (two people both use "the deadline" and mean two different deadlines). Treat the summary as a starting point, not a citation you'd stake a decision on without checking the linked message.
It's weaker on threads that aren't primarily in English. If your team mixes languages in the same thread, expect the summary to lean toward the dominant language and lose nuance in the rest.
It doesn't read attachments. A forty-email thread with a critical number buried in an attached spreadsheet still needs you to open that spreadsheet; the summary only works from the message bodies.
And the chat-pane version without a full Copilot license is scoped to the thread you have open. It won't search across your mailbox for related context, it only knows what's in front of it. If the real answer lives in a different thread from three weeks ago, the summary won't know that thread exists.
None of that makes it useless. It makes it a first pass, the same way you'd treat a colleague's quick recap: probably right, worth a five-second check before you act on it. It's the same grounding gap that shows up everywhere Copilot works from what it can already see: the tool doesn't announce when it's missing something, it just answers from what's in front of it.
Frequently Asked Questions
Do I need a full Copilot license to summarize an email thread in Outlook?
No, not for the chat-pane version. If you've pinned Copilot chat to the Outlook navigation bar, you can ask it to summarize the currently open thread without a paid Copilot add-on. A full license extends this to searching across your whole mailbox and calendar, not just the open thread.
Does the summary update if new replies land after I generate it?
No. The summary reflects the thread at the moment you ran it. A new reply after that needs a fresh summarize, it doesn't refresh automatically the way a live dashboard would.
Can I trust the summary enough to skip reading the thread entirely?
For a quick status check, yes. Before you make a commitment based on it (a number, a deadline, a decision), click through the citation to the actual message. The summary is a shortcut to the thread, not a replacement for verifying anything you're about to act on.
Does it work on Outlook for Mac or Outlook on the web, or just Windows?
The feature is available across Outlook Classic, the new Outlook for Windows, and Outlook on the web, provided Copilot chat is pinned to the navigation bar. Coverage details shift as Microsoft rolls updates out, so if it's missing, check your Outlook version and whether Copilot chat is actually pinned before assuming it's not available to you.
Why does the summary sometimes miss a decision I know was made in the thread?
Usually because the decision was implied rather than stated plainly, buried in a reply that also covered three unrelated topics, or the thread branched (a reply-to-one-person side conversation) in a way that split the "official" answer from the visible main chain. If a decision matters, it's worth writing it as its own clear line in the thread, not just letting Copilot infer it from context.
Does it work the same way on a group chat or Teams thread, or is this Outlook-specific?
This particular summarize-a-thread feature is Outlook email specific. Copilot in Teams has its own meeting- and chat-recap features, but they're a different implementation with different strengths and limits, not the same mechanism applied to a different app.
The three lines it gives you are the ones you'd have found eventually anyway, twenty messages down, read backwards from the bottom. It just gets you there without the scroll.