Recurring meetings + decisions

How to turn Microsoft Teams meetings into useful notes

A recurring Teams meeting needs a record of decisions, owners, and what changed. Prepare your audio, capture the discussion, and review a structured summary before posting it to the team.

macOS 13+ and Windows 11 · 7-day trial · One-time purchase after the trial

Recording, transcription, and notes for Microsoft Teams

Before you start

Complete MeetingDebrief setup and download a transcription model and a summary model. Run a short test with both your voice and another participant’s audio.

Tell everyone you are recording and get the required permission. Follow your organization’s recording rules. MeetingDebrief captures audio separately from the meeting app; do not rely on that app’s recording indicator.

Decide where your meeting record belongs

Teams can already record and transcribe meetings. Microsoft’s recording documentation explains that recordings are stored in OneDrive or SharePoint. Access for external attendees may require explicit sharing.

If your team needs its official recording in Microsoft 365, use that workflow. MeetingDebrief creates a separate audio recording and notes on your own computer. It does not replace the organization’s record, attach a transcript to Teams, or change your tenant’s recording policies.

For a native transcript, Microsoft documents More actions → Record and transcribe → Start transcription. Availability and access depend on meeting roles and settings. See Teams transcription help for the current controls.

Before: prepare for a recurring Teams meeting

Make the audio paths match

Join Teams with computer audio. In MeetingDebrief’s Audio settings, select your microphone and turn on Include system audio. On Windows, choose the System audio device that Teams uses for its speaker output. A headset can have more than one similarly named device.

Use Test Microphone and make a short recording with someone speaking from the other end. On macOS, MeetingDebrief needs its own microphone and system audio permissions, even when Teams already has access.

Choose what you want to remember

For a project meeting, plan to produce decisions, next steps, and unresolved questions. For a one-to-one, focus on agreed follow-ups. Use a descriptive session name and a consistent tag such as weekly-planning once the session is available.

In General settings, enable Auto-transcribe after recording if you want processing to start when you stop. You can also enable automatic summarization and select a default template.

On Windows, select the speaker or headset output that carries your Teams call. Screenshot from MeetingDebrief 5.1.0 on Windows; sample meeting data.

During: record the discussion and preserve context

  1. Confirm recording with the participants, then click Start Recording in MeetingDebrief.
  2. Keep the floating recorder accessible. Pause it when the group agrees to go off record, and resume only when appropriate.
  3. Say important decisions and owners aloud. “Move this one over there” may make sense on a shared board, but leaves an ambiguous audio record.
  4. Stop MeetingDebrief at the end of the discussion. Let the final transcript finish before treating live captions as the final record.

MeetingDebrief’s microphone capture is independent of Teams. Muting yourself in Teams does not necessarily stop the recorder from hearing you. Use the recorder’s pause control when you want to pause capture.

After: generate the decisions and the work to do

Open the session, review the transcript, and correct names or project terms with the line’s pencil control. In Summary, select Project Discussion and click Generate. Add an Action Items summary if you want a separate checklist.

For recurring meetings, a custom summary template can keep the format consistent. Create one in Settings with instructions like these:

Summarize the project discussion under Decisions, Actions, and Open questions. Include an owner and due date only when stated. Distinguish proposed work from agreed work. Mark missing owners or dates as not specified. {transcript}

This is a suggested prompt, not a guarantee that the model will interpret every commitment correctly. Summary templates control the format; the transcript remains the evidence.

Edit the generated summary before it becomes the team’s shared record. Screenshot from MeetingDebrief 5.1.0 on macOS; sample meeting data.

Review the recap before posting it to Teams

  • Check each named owner. Remote voices are grouped as Other, so identity must come from the conversation and your review.
  • Separate a final decision from a suggestion that still needs approval.
  • Add links to the relevant board or document manually. MeetingDebrief does not read Teams chat or shared slides.
  • Use Copy on the summary and paste only the relevant notes into the intended chat or channel.

For next week’s meeting, use folders, tags, and global search to find the previous decision. A consistent project tag lets you keep the history together even if some calls happened in Zoom or Webex.

Microsoft Teams questions

Do I need Copilot for this Teams notes workflow?
No. MeetingDebrief uses its own local transcription and summarization models. Its trial and license are separate from Microsoft’s subscriptions, and your organization still needs to permit local recording.
Does MeetingDebrief attach notes to the Teams recap?
No. Notes stay in MeetingDebrief until you choose to copy or share them. Paste a reviewed summary into the appropriate Teams chat, channel, or document yourself.
Will it name everyone speaking in my Teams meeting?
It separates your microphone from the other side of the call as Me and Other when speaker detection is enabled. It does not identify every remote participant. Confirm names and action owners from what was actually said.

Tap image to zoom