Teams meeting recording or transcription not available: policy, storage and license checks

When a user says "I can't record" or "the recording never showed up", the cause is almost always one of four things: the wrong policy for that kind of meeting, the user's role or the organizer's meeting options, the storage the file is supposed to land in, or licensing. In this post I'll show how to tell which one you're dealing with, fix it, and prove that recordings and transcripts work again.

Symptoms#

Microsoft's troubleshooting article describes the two classic reports:

The meeting recording button is missing.
The recording is complete, but the recording is missing in meeting recap.

Variations include Start transcription being unavailable, the recording appearing for some attendees but not others, or channel members being able to play a recording but not download it. In Teams PowerShell, the policy behind the problem often shows one of these values:

• AllowCloudRecording : False or AllowTranscription : False in the meeting policy
• AllowCloudRecordingForCalls : False in the calling policy (1:1 calls)
• RecordingForWebinar : Disabled in the events policy (webinars)
• ChannelRecordingDownload : Block in the Global meeting policy (channel recordings are view-only for members)

Why it happens#

• Different features, different policies. Meetings use the meeting policy, webinars and town halls use the events policy, and 1:1 calls use the calling policy. Both the organizer and the person who starts the recording need recording permission.
• Role and meeting options. Attendees might not be allowed to record. Organizers can restrict recording and transcription in meeting options (the Who can record and transcribe choice needs Teams Premium), and turning off Copilot for a meeting also turns off recording and transcription.
• Account context. External participants can't record your meetings (third-party compliance recording aside), and anonymous, guest or external users might not be able to start a recording in the organizer's tenant.
• Storage. Meeting recordings go to the organizer's OneDrive, in the Recordings folder, even if the organizer didn't attend. Channel meetings go to the channel's SharePoint site, and 1:1 and group calls go to the OneDrive of whoever selected Record. If the organizer has no OneDrive, Teams tries the co-organizers, then the person who started the recording; if nobody has OneDrive, or the quota is full, the file is held temporarily and the organizer must download it within 21 days.
• Shared mailbox organizers. A shared mailbox without a Teams license follows the Global meeting policy, so blocking recording there blocks everyone in its meetings.
• Access and expiration. Invitees from the organizer's organization get view access automatically; external participants must be added by the organizer, and in meetings with more than 250 participants some people don't get permissions automatically. If the policy's Meetings automatically expire setting is on, older recordings are removed when they expire.

How to fix it#

1. Pin down the scenario#

Ask three questions: was it a scheduled meeting, a channel meeting, a webinar or town hall, or a 1:1 call; who organized it; and who tried to record (organizer, co-organizer, presenter or attendee, and from which account)?

2. Run Microsoft's diagnostic#

In the Microsoft 365 admin center, run the Teams Meeting Recording Test for the affected user; it checks the account, license and policy requirements for recording. For 1:1 calls, type Diag: Teams 1:1 Call Recording in the Need help? box, enter the user and select Run Tests.

3. Check and fix the policy#

Find the policy that actually applies to the organizer, including group assignments, and read the relevant settings:

Connect-MicrosoftTeams
Get-CsUserPolicyAssignment -Identity "organizer@contoso.com" -PolicyType TeamsMeetingPolicy
Get-CsTeamsMeetingPolicy -Identity Global |
    Format-List AllowCloudRecording, AllowTranscription, NewMeetingRecordingExpirationDays, ChannelRecordingDownload

No assignment means the Global policy applies. To fix it in the portal, go to Teams admin center › Meetings › Meeting policies, open the policy, turn on Meeting recording (and Transcription if transcripts are missing), save, and assign it. Or in PowerShell:

New-CsTeamsMeetingPolicy -Identity "Recording allowed" -AllowCloudRecording $true -AllowTranscription $true
Grant-CsTeamsMeetingPolicy -Identity "organizer@contoso.com" -PolicyName "Recording allowed"

For webinars and town halls, use Meetings › Events policies › Recording & transcription (Record a webinar, Record a town hall), or Set-CsTeamsEventsPolicy with -RecordingForWebinar Enabled or -RecordingForTownhall Enabled. For 1:1 calls, set AllowCloudRecordingForCalls in the user's calling policy.

4. Check the meeting itself#

• Make the user a presenter or co-organizer if attendees can't record.
• Ask the organizer to review Meeting options › Recording & transcription, and to check that Copilot hasn't been turned off for that meeting.
• Make sure the user is signed in with the expected work account, not a guest identity; if needed, have someone from the organizer's organization start the recording.
• Leave and rejoin, or try the Teams web client.

5. Check where the file should land#

Confirm the organizer has a licensed, provisioned OneDrive with free space, and look in its Recordings folder. Plan for roughly 400 MB per hour of recording. For channel meetings, check the channel's SharePoint Recordings folder; Microsoft notes that channel recording upload isn't supported when the site uses IP-based restrictions, and recommends Conditional Access instead. If a recording didn't upload, the organizer must download it within 21 days, then fix the license or quota.

6. Check access and expiration#

External participants only see a recording that the organizer shares with them; see external access vs guest access in Teams for how those identities differ. If recordings disappear after a while, review Meetings automatically expire in the meeting policy (PowerShell: NewMeetingRecordingExpirationDays) and check the organizer's OneDrive recycle bin.

Verify the fix#

1. Allow time for the policy change to reach the user, then have the affected organizer schedule a short test meeting with a colleague.
2. Start recording and transcription from the meeting's More menu (Record and transcribe), talk for a minute, then stop.
3. Within a few minutes, the recording appears in the meeting chat and on the meeting's Recordings and Transcripts tab, and the MP4 sits in the organizer's OneDrive Recordings folder.
4. Playback shows captions. Microsoft notes that captions are available only if transcription was on while recording, and aren't fully supported once the file is moved or copied.
5. Rerun the diagnostic; it should report no issues.

Key takeaways#

• Match the policy to the meeting type: meeting, events or calling policy.
• The organizer's policy and OneDrive matter as much as the recorder's.
• Keep licenses consistent across organizers; group-based licensing helps, and its errors are easy to spot.
• Recordings are ordinary OneDrive and SharePoint files, so retention, sharing and eDiscovery apply. To collect them for a legal matter, see eDiscovery search and export errors.

References#

• Manage Teams recording policies for meetings and events (Microsoft Learn)
• Teams meeting recording and transcript storage and permissions in OneDrive and SharePoint (Microsoft Learn)
• Issues that affect meeting recordings (Microsoft Learn)