The Copilot feature
people actually keep using
is the boring one.
In almost every organization I train, the same thing happens. People try the impressive features, enjoy them, and stop. The one they still use 3 months later is meeting recap, because it requires no change in behaviour at all. The meeting happens, Copilot is on, the summary is there afterwards.
That makes it the best starting point for a rollout, and the place where a few specific mistakes quietly cost you the trust of the whole organization.
What it actually produces
When transcription is enabled, Copilot generates a recap containing a summary, the key discussion points, decisions taken, action items, and transcript highlights. It lands in the meeting's Recap tab.
From there it does the useful part: drafting the follow-up email, pushing tasks into Planner or To Do, and answering the question people actually have, which is "what did I miss and was anything assigned to me". For someone who could not attend, that last one is the whole value.
Microsoft has kept building here through 2026, adding a dedicated Meeting Recap app, video recap that turns a recording into narrated highlights, and AI recap that works without a full transcript.
Why this matters more for distributed teams
If your team spans several countries, a meaningful share of people are always in the wrong time zone for the meeting that concerns them. The usual workaround is that someone writes notes, or nobody does and the information simply does not travel.
Recap changes the economics of that. A colleague who was asleep can catch up in 2 minutes and see exactly whether something was assigned to them. In my experience this is the single most persuasive demo for a European organization with people in more than one office, because it solves a problem they already feel every week.
The 4 mistakes I keep seeing
01 Turning it on without telling anyone
People discover mid-sentence that the meeting is being transcribed and summarised. That is not a technical problem, it is a trust problem, and it takes far longer to repair than it would have taken to announce. Tell people before, not during.
02 Never agreeing which meetings get recorded
Some conversations should not be transcribed. Performance discussions, sensitive HR matters, early commercial negotiations. Decide the categories in advance and write them down, otherwise the decision gets made in the moment by whoever clicks first.
03 Treating the summary as a record
It is a good summary and it is not minutes. It can miss nuance, and it can flatten a disagreement into a decision. For anything consequential, someone still reads it before it circulates. I say this as someone who likes the feature.
04 Forgetting that recaps are retained content
Recaps and transcripts are stored, discoverable, and subject to your retention policy like anything else. That is manageable, and it should be a deliberate decision rather than something a compliance review finds later. See Copilot, GDPR and EU data residency.
Getting more out of it than the default
Most people read the auto-summary and stop. The recap is also queryable, and that is where the time actually goes back into your week.
Things worth asking it after a meeting: what was decided and what was only discussed, what is assigned to me, what did the client push back on, what did we say we would send. Those questions produce sharper output than the generic summary, because you are telling it what you care about.
This is the same skill that matters everywhere else in Copilot. Knowing it exists is not the gap. Knowing what to ask is.
Why I usually start rollouts here
Two reasons, and they are both about adoption rather than the feature.
First, it produces something visible. Colleagues see a useful recap arrive in a channel, which is the peer proof that actually spreads adoption. Second, it does not ask anyone to work differently, so it survives the month 2 drop-off that kills most of the other features. If you want the longer version of that argument, it is on the why rollouts stall page.
Questions people ask
Do we need to record the meeting?
Transcription is the requirement rather than recording, and Microsoft has been adding recap options that work without a full transcript. Check what your tenant currently has enabled, because this area has changed repeatedly through 2026.
Can people opt out?
The practical answer is that your policy decides this, not the product. Organizations that state clearly which meeting types are transcribed have far fewer problems than organizations that leave it to the individual.
Is the summary accurate?
Good on what was said, weaker on tone and on distinguishing a firm decision from thinking out loud. Treat it as a strong first draft that a human confirms before it becomes the official version.
Does it work for meetings in Hebrew or other languages?
Multilingual support has improved considerably, and quality still varies by language and audio conditions. Worth testing on your own real meetings rather than trusting a demo, which is what I do with clients before promising anything.
Can you train our team on this specifically?
Yes. It is usually a module inside a broader session rather than a workshop of its own, because it is quick to teach and the value comes from combining it with the rest. Delivered live in English over Zoom for teams across Europe.
Want your team using this properly within a week?
An intro call takes 30 to 45 minutes. We look at how your meetings actually run, what to switch on, what to agree first, and whether a short session gets you there.