Back to All Cheatsheet Libraries cheatsheets

Microsoft Teams

Keyboard shortcuts, channels/chat, and meeting reference for Microsoft Teams.

Showing results
Group Action Windows Mac Notes
EssentialMute / unmuteCtrl + ⇧ + M⌘ + ⇧ + MThe one to memorise. Works when Teams has focus.
EssentialPush to talkHold Ctrl + SpaceHold ⌥ + SpaceTemporarily unmute while held, then back to muted. Ideal in a noisy room.
EssentialToggle cameraCtrl + ⇧ + O⌘ + ⇧ + OO for "on", not zero.
EssentialRaise / lower handCtrl + ⇧ + K⌘ + ⇧ + KQueues you in the order raised, which hosts can see.
EssentialShare screenCtrl + ⇧ + E⌘ + ⇧ + EOpens the share picker — choose a window, not the whole screen, where possible.
CallsAccept video callCtrl + ⇧ + A⌘ + ⇧ + AAnswers with camera on.
CallsAccept audio callCtrl + ⇧ + S⌘ + ⇧ + SAnswers audio-only regardless of how it was placed.
CallsDecline callCtrl + ⇧ + D⌘ + ⇧ + DSends to voicemail if configured.
CallsStart a call from a chatCtrl + ⇧ + C⌘ + ⇧ + CAudio call to whoever the chat is with.
CallsLeave the callCtrl + ⇧ + H⌘ + ⇧ + HLeaves without ending it for everyone else.
NavigateSearch / command barCtrl + E⌘ + EThen type / for commands or @ to jump to a person.
NavigateGo to Activity / Chat / Teams / CalendarCtrl + 1 / 2 / 3 / 4⌘ + 1 / 2 / 3 / 4Numbers follow the left rail order, which is customisable.
NavigateOpen filterCtrl + ⇧ + F⌘ + ⇧ + FFilters the current list — chats, teams, or activity.
NavigateOpen settingsCtrl + ,⌘ + ,Devices, notifications, and appearance live here.
NavigateShow all shortcutsCtrl + .⌘ + .Teams' own always-current list.
ComposeNew chatCtrl + N⌘ + NOpens with the To field focused.
ComposeExpand the compose boxCtrl + ⇧ + X⌘ + ⇧ + XGives you formatting options and stops Enter sending prematurely.
ComposeNew line without sending⇧ + Enter⇧ + EnterEssential. Plain Enter sends — the cause of countless half-finished messages.
ComposeMark as importantCtrl + ⇧ + I⌘ + ⇧ + IUse sparingly or it stops meaning anything.
ComposeAttach a fileCtrl + O⌘ + OFiles land in the channel's SharePoint library — see the Structure tab.
Slash commands worth knowing
  • Press Ctrl/⌘ + E then type / to see them all.
  • /goto — jump straight to a team or channel.
  • /chat — message someone without leaving what you're doing.
  • /available, /busy, /dnd, /away — set presence instantly.
  • /unread — everything you haven't read, in one view.
  • /mentions — only messages that @mentioned you. The highest-signal filter in Teams.
  • /files — recent files across every team.
  • /whatsnew — release notes, so a UI change doesn't surprise you.

A Team is a Microsoft 365 Group wearing a different hat

This is the thing that explains most Teams confusion. Creating a Team silently creates a Microsoft 365 Group, a SharePoint site, a shared mailbox, a OneNote notebook, and a Planner. Files you drag into a channel are stored in that SharePoint site, not in Teams. Understanding this makes permissions, storage, and retention behaviour obvious rather than mysterious.

Channel type Who can see it Where files live Use it for
StandardEvery member of the team.A folder in the team's SharePoint site.The default. Most channels should be this.
PrivateOnly invited members, who must already be in the team.Its own separate SharePoint site.Sensitive work inside a wider team — budget, hiring. Note the separate site complicates retention and eDiscovery.
SharedPeople outside the team, including other tenants, without joining the team.Its own SharePoint site.Cross-team or cross-org collaboration without granting access to everything else.
Channels vs chat — pick deliberately
  • Channels are persistent, searchable, and joinable. A new team member sees the history. Use them for anything that outlives the conversation.
  • Chat is ephemeral in practice — invisible to anyone not in it, and lost to newcomers. Use it for coordination, not decisions.
  • The rule of thumb: if someone joining next month would benefit from reading it, it belongs in a channel.
  • Decisions made in a group chat are effectively undocumented. This is the single most common way organisational knowledge evaporates in Teams.
Mentions and notification hygiene
  • @person notifies one person. @channel notifies everyone following it. @team notifies every member.
  • @team on a large team is almost always wrong. It trains people to mute the team entirely, which then breaks genuine urgent messages.
  • Channel notification settings are per-channel and per-person: right-click a channel → Channel notifications.
  • /mentions is the highest-signal view in the product. If Teams feels overwhelming, live there instead of the Activity feed.
  • Use Do Not Disturb with a priority-access list rather than muting everything — Settings → Privacy → Manage priority access.
Meeting options — set these before, not during
  • Who can bypass the lobby — the most important setting. For external or sensitive meetings, set it to "People I invite" so nobody wanders in.
  • Who can present — set to "Only me" or specific people for anything public-facing. Prevents screen-share hijacking.
  • Announce when callers join — worth leaving on so a dial-in participant can't listen silently.
  • Allow mic/camera for attendees — for webinars and all-hands, restricting these keeps the meeting controlled.
  • Access these from the calendar item before the meeting, or the three-dot menu during it.
Breakout rooms
  • Only the organiser can create them, and only from the desktop app — not the web client.
  • Automatic assignment splits evenly; manual lets you place people deliberately.
  • Set a timer so rooms close automatically rather than chasing groups back.
  • You can broadcast an announcement to every room at once — the reliable way to give a two-minute warning.
  • Pre-assign participants when scheduling to save several minutes of live faffing.
Recording, transcription, and where things land
  • Recordings save to OneDrive (for non-channel meetings) or the channel's SharePoint site — not to a central Teams library.
  • That means a recording's lifetime follows the organiser's OneDrive. If they leave, it goes with their account unless transferred.
  • Transcription is separate from recording and can be enabled independently — useful when you want the text but not the video.
  • Everyone is notified when recording starts. There is no silent recording.
  • Recordings have an auto-expiry setting (often 60 days by default) — check tenant policy before relying on one being there later.
Quality-of-life settings
  • Background blur or replace — three-dot menu → Video effects. Heavier effects cost noticeable CPU on older machines.
  • Noise suppression (Settings → Devices) filters keyboard and fan noise. Set it to Low if you're deliberately sharing audio or music.
  • Share a window, not the screen — avoids broadcasting notifications, and is sharper.
  • Tick "Include computer sound" when sharing video, or the room watches in silence.
  • Live captions are free and available to everyone regardless of tenant tier.
Control Team creation early
  • By default any user can create a Team — and therefore a Microsoft 365 Group and a SharePoint site. Sprawl is the predictable result.
  • Restrict creation to a security group via Entra ID Group settings, or accept the sprawl deliberately with a naming policy and expiry.
  • Set a Group naming policy (prefix/suffix by department or region) so the directory stays navigable.
  • Set a Group expiration policy — owners are asked to renew, and unrenewed Teams are archived. This is the only mechanism that prevents indefinite accumulation.
  • Every Team should have at least two owners. A Team whose only owner has left cannot be managed.
External access vs guest access
  • External access (federation) lets you chat and call people in other Teams tenants. They don't join your Teams and see nothing else.
  • Guest access adds someone to a Team as a member — they see channels, files, and history for that Team.
  • These are configured separately and confusing them is common. Guest access is the more permissive of the two by a wide margin.
  • Audit guests periodically. People leave projects; their guest accounts rarely do.
  • Set guest access expiry where the tenant supports it, and use Entra ID access reviews for anything long-running.
Compliance sits underneath, not in Teams
  • Teams chat and channel messages are stored in Exchange; files in SharePoint/OneDrive. Retention and eDiscovery are configured in Microsoft Purview, not in the Teams admin centre.
  • A retention policy that deletes chat after N days will do exactly that — model it before enabling.
  • Private and shared channels have their own SharePoint sites, which are easy to miss when scoping a retention policy or an eDiscovery search.
  • Meeting recordings follow the OneDrive/SharePoint retention of wherever they landed.

Gotchas

Files are SharePoint, with SharePoint's rules
  • Dragging a file into a channel uploads it to that channel's SharePoint folder. Everyone in the channel gets access — including access you may not have intended.
  • Deleting a file from Teams deletes it from SharePoint. It goes to the SharePoint recycle bin, not the Teams interface.
  • Renaming a channel does not rename its SharePoint folder, which drifts apart over time and confuses anyone browsing the site directly.
  • Sharing a file in a chat stores it in the sender's OneDrive, not SharePoint — so it disappears when they leave.
Moving a channel isn't really possible
  • There's no supported way to move a channel between Teams while keeping its history and files intact.
  • Getting the Team structure roughly right at the start matters more than in most tools.
  • Prefer fewer Teams with more channels over many small Teams — channels are cheap and reorganisable, Teams are not.
  • A Team per department or long-lived project; a channel per workstream.
Notification defaults are wrong for most people
  • Out of the box, Teams notifies aggressively and people respond by muting everything — which then breaks genuinely urgent messages.
  • Set channels you merely monitor to "Off", ones you own to "All activity", and rely on /mentions for the rest.
  • Use Do Not Disturb with priority access rather than blanket muting, so your manager still reaches you.
  • Presence is inferred from calendar and activity and is frequently wrong. Set it manually when it matters.
When Teams misbehaves
  • The classic fix is genuinely clearing the cache — quit fully, then delete the Teams cache directory and relaunch.
  • Windows: %appdata%\Microsoft\Teams (classic) or the packaged app's cache for new Teams. Mac: ~/Library/Application Support/Microsoft/Teams.
  • Missing channel or stale membership usually resolves after sign-out/sign-in — Group membership changes can take time to propagate.
  • Audio device problems: Settings → Devices → make a test call. It verifies mic, speaker, and camera in one pass.

Tips

Live in /mentions

The single highest-signal view. Most Teams overwhelm is solved by reading mentions and treating the general feed as optional.

Save messages for later

Hover a message → three dots → Save. Retrieve them all with /saved. A lightweight read-later queue built into the product.

Pin the channels that matter

Right-click → Pin. Pinned channels sit at the top of the rail regardless of which Team they belong to.

Add tabs to channels

Pin a Planner board, a specific Excel file, a Power BI report, or a website as a tab. Far better than linking to it in a message nobody can find later.

Pop out a chat or meeting

Double-click a chat to open it in its own window — so you can take notes in the main window during a call.

Use Together mode for large calls

Places everyone in a shared virtual space. Sounds gimmicky, genuinely reduces fatigue on long calls with many participants.

Resources