Recording a Teams meeting: how to set it up and who to tell

Most searches for how to record a Teams meeting are not really about the button. The button is in the same place it has been for years. The searches happen because the button was missing when someone needed it, or because it worked and then nobody could find the file, or because a client asked afterwards whether they had agreed to be recorded. Those are three different problems, and only one of them is solved by clicking Record.

What follows is the setup side: which policy has to be on, whose permission counts, what participants are told and by whom, where the file lands, who can open it, and how long it survives. The behaviour described here is what Microsoft documents for Teams as of late September 2026.

What recording actually captures, and what it leaves behind

A Teams recording captures audio, video and screen sharing activity. It works in meetings, in 1:1 calls, in webinars and in town halls, and Microsoft calls this user initiated kind convenience recording to distinguish it from compliance recording, which is automatic, owned by the organisation and delivered through a third party solution.

Once a recording finishes, it does not sit in one place. It is uploaded to storage, linked in the chat for that meeting, shown in the Recordings and Transcripts tab for the meeting in the Teams calendar, added to the various file lists across Microsoft 365 such as Shared with me and Recent, and indexed by Microsoft 365 search. Purview retention and the usual OneDrive permissions apply to it like any other file.

That spread is why recordings feel both easy to find and easy to lose. Anyone who was in the chat has a link for as long as the chat is in front of them. Three months later, when the chat has scrolled away and the person who scheduled the meeting has changed roles, the same recording is effectively gone even though the file still exists.

Transcription is a separate switch with its own policy, and recordings can be set to transcribe automatically so playback carries closed captions. One coupling is worth knowing before troubleshooting: when organisers turn off Microsoft Copilot in Teams meetings and events, recording and transcription are turned off with it.

Two permissions have to line up

If Record is greyed out, the usual cause is not the person clicking it. Microsoft's guidance is that both the organiser and the recording initiator need recording permissions for a meeting to be recorded. One without the other fails.

Recording permission comes from policy, not from a per meeting setting. An administrator finds it in the Teams admin center under Meetings, then Meeting policies, where the Meeting recording toggle sits. The Global policy applies to everyone who has not been assigned a custom policy, so an organisation that has never touched this has recording on by default. In PowerShell the same control is the -AllowCloudRecording parameter on Set-CsTeamsMeetingPolicy, and it can be granted to individual users or to groups through Grant-CsTeamsMeetingPolicy.

Events are governed separately, which catches people out. Webinars and town halls sit under Events policies rather than Meeting policies, in a Recording and transcription section with a Record a webinar toggle for events up to 1,000 attendees and a Record a town hall toggle for events optimised for large audiences. The PowerShell equivalents are -RecordingForWebinar and -RecordingForTownhall on Set-CsTeamsEventsPolicy. Turning recording off in the meeting policy and assuming webinars followed is a common and quiet mistake, and Microsoft's own overview of recording and transcription policies uses exactly that scenario as its worked example: a finance team blocked from recording calls that can still record meetings and events, because only the calling policy was changed.

Who is allowed to start it, and who is not

Inside the organisation, the roles that can record are the organiser, co-organisers and presenters, subject to the policy above. Organisers with a Teams Premium licence can go further and use meeting options, meeting templates or sensitivity labels to control who is allowed to record and transcribe a specific meeting.

External participants cannot record meetings. The single exception is third party compliance recording: if an external Teams user who is enabled for compliance recording joins a meeting hosted by another organisation, their organisation records it regardless of the host's meeting recording setting. Microsoft's recording policy documentation states that organisers, co-organisers and presenters are notified when this happens and can remove the external participant if they do not want the other organisation capturing recordings.

That is the scenario worth rehearsing before a sensitive call with a larger counterparty. The notification arrives mid meeting, and the decision about whether to continue has to be made in front of everybody.

Telling people, and why the default notice may not reach them

Teams shows a recording notice, and there is a stronger option. The -ExplicitRecordingConsent parameter on Set-CsTeamsMeetingPolicy requires participants to give explicit consent before they can be included in a recording or transcript, and it covers Audio Conferencing as well. For teams that record client calls routinely, turning it on removes the argument about whether someone noticed a banner.

The notice also carries a privacy statement link, and this is where organisations quietly expose a gap. A custom privacy and security URL can be set through the Teams admin center under Meeting settings, then Email invitation, or through the -LegalURL parameter on the CsTeamsMeetingConfiguration cmdlet. If nothing is set, Teams falls back to the Microsoft Entra ID privacy policy, and if there is no Entra ID policy it falls back to the Microsoft privacy policy.

The gap is in the fallback. The Entra ID privacy policy is not shown to external tenant users or to anonymous users. In other words, the participants most likely to need the notice, namely clients and contractors joining from outside, are the ones who see the generic Microsoft statement instead of the organisation's own. Setting a real URL is a ten minute job that changes what an external attendee is shown.

Where the file goes and who can open it

Storage depends on the type of meeting. A private meeting recording is uploaded to the meeting organiser's OneDrive. A channel meeting recording goes to the channel's SharePoint site. Users with full edit rights on the file can change its permissions and share it later.

Access is narrower than most people assume. People invited to the meeting get permission to view the recording, but guests and external attendees can view it only if the recording is explicitly shared with them. So a client who sat in the meeting for an hour has no automatic access to the recording of it, and nobody is told that.

There is one more control on the channel side. -ChannelRecordingDownload is an organisation wide setting with two values. Allow, the default, saves channel recordings and transcripts to a Recordings folder that follows normal channel SharePoint permissions, so members can download them. Block saves them to a Recordings\View only folder where channel owners keep full access and members can view without downloading or editing. For town halls there is a further difference: attendees cannot reach the recording through the chat at all, because events publish through video on demand.

The 120 day clock

The detail that causes the most avoidable loss is expiry. Meeting recordings and transcripts have a default expiration time of 120 days. When a recording reaches that date, OneDrive or SharePoint moves it to the recycle bin of wherever it was stored.

The setting lives under Meetings, then Meeting policies, then Recording and transcription, as Recordings and transcriptions automatically expire, with the default expiration time measured in days. The value can be set from a minimum of 1 day to a maximum of 99,999 days, and PowerShell accepts -1 to mean never. Two limits sit on top of that: the maximum default expiration for A1 users is 30 days, and published recordings for Teams events expire after 30 days, extendable to 90.

The part that cannot be undone is the scope. Changes to the expiry setting affect only newly created recordings and transcripts. Existing recordings keep the expiry they were born with, and it cannot be changed. An organisation that discovers the 120 day default in month five cannot retroactively rescue what is already ticking.

Recovery is possible but time limited. An expired recording sits in the recycle bin of the organiser's OneDrive or the channel's SharePoint site, and for work or school accounts items in the OneDrive recycle bin are deleted automatically after 93 days unless an administrator has changed the setting. Once purged, the documentation on recording expiration is blunt that recordings cannot be recovered.

Finding a recording again, months later

Two things make an old recording findable. The first is search: recordings are indexed by Microsoft 365 search, and a transcript turns the recording into text that search can actually match, which is the practical argument for leaving automatic transcription on even when nobody reads the transcript at the time.

The second is eDiscovery, which is the route when a specific recording has to be produced rather than browsed for. Microsoft documents the path through the Purview portal: create an eDiscovery case, add a collection, commit it, then filter inside the review set to find recording and transcript files. That is an administrator task with compliance implications, not a substitute for filing recordings sensibly in the first place.

When a recording simply will not play, the banner text is diagnostic. Users see a message saying the recording is currently unavailable and to check with the organiser whether it is still uploading, has expired, or has been deleted. Those three causes need three different responses, and the banner does not distinguish between them, so the first question is always which organiser's OneDrive the file was written to. For a channel meeting the answer is the channel's SharePoint site instead, and the recycle bin there is the place to look before assuming the file is gone.

Microsoft also publishes separate troubleshooting articles for users who cannot record and for recordings that fail or go missing, and diagnostic tools for administrators. Checking the assigned policy for the exact meeting type comes first: meeting, 1:1 call, webinar or town hall each have their own setting.

Recording automatically, and the default that differs

There is a setting for recording without anyone remembering to press anything, and its default is not the same for meetings and events. If an administrator allows auto recording, the organiser's Record and transcribe automatically setting is off by default for meetings and on by default for events. So webinars and town halls are recorded automatically unless an organiser turns it off in meeting options, which is the opposite of what most people expect from the meeting behaviour they are used to.

With a Teams Premium licence, meeting templates or sensitivity labels can enforce a value for that setting rather than leaving it to each organiser. Without Teams Premium, auto recording remains a per meeting toggle, which means it is a habit rather than a policy.

For teams that record regularly, the useful discipline is not technical. It is deciding in advance which meetings are recorded, telling attendees in the invitation rather than at the moment the banner appears, and agreeing where the recording will live once the 120 day clock is running. Recordings that matter belong somewhere durable and attached to the work they describe, which is why some project management tools keep the recording, the transcript and the task on the same board rather than leaving the link to survive in a chat thread. Comparing how different tools handle that is usually a question about where the work already lives.

What to change first

Set a custom privacy and security URL and check the expiry value before touching anything else, because both of them silently affect recordings that have already been made. Then decide where recordings are filed after the meeting, whether that is a named SharePoint library or a board where the recording sits on the task it belongs to, as it does in Pinateca.

Q1. Why is the Record button greyed out in a Teams meeting?

Recording permission comes from policy, and both the organiser and the person starting the recording need it. An administrator controls it in the Teams admin center under Meetings, then Meeting policies, with the Meeting recording toggle, or through the -AllowCloudRecording parameter in PowerShell. If Copilot has been turned off for the meeting, recording and transcription are turned off with it.

Q2. Can an external guest record a Teams meeting?

No. External participants cannot record meetings, with one exception: third party compliance recording, where an external user's own organisation records automatically regardless of the host's setting. Organisers, co-organisers and presenters are notified when such a participant joins and can remove them from the meeting.

Q3. Where is a Teams meeting recording saved?

A private meeting recording is uploaded to the meeting organiser's OneDrive, and a channel meeting recording is saved to the channel's SharePoint site. It is also linked in the meeting chat and listed in the Recordings and Transcripts tab for that meeting in the Teams calendar.

Q4. How long do Teams recordings last before they are deleted?

The default expiration time is 120 days, after which the file is moved to the recycle bin of its storage location. An administrator can set anything from 1 to 99,999 days, or use -1 in PowerShell for no expiry, but the change applies only to recordings created afterwards. Published recordings for Teams events expire after 30 days, extendable to 90.

Q5. Do the people who attended automatically get access to the recording?

People invited to the meeting get view permission, but guests and external attendees do not. They can only open the recording if it is explicitly shared with them. For town halls, attendees cannot reach the recording through the meeting chat at all, because events publish through video on demand.

Q6. Is there a way to require consent instead of just showing a banner?

Yes. The -ExplicitRecordingConsent setting on the meeting policy requires participants to give explicit consent before they can be included in a recording or transcript, and it applies to Audio Conferencing as well. It is worth pairing with a custom privacy and security URL, because the default fallback statement is not shown to external or anonymous participants.