Microsoft Teams meetings best practices

Most Teams problems aren't with the product itself but with how meetings are set up. A handful of habits — and a few admin settings — go a long way.

The admin side of these practices is in meeting policies design, breakout rooms, recording management, and Teams Rooms; the AI layer is Copilot in Teams meetings.

Schedule from the right surface

Use the Teams calendar, Outlook, or Bookings to create meetings rather than ad-hoc "Meet now" calls. Scheduled meetings get a proper join link, a chat that persists, a calendar entry, and the option of channel meetings (which post the meeting to a channel where the team can pick it up).

Lock down lobby and presenters

By default, anonymous and guest users wait in the lobby. Keep this on for external meetings. For internal recurring meetings, make trusted attendees Presenters and everyone else Attendees, which restricts who can share screens, manage breakouts, or mute others.

Recording, transcription, and Copilot

Recording and transcription are admin-toggled. Once on, recordings are stored in the organiser's OneDrive (for non-channel meetings) or in the channel's SharePoint site (for channel meetings), with permissions inherited from those locations. Transcription is required for meeting recap and Microsoft 365 Copilot in Teams post-meeting summaries to work well. Make sure attendees know meetings are being recorded.

Layout and accessibility

• Turn on Together mode or Gallery for large meetings; Speaker view for small ones.
• Enable live captions for accessibility and noisy environments. Live translation is available in some plans.
• Use PowerPoint Live instead of screen-sharing slides — it preserves searchable text, lets attendees navigate independently, and reads cleanly to screen readers.

Breakouts and town halls

For workshops and training, breakout rooms scale well up to about 50 rooms per meeting. For very large audiences (1,000+), use Town Halls, which provide a structured presenter/attendee model and built-in event production tools.

Admin defaults that matter

In the Teams admin center, set sensible defaults under Meetings → Meeting policies: anonymous join, recording retention, who can present, and chat history controls. Pair those with a clear Conditional Access policy that enforces MFA and compliant devices for joining sensitive meetings.

Good defaults beat good habits — once these are set, meetings tend to run themselves.

Meeting hygiene that isn't a setting

Some of the highest-impact practices aren't admin toggles at all. Agendas in the invite — even three bullet points — measurably shorten meetings and give latecomers something to orient against without asking "what did I miss." Naming meetings specifically ("Q3 budget review — decision needed" rather than "Sync") helps attendees triage a packed calendar and helps anyone searching Copilot-generated recaps later find the right one. Ending meetings with a clear owner per action item, not just a list of tasks, is what actually makes a Copilot-generated action-item summary useful afterward — a summary of "things discussed" with no owners just becomes another document nobody acts on.

Frequently asked questions

Should cameras be required in meetings? There's no admin setting for this — it's a team-culture decision, not a policy one — but a light-touch default (cameras encouraged for internal working sessions, optional for large all-hands or when someone is on a poor connection) tends to work better than a hard mandate, which mainly generates friction for the exact situations where it's least warranted.

Why do some recordings show up in a channel's SharePoint site while others land in a personal OneDrive? Recording storage location follows the meeting type: a channel meeting (scheduled from within a Teams channel) stores its recording in that channel's SharePoint site, visible to the whole channel by default; an ordinary calendar meeting recording lands in the organiser's own OneDrive, visible only to people the organiser explicitly shares it with. Choosing to schedule as a channel meeting when the recording should be broadly discoverable — and as a personal meeting when it shouldn't — is a simple lever many organisers don't realise they're pulling.

Is it worth enabling live translation alongside captions? For genuinely multilingual audiences, yes — but it's worth testing with real speakers on real accents and technical vocabulary before rolling it out broadly, since automated translation quality varies noticeably by language pair and drops further with jargon-heavy content; a pilot with the specific meeting types and languages that will actually use it avoids discovering the gaps live in front of an audience.