How to record a Teams meeting so the notes survive the call

Recording a Teams meeting takes three clicks. The part that goes wrong is everything after the meeting: the file is in a place nobody expected, the whiteboard that carried the whole discussion is missing from the video, and four months later the recording is gone because an expiry policy nobody configured did exactly what it was set up to do.

So this is worth treating as two separate questions. How to start a recording, which takes a paragraph, and how to make a recording still be useful next quarter, which is the rest of the article. Everything below reflects Microsoft's own documentation as of 25 September 2026.

What has to be true before the button appears

If the record option is missing or greyed out, one of three things is the cause.

The licence. Microsoft's support documentation lists the licences that allow recording: Office 365 Enterprise E1, E3, E5, F3, A1, A3, A5, Microsoft 365 Business, Business Premium and Business Essentials. A Teams account outside that list will not show the option.

The admin policy. Recording is controlled centrally through Meetings and then Meeting policies in the Teams admin center, where a Meeting recording toggle applies per policy, and through the AllowCloudRecording parameter in PowerShell. Both the organiser and the person starting the recording need recording permission. Webinars and town halls are governed by separate events policies, so a team that can record ordinary meetings may still be unable to record a webinar.

The role. Guests, anonymous participants and people from a different organisation cannot start or stop a recording. Only the organiser and members of the same organisation can, and where the organiser holds a Teams Premium or Copilot licence, a meeting option narrows that further to organisers and co-organisers, or to organisers, co-organisers and presenters.

One more dependency catches teams by surprise: if Copilot is turned off for a meeting or event, recording and transcription are turned off with it. A meeting created from a template that disables Copilot will not record, and the cause is not obvious from the meeting window.

Starting and stopping, and the option that matters more

During the call, open the More actions menu, choose the record and transcribe entry, then Start recording. Stopping works the same way, and leaving the meeting without stopping ends the recording anyway. The mobile apps carry the same menu, and a recording started on a phone behaves identically because the processing happens in Microsoft's service rather than on the device.

The setting that decides whether recordings actually happen is not that menu. It is Record and transcribe automatically in meeting options, which starts the recording when the meeting begins. Manual recording gets forgotten precisely on the calls that overrun, which are the ones worth having a record of. There is no admin policy for the option itself, though administrators can control whether organisers see it, and organisations can enforce it through a meeting template or a sensitivity label for categories of meeting that must always be recorded. Events behave the other way round: they are recorded automatically by default, and the organiser has to switch that off.

Transcription is a separate toggle that costs nothing to leave on and changes what the recording is worth. A video file is watchable. A transcript is searchable, which means a decision made at minute 34 can be found six weeks later by someone who was not there. Turning on transcription also produces closed captions during playback.

Where the file actually lands

This is the part that generates support tickets, and the rule is simple once stated. A recording of a private meeting goes to the meeting organiser's OneDrive, not to the OneDrive of whoever pressed record. A recording of a channel meeting goes to a Recordings folder in the SharePoint site behind that channel, where it inherits the channel's permissions like any other file.

Teams then makes the recording reachable from several places: a link in the meeting chat, the Recordings and Transcripts tab for the meeting in the Teams calendar, and the usual Microsoft 365 file lists such as Shared with me and Recent. Microsoft 365 search indexes it. People who were invited to the meeting have permission to view it, while guests and external attendees can only see it if the recording is explicitly shared with them.

Two consequences are worth planning around. First, ownership follows the organiser, so a recurring meeting organised by someone who later leaves the company leaves its recordings in a departing employee's storage. Second, for channel meetings an administrator can block downloads with the ChannelRecordingDownload policy, in which case recordings are saved to a view only folder where members can watch but not download or edit.

What the recording does not contain

Recordings capture audio, video and screen sharing. They do not capture whiteboards, annotations, shared notes, content shared through an app, or videos embedded in a PowerPoint deck.

For a status call, none of that matters. For a design review, an architecture discussion or a planning session run on a whiteboard, the missing item is often the only artefact anyone will want afterwards. The video will show people talking about a diagram that is not visible.

The practical habit is to save the artefact separately and attach it where the work lives, not only in the meeting chat where it will be scrolled past within a week. A diagram exported as an image and attached to the task it belongs to survives. The same diagram left on a whiteboard inside a meeting that has ended is effectively gone, whatever the recording shows.

Who is told, and who has to agree

Every participant receives a notification in their Teams desktop, web or mobile app as soon as recording starts, so recording is never silent. Beyond that notification, administrators can require explicit agreement: with the ExplicitRecordingConsent policy enabled, participants must consent before they can unmute or turn on their camera, and the consent result is stored in the meeting attendance report.

Organisations can also replace the default privacy statement shown with recordings with their own link, through the Privacy and Security URL in meeting settings. If no URL is set, Teams shows Microsoft Entra ID's privacy policy, or the Microsoft privacy policy when there is none.

One asymmetry deserves attention. External participants cannot record a meeting hosted by another organisation, with one exception: a third party compliance recording solution in the external participant's own organisation can capture the call regardless of the host organisation's recording setting. Organisers, co-organisers and presenters are notified when this happens and can remove that participant. Whether announcing a recording is sufficient or explicit agreement is required varies by jurisdiction, and that question belongs with whoever handles contracts and employment matters rather than with the person configuring Teams.

How long a recording lasts

By default, Teams meeting recordings and transcripts are deleted after 120 days. Two admin settings control this: Recordings automatically expire, which switches the behaviour on or off, and Default expiration time, which sets the number of days and defaults to 120.

Three details about that expiry matter more than the number itself. A recording moved out of its original location is no longer affected by the expiry setting, so relocating a file is also a way of keeping it. Microsoft states plainly that the expiry feature exists to save storage and does not enforce compliance requirements, so organisations with retention obligations should store recordings in a library covered by proper retention policies. And recordings are ordinary .mp4 files, which means anyone with edit rights can move, delete or reshare them like any other document.

For a project team, the practical reading is that a recording is a temporary artefact by default. Anything that needs to outlive the quarter has to be either moved deliberately or, better, reduced to something durable: a decision written on a card, a transcript excerpt attached to a task, a date changed on a plan.

Sharing, downloading and finding a recording again

Because a recording is a file in OneDrive or SharePoint, sharing it works the way sharing any document does. People who were invited to the meeting already have permission to view it, and anyone with full edit rights on the file can change those permissions and share it further, including with guests and external attendees who otherwise cannot see it at all. That is convenient and it is also the main way recordings end up somewhere unintended, so it is worth treating the sharing dialogue on a recording with the same care as a contract.

Downloading is available in the same way, with one exception worth knowing about: for channel meetings, an administrator can set the ChannelRecordingDownload policy to Block, which routes recordings into a view only folder where channel owners keep full access and members can watch without downloading or editing.

When a recording cannot be found, check in this order. Whether the meeting was a meeting, a one to one call, a webinar or a town hall, because each is governed by a different policy and stored differently, and attendees at events optimised for large audiences cannot reach the recording through chat at all. Then whose OneDrive it should be in, which is the organiser's and not the recorder's. Then whether the file was moved, since a relocated recording keeps existing but loses its link to the expiry policy. Administrators with a compliance requirement can also locate recordings and transcripts across the organisation through eDiscovery in the Microsoft Purview portal, which is the reliable route when a file has been moved or renamed by someone who has since left.

Turn the recording into something the team uses

A recording that nobody opens is storage. Three habits make the difference, and none of them require another subscription.

Name the decisions before leaving the call. Two minutes spent stating conclusions out loud gives the transcript something to find and gives the notes something to quote.

Attach the record where the work is tracked. A link to the recording on the relevant card or board means a person picking up the task next week has the context in one click, rather than searching a chat thread for a meeting title they half remember. A tool that can hold the meeting video and the searchable transcript beside its boards removes that search entirely, which is what the Pinateca feature set is organised around.

Extract the tasks the same day. The recording is evidence, not a plan. Items with an owner and a date belong in whatever the team actually opens each morning, and a comparison of how different tools handle that handoff is on the comparison pages.

What to change first

Turn on automatic recording and transcription for one recurring meeting, then check the following week whether anyone opened the file. If nobody did, the gap is not recording, it is that the decisions never reached the board, and a link from the task to the recording is a faster fix than any change to how the meeting is captured.

Q1. Why is the record button missing in a Teams meeting?

Usually one of three reasons: the account's licence does not include recording, an admin policy has the Meeting recording toggle off for that user, or the role is wrong because guests, anonymous participants and people from other organisations cannot record. A fourth cause catches teams out: if Copilot has been turned off for that meeting or event, recording and transcription are turned off with it.

Q2. Where does a Teams recording get saved?

A private meeting recording goes to the meeting organiser's OneDrive, not to the recorder's. A channel meeting recording goes to a Recordings folder in the SharePoint site behind that channel and follows the channel's permissions. In both cases a link appears in the meeting chat and in the Recordings and Transcripts tab in the Teams calendar.

Q3. How long are Teams recordings kept?

By default they are deleted after 120 days. Administrators control this with the Recordings automatically expire setting and the Default expiration time value, which is 120 days out of the box. A recording moved out of its original location is no longer governed by that expiry, and Microsoft notes that the expiry feature saves storage rather than satisfying compliance requirements.

Q4. Does the recording include the whiteboard?

No. Recordings capture audio, video and screen sharing, and leave out whiteboards, annotations, shared notes, content shared through an app, and videos embedded in a PowerPoint deck. For design and planning sessions, export the diagram separately and attach it to the task or board it relates to, because the video will show people discussing something the viewer cannot see.