How the advisory team should use Copilot in Teams — to end the era of taking minutes, catch up on anything in 90 seconds, and turn every meeting into structured, searchable, reusable material. Six distinct Teams AI surfaces, six advisory workflows, and the discipline that makes it safe for client work.
Before the features, the reframe. Meetings used to be ephemeral — they happened, someone tried to remember them, a few notes survived. With Copilot in Teams, meetings become durable, queryable, reusable content. That changes what meetings are for.
Consider the typical advisory consultant's week: perhaps 15-25 hours spent in meetings. Client workshops, internal reviews, standups, kickoffs, steering committees. Every one of those hours previously vanished unless someone took careful notes — and even then the notes captured 10% of what was said, filtered through the note-taker's attention and biases.
"The senior person in the room used to have a choice: actually listen and contribute, or take the notes. They couldn't do both. With Intelligent Recap, they don't have to choose."
The shift isn't about convenience. It's about what meetings are structurally capable of. Three specific changes:
Old pattern: the meeting ends and it's gone, except for whatever someone wrote down. New pattern: the meeting ends and it's indexed by topic, speaker, chapter, and mentioned file — searchable like a document, queryable by Copilot, reusable as source material for the deliverables that follow.
Old pattern: somebody in every meeting has the "I'm taking notes" role. Usually the junior person. They contribute less because their cognitive load is split. New pattern: nobody takes notes. Everyone listens. The most valuable person in the room is free to think rather than to transcribe.
Old pattern: the meeting is the deliverable's grandparent — something happened, notes were written, the deliverable was drafted from memory and notes. New pattern: the meeting is directly referenceable in Word and Copilot Chat via the /meeting syntax. The transcript becomes source material the same way a research brief does. Meetings feed deliverables directly.
For an advisory team, this matters more than for almost any other role. Most of what the team produces — workshop outputs, client briefings, decision documents, status reports — is literally about conversations. With Copilot in Teams, those conversations stop being the hard-to-reconstruct upstream material and become the first-class source of the downstream document.
"Copilot in Teams" covers six quite different features, each in its own part of the product. Intelligent Recap is the headline, but four of the other five are underused — and two of them (Facilitator and Channel Agent) change Teams from a communication tool into a collaborative AI workspace.
Teams Copilot's prerequisites are structural, not cosmetic. Transcription has to be on. Admin policy has to permit it. External attendees need to consent. These aren't speedbumps — they're non-negotiable conditions without which nothing else in this chapter works.
1. Admin policy check. Your Teams admin must have enabled Allow transcription in the Teams admin centre under Meetings → Meeting policies → Recording & transcription. If transcription is disabled tenant-wide, every other feature in this chapter is disabled too. Check before investing in workflow training.
2. Licence confirmation. Microsoft 365 Copilot add-on licence for the full feature set (Facilitator, Channel Agent, Custom Summary, live Copilot during meetings, Audio Recap). Teams Premium alone gives basic Intelligent Recap only. Personal and Family subscriptions don't give commercial Copilot. Check via the Microsoft 365 admin centre or File → Account → Update Licence.
3. The transcription habit. For every internal meeting, the organiser turns on transcription before or at start — three clicks: More actions → Record and transcribe → Start transcription. Once the team builds the habit, it takes five seconds. Without the habit, nothing else works. Some organisations set auto-transcription at the tenant level for recurring meetings — worth asking your admin about.
4. External meeting consent protocol. For any meeting with client, vendor, or partner attendees, transcription requires explicit consent. Two approaches:
No shortcuts here. Client trust is infinitely more valuable than the Copilot features transcription enables. If an important client prefers no transcription — respect it and take notes the old way for those specific meetings.
The single highest-ROI habit change from Copilot in Teams. Turn on transcription for every internal meeting. Nobody takes notes. The most senior person in the room listens. Recap handles the rest.
The default AI summary is good. Custom templates built specifically for Arup advisory meeting types turn it from good to structurally reliable. Set these up once; they're saved to your profile and available for every future meeting.
The everyday moment Copilot in Teams was built for. You join 15 minutes after the start. Previously you'd guess from context, interrupt someone, or stay quiet for ten minutes while orienting. Now you catch up in 30 seconds without derailing the room.
Copilot's in-meeting responses can be exported. If the response is over 1300 characters, a button appears: Open in Word. Click it and the response opens in a Word doc — useful if the "catch me up" summary becomes a substantial document you want to keep. If the response is formatted as a table, an Open in Excel button appears. This matters because for longer meetings where you've asked several progressive questions, by the end you have a structured document summarising the whole meeting — built by Copilot while you were just trying to catch up.
Two things that stop the export:
Both are legitimate controls — respect them. But in most internal meetings neither applies, and the export-to-Word move turns Copilot's catch-up from a one-off utility into reusable structured content.
The cross-app workflow that's probably the single most valuable in the whole playbook. Workshop ends at 3pm. Client has the outputs document by 4pm. Previously this was a day's work. Teams transcription plus Word's /meeting reference turns it into an hour.
Not a summary tool. Not a transcription tool. A meeting teammate. Facilitator generates live notes in Loop that the whole room can co-edit, tracks the agenda with timers, and answers participants' contextual questions in chat. For meetings that need visible shared capture, it's transformative.
Facilitator only works on scheduled Teams meetings. Not channel meetings, instant meetings, or Teams calls. Add it during scheduling via Add Facilitator in the meeting form, or during the meeting via the toggle in Copilot and other AI options. Requires M365 Copilot licence on the person who adds it; other meeting participants (except external ones) can see all real-time updates without needing their own licence.
Recap is post-meeting — you get the summary after everyone's left. Facilitator is during-meeting — the shared notes form as the meeting happens, and everyone can correct, expand, or refine them in real time. For meetings where the notes are the output rather than an after-the-fact record, Facilitator is structurally different from Recap. Workshops, brainstorms, collaborative design sessions, planning meetings — these are Facilitator territory. Status reviews, information-giving meetings, external client calls — these are Recap territory.
In Teams public preview, Facilitator can additionally: create a Loop or Word document from the meeting conversation on request; manage tasks via @mention — "@Facilitator create a task for Sarah to draft the proposal by Friday" — with tasks auto-syncing to a meeting plan.
The non-meeting Teams use case. Teams chats and channels accumulate conversation density the same way email inboxes do. Copilot turns a 200-message channel thread or a weeklong 1:1 chat into a searchable, summarisable artefact.
Limitations to know before relying on chat Copilot for critical work:
For text-heavy conversations, Copilot in chat is excellent. For mixed-media chats where half the substance is in images, Loop, or files, treat the summary as a starting point and check the visual content manually.
In compose mode in any Teams chat, you can select your drafted message and use Rewrite with Copilot to adjust for tone, length, or clarity — the same way you would in Outlook or Word. Useful for chats that matter: client-facing channels, sensitive internal conversations, messages you'd want to read twice before sending.
The feature that turns Teams from a communication app into a collaborative AI workspace. One Channel Agent per project channel, grounded on that channel's messages, files, and meetings. Ask it questions, request status reports, flag deadlines. The dedicated project brain — finally.
Create Channel Agent from within the project channel — it will automatically adopt the channel's name and icon. Only one Channel Agent per channel; you can't add the same agent to multiple channels. Expand its knowledge by adding it as a participant to the channel's recurring meetings — it will absorb those transcripts into its memory and be able to answer questions about them later.
Six use cases, six tools, one table.
| Your scenario | Use this | Surface | Time |
|---|---|---|---|
| Run an internal meeting without a note-taker | Transcription + Intelligent Recap | Teams meeting | 0 min during |
| Review a client workshop afterwards | Custom Summary template | Recap panel | ~5 min |
| Join a meeting 15 min late without disruption | Copilot during meeting · catch-me-up | Meeting controls | ~30 sec |
| Ask a question about what was said mid-meeting | Copilot during meeting · live Q&A | Meeting pane | ~10 sec |
| Workshop → client-facing outputs document | Recap + Word /meeting reference | Teams + Word | ~45 min |
| Internal workshop with shared live notes | Add Facilitator agent | Meeting setup | ~2 min |
| Keep an agenda-driven meeting on track | Facilitator + agenda timer | Meeting | ~0 min active |
| Catch up on a chat you've been away from | Copilot in chat | Chat pane | ~1-2 min |
| Synthesise a 47-reply channel thread | Copilot in channel · expanded view | Channel thread | ~2 min |
| Recurring project — weekly status automation | Channel Agent | Project channel | ~5 min setup |
| New joiner onboarding to a project | Channel Agent Q&A | Project channel | ~15 min for them |
| Regulated-sector client — no transcript allowed | Recap without transcript | Meeting options | ~0 min |
| Commute catch-up on missed meetings | Audio recap | Recap | ~10 min passive |
Patterns from training advisory teams on Copilot in Teams. Almost every bad outcome maps to one of these.
/meeting reference in Word is the whole workflow.