Restrict access to Teams recordings

The short answer

You restrict access to a Teams recording mainly by controlling the file's sharing permissions where it is stored, not inside the Teams meeting window. In current Microsoft 365 setups, recordings of regular (non-channel) meetings are generally saved to the OneDrive of the person who started the recording, and channel meeting recordings are saved to the SharePoint site behind that team. Whoever can manage that file, typically the recorder and meeting organizer, can narrow or remove access through the file's sharing settings. Organization-wide limits, such as who may record at all or whether recordings expire, are set by IT administrators through Teams and Microsoft 365 policies.

The main condition is that your options depend on your organization's licensing, admin policies and Teams version. Microsoft changes these controls periodically, so treat the steps below as a general pattern and confirm the exact menus in your own tenant or with your administrator.

Why storage location decides who can see a recording

Because a Teams recording is an ordinary file in OneDrive or SharePoint, it inherits the permission model of that storage. This has a practical consequence: a channel meeting recording is usually visible to members of the channel, because channel files are shared with them by default. If a conversation should not reach the whole team, holding it as a channel meeting makes restriction harder than holding it as a private scheduled meeting.

Meeting type | Typical storage location | Who usually controls access

Scheduled or ad hoc meeting (not in a channel) | Recorder's OneDrive, in a Recordings folder | Recorder and organizer, via file sharing settings

Channel meeting | The team's SharePoint site, in the channel's files | Team owners and site permissions; channel members generally have access

Steps a meeting owner can usually take

• Open the recording file from the meeting chat or directly from OneDrive or SharePoint, then open its sharing or Manage access panel.
• Review who currently has access, and remove people or sharing links that should not be there.
• Where offered, change access from edit to view, and turn on options that block downloading so viewers can watch but not save a copy.
• Avoid broad links such as 'anyone with the link' or 'people in your organization' for sensitive recordings; share with specific people instead.
• Check the meeting options before the meeting, if your version offers settings for who can record or who can access recordings, so the restriction is in place from the start.
• If the recording should not exist at all, delete it from storage, keeping in mind that deleted files may stay in a recycle bin or be retained under your organization's retention policies.

What administrators control

Administrators can generally decide whether users are allowed to record meetings, whether transcription is on, and whether recordings expire automatically after a set period. Some additional protections, such as sensitivity labels or extra restrictions on recording and downloads, may depend on specific Microsoft 365 or Teams add-on licenses. No evidence was supplied here on which features belong to which license, so check current Microsoft licensing documentation or ask your IT team before relying on a particular control.

Why this matters for webcam and microphone audio

A Teams recording captures whatever the active audio input picks up, including the built-in microphone on a webcam. Webcam microphones are often omnidirectional, meaning they pick up sound from most directions, so a recording can include side conversations, background voices or room noise that participants did not intend to share. Restricting file access limits who hears that material later, but it does not change what was captured.

Before recording, it helps to confirm in Teams device settings which microphone is selected, mute when not speaking, and use a more directional microphone or headset if you need to reduce pickup of other people in the room. Restricting access is the after-the-fact control; choosing and managing the input device is the before-the-fact one.

Gaps in the available evidence

No confirmed specifications, menu paths, license tiers, default expiration periods or dates were provided for this guide. The guidance above reflects Microsoft's general storage and permission model for Teams recordings, not tested behavior in a particular tenant. Exact option names, defaults and availability can differ by organization and change over time, so verify them in your own Teams and Microsoft 365 environment.