When Teams says a meeting recording failed to upload to OneDrive, the file usually still exists — but Teams will not try the upload again on its own. That one detail decides what you should do next, and it comes straight out of Microsoft's admin documentation rather than from guesswork.
Here is the relevant passage, verbatim, from Microsoft's page on recording and transcript storage in OneDrive and SharePoint:
"If a Teams meeting recording fails to successfully upload to OneDrive because the organizer, co-organizers, and recording initiator don't have OneDrive accounts, or the storage quota is full, an error message appears. The recording is instead temporarily saved to async media storage. Once the recording is in async media storage, no retry attempts are made to automatically upload the recording to OneDrive or SharePoint. During that time, the organizer must download the recording. The organizer can try to upload the recording again if they get a OneDrive or SharePoint license, or clear some space in their storage quota. If not downloaded within 21 days, the recording is deleted."
What this error actually means
Four separate facts are packed into that paragraph, and most write-ups of this problem miss the third one.
- Microsoft names exactly two causes here: nobody in the chain (organizer, co-organizers, recording initiator) has a OneDrive account, or the storage quota is full.
- The recording is diverted to "async media storage", which Microsoft describes as temporary.
- "No retry attempts are made to automatically upload the recording." Waiting does not help. There is no background job that will quietly succeed overnight.
- The download is the organizer's job. The same passage puts the obligation on the organizer, not on the person who pressed Record.
Point 3 is the one worth internalising. The usual instinct with a failed cloud upload is to give it time. Here, time only moves you closer to deletion.
Where async media storage physically sits, and whether an admin can retrieve a file from it after the window closes, is not something the official pages spell out — check the official documentation if you need that answer for a compliance case.
The deadline is 20 days or 21 days, depending on which page you read
Microsoft publishes three statements about this window, and they do not agree.
The user-facing help page "I can't record a meeting in Microsoft Teams" says:
"If you can't find your recording in OneDrive but see the below message with your recording in chat history, your recording failed to upload to OneDrive and will be stored temporarily for 21 days. You can retry uploading it to OneDrive or download it to your local device."
The admin storage page, quoted above, agrees: "If not downloaded within 21 days, the recording is deleted."
But the Limits and specifications for Microsoft Teams table gives a different figure for the same idea:
"Teams keeps meeting recordings that don't get uploaded to Microsoft Stream, available for local download 20 days"
Two pages say 21, one says 20. Act on 20. Downloading a day early costs nothing; being a day late costs the recording. And if this is a file somebody will ask for later, do not plan around either number — get it onto storage you control this week.
The fastest fix: download it, then put it somewhere permanent
- Open the meeting chat and find the failure message attached to the recording. That is the entry point both Microsoft pages point to.
- Download the file to your device. Per the admin page, this is the only action that reliably preserves it.
- Clear the blocker. The same page says the organizer can retry the upload after getting a OneDrive or SharePoint licence, or after clearing space in the quota. If the cause was a missing licence, that is an IT admin request, not something you can self-serve.
- Re-upload the file manually once the blocker is gone.
Recordings are not small. Microsoft's own capacity planning guidance states: "The size of a one-hour recording is 400 MB." A two-hour workshop is therefore roughly 800 MB before you have done anything with it — and Microsoft also warns that "External sharing isn't designed for the distribution of large files or a large number of files."
So if the next step is emailing that file to a client or dropping it into a chat thread, shrink it first:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs entirely in your browser tab — the recording is read from disk, re-encoded locally, and handed back. Nothing is uploaded, which matters when the file is an internal meeting. If you would rather tune the settings yourself, the video compressor exposes the same controls, and Gmail's own attachment ceiling is a good illustration of why a raw recording rarely travels well by email.
If you never saw a failure message
Not every missing recording failed to upload. Before you assume the worst, rule out the cheaper explanations.
It uploaded, just not where you looked. Destination depends on the meeting type:
| Type of recording | Where the file lands |
|---|---|
| Meeting or event | The organizer's OneDrive Recordings folder — "even if the organizer didn't attend the meeting or event" |
| Channel meeting | The channel's SharePoint site, in a folder named Recordings |
| 1:1 and group calls | "the OneDrive account of the user who selected Record" |
For non-channel meetings, Microsoft's troubleshooting page adds that the recording sits "in the Recordings folder under My files".
The recording never started. Microsoft is blunt about this: "Check if there is a message indicating that your recording started. If you don't see this message, the recording most likely didn't start and can't be recovered." The most common reason is a dialog nobody finished — "The recording only starts once you select Confirm."
The chat link is missing, not the file. The troubleshooting page describes a known issue where "In high-volume chat sessions, a known issue prevents the meeting recording link from appearing for one or more users," and suggests scrolling to the top of the chat window and back down to trigger a refresh.
It expired. Recordings and transcripts have a default expiration of 120 days, and on expiry they move to the recycle bin of wherever they were saved. Microsoft's guidance if you know the recording existed: "check if it was deleted, moved to a different location, or expired. Look in your recycle bin and second stage recycle bin." One clarification worth quoting because so many people assume the opposite: "Watching the recording won't affect the expiration date."
How to tell it worked
Open the organizer's OneDrive Recordings folder (or the channel's SharePoint Recordings folder) and confirm the .mp4 is listed there, not just playable from the chat card. If the manual re-upload itself fails instantly, check the file name — OneDrive and SharePoint reject these characters outright:
" * : < > ? / \ |Leading and trailing spaces are not allowed either. Renaming and retrying costs ten seconds and rules out an entire class of failure.
FAQ
Will Teams retry the upload by itself if I just wait? No. Microsoft's storage page states that once the recording is in async media storage, "no retry attempts are made to automatically upload the recording to OneDrive or SharePoint." Download it yourself.
Is the window 20 days or 21 days? Both figures are published. Two Microsoft pages say the recording is deleted if not downloaded within 21 days; the limits and specifications table lists 20 days for recordings available for local download. Treat 20 as your deadline.
Why did it fail when I have plenty of OneDrive space? For a meeting, the documented destination is the organizer's OneDrive, so your own free space is not necessarily the quota involved. The documented fallback order is co-organizer's OneDrive first (by the order of co-organizers in meeting options), then the OneDrive of whoever started the recording, and only then async media storage.
Can an admin recover a recording after the window closes? The official pages describe async media storage as temporary and say the recording is deleted if not downloaded in time, but they do not describe an admin recovery path — check the official documentation before promising anyone a restore.
What about the transcript that went with it?
Transcripts are a separate file. Organizers and co-organizers can download one as a .docx or .vtt file — those are the two formats the support page documents, so if your editing software wants SubRip, run the file through VTT to SRT. More fixes like this one live in the fix guides hub, and every browser-side converter is listed under all Clapr tools.
Quotations are from Microsoft's Teams documentation on recording and transcript storage, limits and specifications, and the support article "I can't record a meeting in Microsoft Teams", checked 16 September 2026. Microsoft revises these pages — verify before relying on a number.
