Migration Details: Microsoft Stream (2023)

This article covers several migration topics that require detailed explanation.

Video Streaming Report (classic)

It's an inventory report of all the videos on Stream (classic) and provides a bunch of metadata information. The report will help you plan your migration and make decisions about which video to migrate to Stream (in SharePoint). The output is a CSV file with one row for each video in Stream (Classic). We also created oneSample Power BI Desktop report templatewhich you can use to analyze, filter and understand inventory data.

The report includes the following information for each video

• video identifier: also found at the end of the URL when playing a (classic) stream video
• Videoname
• Videostatus: See definition below
  • created= Record created but upload not started
  • From you= Uploading video
  • Processing= Upload successful but currently in progress
  • Completed= Processing is complete
  • Excluded= Deleted by software (will be available in Recycle Bin)
  • mistake= Error uploading or processing
  • life= Live stream running
• video description
• release date
• Last viewed date: Date the video was last viewed. This date was recorded around July 2021. Any video uploaded and viewed before July 2021 would have this field blank even if it was viewed.
• size: Em-Bytes
• number of views
• number of likes
• content type: can take on the following values
  • Generic
  • meeting
  • live event
• privacy mode: can take on the following values
  • Organisation: visible to everyone in the organization
  • Private: visible to a select few people
• The creator: The original video uploader
• the owner: Can be multiple, single or groups
• Container (ID, Name, Typ, E-Mail): These are useful when you want to map videos to containers, as the tool displays the data at the container level. These values ​​can be empty if the video is orphaned and does not belong to any container. Container email is also blank for flow groups.

Suitable videos for migration

In order for a video to be migrated, it must meet the following criteria. Only these videos can be found via the migration tool.

1. Specify Processing or Done
2. Released
3. ID of the non-empty container

Videos cannot be migrated

Videos that cannot be migrated are therefore:

1. Videos that are not published, i. H. the only person who can see it is the original uploader
2. Videos that are in an incorrect processing or uploading state and therefore cannot be played
3. Videos that are "orphaned", meaning that there are no longer any owners in the organization of the video, the people who uploaded it have left the organization, the "container code" for them in the report is empty*
4. “Temporarily Deleted” videos i.e. H. they have been deleted by the user but are still in the recycle bin

* Orphaned - Currently orphaned videos and an orphaned video container are not visible in the migration tool. We are working in CY2023 to improve the migration tool so that you can migrate all orphaned videos through a single orphaned container. If you want to migrate them before then, a workaround is to assign owners to these videos and they will be recognized in the appropriate container in the tool.

report format

Important information about the report:

• Last viewed date: This date was recorded around July 2021. Any videos uploaded and viewed prior to this date would have this field blank

• Condition:

  (Video) Migrating from Stream Classic
  • Created = Record created but upload not started
  • Uploading = the video is uploaded
  • Processing = Upload successful but currently processing
  • Done = The editing is complete
  • Deleted = Soft Deleted (will be available in Recycle Bin)
  • Error = Error uploading or processing
  • Live = live stream is running

• Container (ID, Name, Typ, E-Mail): These values ​​can be empty if the video is orphaned and does not belong to any container.

Steps to run the script

1. Navigate to Stream Admin Settings -> Stream Migration -> Reports (Preview) and download the script

2. Copy the stream token from the browser and save it to a file.
   • Open the browser, press F12 and navigate to the stream portal
   • On the "Network" tab, select and filter for "refreshtoken". From the two requests on the left, select the one with the request method – GET.
   • Under Request Headers, locate the Authorization header and copy the value after Bearer.

• Save it in a file like below. Example: C:\Users<alias>\Documents\StreamReportGenerator\token.txt

Large tenant refresh token

• Large tenants may need to enter the token more than once as the token expires after an hour
• Update the token file with the latest browser token and run the script again

3. Open PowerShell and run the script by providing four inputs:

   • InputFile (Required): Path of the file to import the stream token
   • OutDir (Mandatory): Path of the folder where the final report and some intermediate files will be saved
   • AadTenantId (required): Tenant AAD Tenant ID
   • ResumeLastRun (optional): A true/false flag to control whether to resume execution from the last run or to fetch all videos from the beginning again.template= true
   • PublishedDateLe (optional): Searches for video entries whose publication date is less than the value. For example: "2022-07-15"
   • PublishedDateGe (optional): Searches for video entries with a published date greater than the value. For example: "2022-01-15"

   Beispiel: .\StreamClassicVideoReportGenerator.ps1 -AadTenantId "00000000-0000-0000-0000-000000000000" -InputFile "C:\Users\alias\Desktop\token.txt" -OutDir "C:\Users\alias\Desktop" -ResumeLastRun verdadeiro.

   Beispiel: .\StreamClassicVideoReportGenerator.ps1 -AadTenantId "00000000-0000-0000-0000-000000000000" -InputFile "C:\Users\alias\Desktop\token.txt" -OutDir "C:\Users\alias\Desktop" -ResumeLastRun true -PublishedDateLe "2022-07-15" -PublishedDateGe "2022-01-15"

4. The script runs and retrieves data from the reporting APIs

5. Responses from API calls are saved in a folder "StreamClassicVideoReport" underOutDirPasta

6. After the script runs, the final report CSVs are available in the StreamClassicVideoReport folder (the path is shown in the console).

7. A new folder is generated in the StreamClassicVideoReport folder for each execution of the script. The CSV files in these folders contain your renter's video data

Watch:

• Do not open the generated files while the script is running. This leads to crashes during script execution
• Generated files may contain duplicate entries for a video

Resume the script if it fails

• If the script stops midway due to network/machine issues, the admin can re-run the script and it will continue from where it left off
• By default, the resume flag is true. If you want to start a new race, pass theResumeLast Runparameters as 'false'

Example: .\StreamClassicVideoReportGenerator.ps1 -AadTenantId "00000000-0000-0000-0000-000000000000" -InputFile "C:\Users\alias\Desktop\token.txt" -OutDir "C:\Users\alias\Desktop" -ResumeLastRun not correct

Troubleshooting crashes

To help troubleshoot the crash, please split the generated log.txt and state.csv filesOutDirPasta

Sample Power BI analytics report

Last updated on November 22, 2022 to v0.7

To make it easier to analyze the inventory report output, we've created a sample Power BI Desktop template that will hold the CSV files generated by the script. The Power BI sample report will help you better understand what content is in Stream (classic), who owns it, and if it's out of date. You can use this report to decide which containers to migrate.

How to run the analysis report

1. Download PowerBI Desktop

2. Download the sample PowerBI templatewhich parses the flow inventory CSV file (classic)

3. Open mindedthe downloaded.pbit-Datei in PowerBI Desktop

4. Enter the local file pathto the folder containing the .csv exports generated from the script (remove the backslashes at the end of the path)

   Example:C:\StreamClassicVideoReport\20221013T1155251021

5. SelectLaden

Permissions and Goals

This section explains how permissions are mirrored between Stream (classic) and Stream (in SharePoint).

We've already discussed the standards for theVideo migration destination. Administrators are free to override our default settings. You can change location for a single target or in bulk.

• In Stream (classic), a video can have multiple owners. In OneDrive and SharePoint (ODSP), a video can have multiple owners in SharePoint, but it always has a single owner in OneDrive for Business (ODB).

• ODSP stands for physical boundaries, videos in a physical location (e.g. a folder or document library). Stream (Classic) has soft borders, which means videos can be viewed in multiple locations and groups, e.g. B.my contenteThe group.

• Flow (Classic) has legacy constructs such as flow groups or a corporate channel. ODSP has Microsoft 365 communication groups and websites.

• With a Microsoft 365 group on SharePoint, members of a group always have editing rights. For Stream (Classic), members can have edit or view rights based ontaxpayerConfiguration at the time of group creation.

Permissions for a video between Stream (classic) and Stream (in SharePoint) are mirrored. However, due to the above differences in permissions behavior, we encourage you to read this article in detail. Once you understand the permissions differences, set custom permissions on some test videos, migrate them, and verify that the permissions behaved as expected. Some videos are linked to multiple entities, e.g. B. users, groups, stream groups and a corporate channel. The migration target and permissions for these multi-entity videos are explained in the following cases.

Case 1: Personal video, single owner case

User A uploads a video to Stream (Classic). The video is never featured in any group or channel and User A is the sole owner. Default migration mapping in Stream:

• The video is added to User A's Stream Migrated Videos folder in OneDrive for Business. User A is given Owner permission by default.
• If a video is a Teams meeting recording, it will be migrated to the Recordings folder within the same Stream Migrated Videos folder.
• The video in OneDrive will have viewing (custom) permissions set to match the permissions set for Stream (classic). Viewers cannot download files.

Case 2: Private video, multiple owners

User A uploads a video to Stream (Classic) and shares ownership with User B. The video never appears in any group or channel. Default migration mapping in Stream:

• The video is added to User A's Stream Migrated Videos folder in OneDrive for Business. User A is given Owner permission by default.
• If the video is a Teams meeting recording, it will be migrated to the Recordings folder within the same Stream Migrated Videos folder.
• (Custom) User B is granted owner permissions for the video.
• The video in OneDrive will have viewing (custom) permissions set to match the permissions set for Stream (classic). Viewers cannot download files.
• User B sees this video under Shared with me on office.com, OneDrive, etc. via Microsoft 365 search.

Case 3: Group video and personal and group owner case

User A uploads a video to Stream (Classic) and shares ownership with Group A. Default migration mapping in Stream:

• The video is added to the Stream Migrated Videos folder on Group A's SharePoint team site.
• (Custom) We've broken the Stream Migrated Videos folder's inheritance and it doesn't inherit permissions from its parent site. Additionally, we will apply specific permissions to the folder to match those of the corresponding group membership in Stream (Classic). Files in that folder still inherit permissions from it.
• (Custom) User A is granted owner permissions for the video.
• User A sees this video under Shared with me on office.com, OneDrive, etc. via Microsoft 365 search.
• The video in SharePoint is set with viewing (custom) permissions that match the permissions set for Stream (classic). Viewers cannot download files.
• If a video is a Teams meeting recording, it will be migrated to the Recordings folder within the same Stream Migrated Videos folder and corresponding channel folders.

Case 4: Group video, case of multiple group owners

User A uploads a video in Stream (Classic) and shares ownership with Group A and Group B. Default migration mapping in Stream:

• The first Microsoft 365 group the video is added to is its default owner.
• The video is added to the Stream Migrated Videos folder on Group A's SharePoint team site.
• (Custom) We have broken inheritance for the Stream Migrated Videos folder and it does not inherit any permissions from its parent site A. Also, we will enforce specific permissions on this folder to match those of Group A's corresponding membership Stream (classic ). Files in that folder still inherit permissions from it.
• (Custom) Group B Members of the Microsoft 365 group are given owner permissions to the video. They won't see this video directly in their Microsoft 365 group, but will still have access through Microsoft 365 Search.
• (Custom) The original uploader of this video for streaming (classic) is granted owner permission and sees this video in Shared with Me on office.com, OneDrive, etc. via Microsoft 365 search.
• The video in SharePoint is set with viewing (custom) permissions that match the permissions set for Stream (classic). Viewers cannot download files.
• If the video is a Teams meeting recording, it will be migrated to the Recordings folder within the same Stream Migrated Videos folder and corresponding channel folders.

Case 5: Stream-only group video, case with multiple group owners

User A uploads a video to Stream (classic) and shares ownership with Stream-only group and Microsoft 365 Group A as other owners of the video. Default migration mapping in Stream:

• Between the Microsoft 365 and the stream-only group, the first stream-only group to which the video was added is selected as the target.
• Administrators can create a new SharePoint site or use an existing site to migrate Broadcast Group content
• A top-level folder "Stream Migrated Videos" is created in the root document library of the above site. And a folder (with the group name) will be created in this top-level folder. The video is then added to the group folder.
• (Custom) We have broken inheritance for the Stream Migrated Videos folder and it does not inherit any permissions from its parent site A. Additionally, we will apply specific permissions to each group folder to match those of the corresponding group membership in Stream (Classic ). Files within the group-specific folder inherit its permissions.
• (Custom) Group A Members of the Microsoft 365 group are given owner permissions to the video.
• Group A members won't see this video directly on the group's website, but will still have access through Microsoft 365 Search.
• (Custom) The original uploader of this video for streaming (classic) is granted owner permission and sees this video in Shared with Me on office.com, OneDrive, etc. via Microsoft 365 search.
• The video will have viewing (custom) permissions set to match the permissions set for Stream (classic). Viewers cannot download files.
• If the video is a Teams meeting recording, it will be migrated to the Recordings folder within each group and their channel folder.

Case 6: Corporate channel video, case with multiple group owners

User A uploads a video to Stream (classic) and shares ownership with the corporate channel and Microsoft 365 Group A as other owners of the video. Default migration mapping in Stream:

• Between the Microsoft 365 group and the corporate channel, the first Microsoft 365 group to which the video was added is targeted.
• The video is added to the Stream Migrated Videos folder on Group A's SharePoint team site.
• (Custom) We have broken inheritance for the Stream Migrated Videos folder and it does not inherit any permissions from its parent site A. Also, we will enforce specific permissions on this folder to match those of Group A's corresponding membership Stream (classic ). Files in that folder still inherit permissions from it.
• The corporate (custom) channel doesn't see this video on their website, but the video is accessible to anyone in the organization with viewing permissions (EEEU) through Microsoft 365 search.
• (Custom) The original uploader of this video for streaming (classic) is granted owner permission and sees this video in Shared with Me on office.com, OneDrive, etc. via Microsoft 365 search.
• The video in SharePoint is set with viewing (custom) permissions that match the permissions set for Stream (classic). Viewers cannot download files.
• If a video is a Teams meeting recording, it will be migrated to the Recordings folder within the same Stream Migrated Videos folder and corresponding channel folders.

Case 7: Corporate channel video, user owner case

User A uploads a video to Stream (Classic) and links it to the corporate channel. Default migration mapping in Stream

• From multiple users and company-wide channels, the first company-wide channel to which the video was added is selected as the target.
• Administrators can create a new SharePoint site or use an existing site to migrate content from an "enterprise-wide channel".
• A top-level folder "Stream Migrated Videos" is created in the root document library of the above site. And a folder (with the channel name) will be created in this top-level folder. The video will then be added to the channel folder.
• (Custom) We have broken inheritance for the Stream Migrated Videos folder and it does not inherit any permissions from its parent site A. We will also enforce EEEU view permission on this top-level folder. Files in the channel folder inherit the permissions of their parent channel folder.
• (Custom) The original uploader of this video for streaming (classic) is granted owner permission and sees this video in Shared with Me on office.com, OneDrive, etc. via Microsoft 365 search.
• The video will have viewing (custom) permissions set to match the permissions set for Stream (classic). Viewers cannot download files.
• If the video is a Teams meeting recording, it will be migrated to the Recordings folder within each channel's folder.

In light of the above, we recommend:

1. Migrate multiple broadcast-only groups to a single site and migrate enterprise-wide channels to a single site. Don't migrate both to the same site.
2. Do not migrate all broadcast-only channels or groups to individual sites, as custom permissions set on each file will exhaust thisQuotas at the SharePoint site level.
3. Prefer default values ​​for most migration targets. Migrate Microsoft 365 Groups to your sites and existing users to their respective ODBs.

Reasons for the above decisions

1. Keeping videos in a group ensures they comply with the SharePoint permissions model. Also, users can see all their videos in one place. If no default settings are selected for videos in a group, some group videos will be migrated to individual users' ODBs.
2. For a video associated with stream-only groups and a Microsoft 365 group, we would move the video to the former as we cannot assign permissions to a stream-only group in SharePoint

• If you decide to move the Microsoft 365 group first, it won't include the regular videos because those videos would be moved with the Stream Only group.
• On the other hand, if you migrate the stream-only group first, we'll migrate all videos, including the general ones, and also set permissions for the Microsoft 365 group for the commons. This is possible because a Microsoft 365 group identity already exists in the ODSP. However, the reverse is not possible.

3. Similarly, for videos associated with a corporate channel and Microsoft 365 group, we would move the video to the latter since permissions cannot be set on the corporate channel (videos are visible to everyone in the organization).
4. Moving videos to corporate channel folders is preferable to adding to a user's ODB because we take advantage of keeping the video together in the corporate channel.

In summary, if a video is associated with multiple entities, e.g. For example, a Microsoft 365 group, a Stream group, and a corporate channel, let's follow this order:

Other factors to consider

1. Stream only syncs Microsoft 365 Groups from Teams and SharePoint. no channels created there For all channel-based meetings in such groups, this channel is not available in the stream and is therefore missing from the whitelist in the UI. You would see the channel recordings in the group list view, but that group is not set as the owner. See picture below.

2. Previously, when a Teams meeting recording associated with a group was uploaded, Teams leveraged the group's membership and assigned individual permissions to its members. In these cases, the file is associated with its creator and moved to its ODB. You won't see members added individually to Teams meeting recordings as a group. See picture below.

Pass URL (classic) and embed support after migration

Stream (classic) URLs and embeds are supported for one year after the Stream (classic) end of life. The following table summarizes the support plan.

Link-URL

• Existing Stream (classic)Video-Linkwill continue to work after migration. It will be redirected to ODSP for playback from the migrated target.

• an existing oneGroup linkfrom the Stream Portal (Classic) redirects to the destination folder selected by the administrator during migration.

• an existing oneLink to the channelfrom the Stream (Classic) portal redirects to the channels folder created within the selected target SP site or ODB by the administrator during migration.

embedded video

Support during public preview

During preview, the video is embedded in SharePoint, Teams, or a third-party siteDO NOT keep playing inline. The thumbnail will be replaced with a link to the migrated video (see screenshot below). When a user selects thewatch videobutton, OnePlayer plays the video from the migrated location in a new browser window.

General tool availability support

Videos are played inline, similar to embedded stream playback (classic).

Videos migrated during preview that have been partially supported will also play inline after general availability.

built-in channel

Channel embeds in SharePoint and Teams will bepartially supportedPostmigration.You will no longer view or play inline videos. The new channel thumbnail contains a link to the migrated channel's videos folder (see screenshot below). thewatch channelThe button takes users to the migrated channel video folder in ODSP.

also see

Migration Strategies Guide

Adoption Strategies Guide

Stream migration overview (in SharePoint)

Migrate your videos from Stream (Classic) to Stream (in SharePoint)

Migrationsdetails

Migration tool details

Learn more about Stream (in SharePoint)

Stream resources and roadmap (in SharePoint)

Contact the Stream engineering team to provide feedback and learn more about Microsoft Stream