Why are Live Event recordings only available for 180 days after the event

[Darrell Webster]

I recently discovered that the recordings from Live Events are only available in Stream for 180 days. Then they are deleted.
https://techcommunity.microsoft.com/t5/Microsoft-Teams/Live-Event-video-available-fo-180-days-after-...

The work around is to download the video after the event and upload it again to Stream.
Why should we have to go through these extra steps to keep recorded Live Events?
All company Live Events are valuable. The recordings can be organised into channels, embedded in SharePoint pages alongside resources and wrap up stories. But if the original recording is deleted after 180 days, that defeats the longevity of the recordings.
Please make the Live Events recordings remain in Stream indefinitely, without the extra steps of downloading and uploading again.

[#2]

I am very eager to learn about this as well.

[#3]

Thanks for highlighting this Darrell! Also, when the video is uploaded again, would the related conversations disappear?

This would be a must have for us as well. The beauty of all of the apps working together is to avoid extra steps/work like this.

[#4]

Whoa! I hadn't realized that. This would seriously degrade my efforts to get Live Events adopted versus going with another solution.  

[#5]

Following this...

[#6]

Same. The great thing about Live Events is there is an opportunity to capture a company moment, for example something that occurred in a town hall meeting that the org would want to keep longer.

[#7]

180 days hardly seems like enough time. I get that the trend is towards more ephemeral communication but a live event doesn't seem to fit the bill.

[#8]

You are correct. It means the conversation is no longer attached to the newly uploaded video. You can post in the threads "here's the new video link" but... Meh.

[#9 · Accepted solution]

Hi @Darrell Webster - understand the furstration and I'm sorry about that. Today events that are produced in Teams goes through the Azure Media Services stack. They have certain compliance requirements that required us to only keep data for 180 days. Now that we have a few GDPR items implemented, we're looking at ways that we can increase that time period or keep it consistent with Stream. We don't have an exact date but stay tuned. 

To clarify, events produed externally (via an encoder) go through Stream and they do not have the 180 day time limit. 

[#10]

@Darrell Webster This seems like a timebomb of a problem.

[#11]

@Ashwin Appiah, thank you for clarifying the difference. It’s good to know that events using an external encoder stay in Stream and are not limited to 180 days. 

I need to ask though, when a Teams online meeting is recorded, it stays in Stream. But when it’s a Live Event, it is served up by Azure Media Services. Is this how a Teams -produced Live Event is made publicly available? (Stream videos aren’t publicly available.)

I’m also interested to know what compliance requires the video to be removed from Azure Media Services after 180 days? How does it differ from live streamed events held on platforms like YouTube, Periscope or Facebook, where the video can remain publicly available indefinitely. 

[#12]

I don’t think there’s any difference regarding to public availability since normal teams meetings can have public anon users too! Also the recording has to be downloaded from AMS in order to watch it

[#13]

You’re right Adam, a Teams meeting supports anonmyous audience members. But only in realtime. Anonymous users can’t access the meeting recording in Stream can they?
Sorry, I should be more specific. I’m asking if Azure Media Services is used to make the the video available to an anonymous audience for public replay.

[#14]

Hm, no, afaik there no public display of the recording! You have to download it and distribute it other ways

[#15]

It would be great if Microsoft could use a common engine to deliver the video to both Organization and Public, used the same storage solution, and provided the customer with setting their own policy for data retention. Also, allow the usage of External Encoders, while allowing anonymous or guest access to Microsoft Live Event sessions. @adam deltinger