Forum Discussion

hb200007

Copper Contributor

Nov 22, 2021

Solved

Recording failed to upload [November 2021]

A colleague recently created a meeting and recorded it. However, when they stopped the recording, we got the following: The recording seems to have been lost. It is not there on the c...

meetings

ChristianJBergstrom
Nov 23, 2021
As already mentioned, there was an incident yesterday affecting Teams meeting recordings. You need to open an official support ticket with Microsoft for assistance, the community cannot do anything about it. If you're not an Teams admin / IT admin reach out to your organizations admin and ask that person to create a support ticket from the M365 admin center.

Let me add to this that some users have been able to access their recordings by having their admin using the support tool "meeting diagnostics" from within the M365 admin center.

Self-help diagnostics for Teams administrators - Microsoft Teams | Microsoft Docs

justanotherday

Copper Contributor

Nov 22, 2021

We had the same problem today, raised a support ticket. I have no idea how you download files from AMS. It talks about it half way down this pages https://docs.microsoft.com/en-us/microsoftteams/tmr-meeting-recording-change
I only could find AMS within the azure portal under Media Services however nothing obvious in there.

ChristianJBergstrom

MVP

Nov 22, 2021

Hello, when they say it's being stored in AMS you don't actually go and download it from there but rather it's supposed to be downloadable just like any other recording. You did the right thing opening a support ticket if no option to download was present and it seems to be missing from the intended storage location. On the topic I actually heard in here about people using the "auto-record" feature and that put the recording in the supposed deprecated Stream storage..

justanotherday
Copper Contributor
Nov 22, 2021
FYI all our meetings are started manually. We use this feature a lot everyday, and this is the first time we have seen this. I can see from the logs we have had successfully recorded meetings today. So I am presuming this was a glitch on the back end.