You're @mentioned in a channel with two hundred unread messages, and someone needs "the three decisions" in ten minutes. Copilot can summarize the thread and pull out actions and owners. It can also assign an item that nobody accepted. This lesson starts with the conversation itself, then moves to the license map so you can separate a weak summary from a feature you aren't entitled to use.
Pick the right surface first
Copilot works on the conversation you point it at, so the first move is choosing the right one:
Before you prompt, finish this sentence: "I need Copilot to work with the messages in ____." Then confirm the conversation you have open matches the blank: read its name and the first and latest relevant messages. Analyzing the wrong thread is the quietest way to get a confident, useless answer, and it's entirely avoidable with a five-second check.
Explicit means explicit
A trustworthy conversation summary keeps four categories apart: a fact someone reported, a decision the messages show was made, an action item someone explicitly committed to or was assigned, and an unknown where a required owner, date, or answer is absent. The word that does the work is explicit.
Marco writes, "the accessibility review found two issues." Ana writes, "I will fix the first issue by Friday." The thread supports one action: Ana's fix of the first issue by Friday. You can report the second issue as unresolved, but nobody has accepted it. A summary that says "both issues are owned" has created a commitment the conversation doesn't contain. Keep ability statements such as "I could look at that," suggestions, and concerns outside the assigned-action list. Before forwarding Copilot's summary, compare it with the messages that support each decision and action.
Rewrite without changing the ask
Teams can rewrite a message you're composing to fix the tone: turn a terse, frustrated line into something professional and collaborative. That's useful, and it's also where facts leak. Rewriting is allowed to change wording. The underlying request has to survive intact.
Compare the proposed rewrite with the original request, deadline, recipient, counts, and level of urgency. It must not add a promise, reason, or accusation. Take "need the revised budget by 3 PM. This has already slipped twice." The new version still needs 3 PM and "twice." If it says "soon," drops the count, or explains why the delay happened without a source, the friendlier tone has changed the message.
Agents answer within a boundary
A Copilot agent in a group chat is an AI participant scoped to a defined kind of question, say a purchasing-policy agent. The difference from a plain summary matters: a summary organizes a conversation, while an agent answers within an information boundary. A well-behaved agent distinguishes fields its available information answers from fields it doesn't, and it never fills the gap with something that merely sounds right.
Make the boundary explicit in your prompt and demand a specific phrase for gaps, such as "Not answered by the available policy." If you ask a policy agent for the required approver, the required documentation, and the escalation path, and the policy it holds covers only the first two, the correct answer flags the third as unanswered rather than inventing a plausible escalation chain. Never treat an agent as the final authority on a policy, an approval, or a commitment. Check the important fields against the governing source.
Which license turns this on?
Everything you've done in this module (live meeting questions, the recap features from Meetings: Recaps, Actions, and Follow-Ups, Channel Agents) sits on a licensing map with three tiers: baseline Teams AI (standard features, no Copilot license), Teams Premium (a paid add-on), and Microsoft 365 Copilot (a paid add-on). Both paid tiers cost money on top of your base plan. This course doesn't quote prices, because they change, and the durable knowledge is which tier turns on which feature.
Read that table as two separate questions. The AI-entitlement column answers "which tier gates this?" The extra-condition column answers "what else must be true?" They are not the same thing. A PSTN call recap needs a Teams Premium or Microsoft 365 Copilot entitlement and Teams Phone: one is the license gate, the other is a service requirement, and collapsing them produces wrong purchasing decisions. A PSTN call (to a regular phone number) carries the Teams Phone condition, while a one-to-one or group VoIP call between Teams participants does not, so classify the call before you decide.
A control you can't find proves only that the feature was not observed in that test. The client, a policy setting, the rollout state, or the communication type may explain it. Record the observation first. Then check entitlement, conditions, and configuration as separate questions. "I don't see the button" and "we didn't buy the license" require different evidence.
