This is Microsoft’s vision for the new Stream:

As the M365 feature set grows, this becomes a growing compatibility issue with Stream (Classic).Īs a result, Microsoft is re-platforming Stream. For example, Stream (Classic) videos don’t work with records management capabilities, metadata settings, privacy features, sensitivity labels, etc. As a result, video files are missing content management features that you expect with a platform like M365. The major downside with Stream (Classic) is that videos are stored in a specific Stream repository - the files live in a standalone app in the back end of Microsoft 365 (M365). Stream (Classic) worked well for intranets as you could embed videos on SharePoint pages with the Stream webpart, and they showed up in a Feed webpart as either a single video or multiple videos in a list. Why are videos changing in Microsoft 365? Note: at the time of this writing, Stream (on SharePoint) and the migration tools are in preview mode, so some capabilities may vary at the general availability release. The older version of Microsoft Stream is still available, and will be for the foreseeable future, but it’s now called Stream (Classic). In terms of naming: the new version is called Stream (on SharePoint). This post explores the rationale behind the change, and what you need to do migrate to the new experience. Videos for the new Stream need to be saved into SharePoint/OneDrive libraries. The big change is this: Stream as a concept for videos still exists, but how videos are saved is different.

There are changes coming with a new version of Stream, which affects how videos are saved and shared.

Office 365 app launcher missing