Copilot in Teams Meetings | Actions and Controls

Copilot in Teams can help people catch up on a meeting, identify discussion points and prepare action lists. The useful outcome is not a polished summary. It is a checked record that helps the team complete the work.

Meetings also contain sensitive conversations and uncertain statements. The organiser needs to decide how Copilot, recording and transcription should be used.

Set the meeting rules

Before the meeting, decide whether recording or transcription is appropriate, who should have access and how participants will be informed. Use the organisation's meeting policies, sensitivity labels and privacy guidance.

Microsoft provides organiser controls for whether participants can use Copilot. Available behaviour can depend on policy, meeting settings and licensing.

Use Copilot during the meeting

Copilot can summarise key discussion points, answer questions about the conversation and suggest action items. A participant might ask what decisions remain open, which risks were raised or what actions were assigned.

Do not let the generated answer replace active listening or the chair's responsibility. If the meeting contains an important decision, confirm it aloud and record the agreed wording.

Understand the role of transcription

Microsoft notes that transcription affects what Copilot can use during and after a meeting. A transcript supports post-meeting questions and recap features, but it also creates a record that needs suitable access and retention.

Names, technical terms and unclear speech may be transcribed incorrectly. Check critical statements against the recording, notes or participants.

Build a checked action list

After the meeting, ask Copilot for actions in a simple structure:

action
owner
deadline
dependency
source or decision
status

Then ask the meeting owner to confirm the list. An action without an owner is still a note. A deadline invented from context can create a false commitment.

Use recap as a starting point

Teams recaps can bring together recordings, transcripts, files, notes and follow-up information. Intelligent recap features may add AI-generated summaries and markers, depending on the licence and meeting type.

Share the recap only with people who should see the meeting material. Microsoft notes that sensitivity and access settings can restrict sharing and exporting.

Move actions into the system of work

Do not leave the final action list inside a meeting summary nobody revisits. Move checked actions into Planner, a project system, CRM or another approved record.

Power Automate may help with a consistent handoff once the team agrees the fields and ownership. Keep a person in control when a generated action could create a customer promise or financial commitment.

Close the loop at the next meeting

Bring the confirmed action list back to the next agenda. Review overdue work, changed owners and decisions that need reopening. This turns recap into an operating habit rather than another document.

Keep the approved task system as the source of status. The meeting transcript explains the conversation, but it should not compete with the final record.

Choose meetings that suit a pilot

Start with regular internal meetings that have clear agendas and actions. Avoid highly sensitive conversations until the organisation understands the controls and participant expectations.

Test meetings with accents, specialist terms, several speakers and incomplete decisions. Review what Copilot captures well and where the team must correct it.

Plan for guests and absent colleagues

External guests and absent staff may not have the same access to the meeting chat, recording, transcript or recap. Confirm access before telling people that the recap is the official follow-up.

When a guest should receive a decision or action, send a checked summary through the agreed channel. Do not assume a shared recap link grants appropriate access, and do not broaden permissions merely to make sharing easier.

For sensitive meetings, decide whether a separate, approved record should hold the confirmed decisions while the transcript and recording follow their own retention rules.

Train the organiser and participants

Organisers need to understand meeting options, transcription, access and recap. Participants need to know when AI is active, where the output is stored and how to challenge an incorrect summary.

A simple meeting rule can help: Copilot may prepare the draft record, but the chair confirms decisions and owners before the meeting is closed.

Blue Canvas provides Microsoft Copilot training for Teams, Outlook, Excel and wider rollout.