01-23-2020 10:16 AM
01-23-2020 10:20 AMSolution
01-23-2020 10:47 AM - edited 01-23-2020 11:20 AM
Thanks @Linus Cansby . We've been testing recordings and at some point, we had users who received the attached message after recording. Though the meeting notes a recoding failed message, they could click download and it saved the recording locally, and the recording was playable. I'm trying to figure out what setting we had so that worked.
01-23-2020 12:10 PM
Second time I see that message this week here, some bug maybe? The recording will be downloaded from a Teams service running in Azure, it is in that service that the meeting is recorded. When you stop the recording the recording should be encoded and uploaded from the teams recording service in Azure to Microsoft Stream and it is that that fails for you.
Make sure that users have a license for Microsoft Stream and that it is activated for them.
01-24-2020 12:59 PM
02-05-2020 01:01 AM
I did not understand if you need to save it locally or this is not the preferred behavior?
Some companies do not want to have the recording to be saved in the Stream.
In such cases you may consider using a third party solution such as SphereShield here:
This will also allow to share video externally as well as perform eDiscovery on a company level.
09-11-2020 11:04 AM
@Erin Scupham If you disable the Stream licences for users then the meeting is recorded and processed in Azure but it will not upload it to Stream as the user does not have a licence. The recording will be visible in the meeting chat the user has 21 days to download the meeting recording before the file is auto deleted.