DestinationMapping Report, Script, and Upload

[Anne O'Day]

We have a tenant with more than 50K SharePoint sites. According to the documentation, we should plan to upload Migration Destinations because automapping may not work correctly.

I've been trying to get the "MigrationDestinations" script to work and so far have had no success. When I download the sample, it's only downloading the list of containers presently showing on the Migrations tab. When I run the script, it seems to only want to look for M365Group containers with Null values.

So first I had to find an M365 Group that had no destination path set already, load that into the Migrations tab just in order to try testing out the script.  Once I ran the script, it didn't seem to want to run until I was willing to do a full inventory report first.  OK fine, got that done.  Then I ran the command with the " -CreateDestinationPathMappingForM365GroupContainers true -MigrationDestinationCsvFilePath" bits again, and it gave me an empty file with header.  I don't know if it's having an issue with Exchange or not ... I'm guessing it's just doing a Get-UnifiedGroup command which I can do, so I don't think it's an issue with not-enough-permissions.

So as a test, I then took my empty output file and added one line to populate one destination for one M365 group that previously had no destination set, and that seemed to work. Just for grins and giggles, I put an email address in there of the person's OneDrive where I want that M365 Group content to go, and it seemed to take that.

Could anyone here confirm for me the following assumptions:
1) The only purpose of this script is to fill in MISSING destinations .... as long as we have destinations already filled in or are able to set them in the GUI, then there is not some other requirement that says we have to run the script.
2) This script is only intended to map M365Groups to their respective SharePoint sites, it does not allow for deviations from that.  
3) If I choose to manually build a CSV with Destination Paths and use the Upload Destinations feature, that should work.

Reference: https://learn.microsoft.com/en-us/stream/streamnew/migration-details#destination-mapping-report

Thanks!  

[#2]

Updating my post with my own findings from trial and error.

Oh, hey, the documentation changed. Previously it said "If your SharePoint has more than 50-K sites, Microsoft 365 group autodestination mapping may not work perfectly." That number has changed to 100-K sites as of 9/25/2023.

After getting the Destination Mapping template downloaded, the Microsoft Documentation seems to suggest that you have to run StreamClassicVideoReportGenerator_V1.11.ps1 with some parameters to create a new file with destination paths filled in. As near as I can tell, the only purpose of this step is for mapping M365Group containers that show up as NULL in the MigrationDestinations.csv. It will proceed to "automap" those NULL values to the respective SharePoint sites for those M365 Groups. I don't think it's going to help you in cases where the M365 Group has already been deleted, the M365 Group exists but has no SharePoint site, or where you want to map any container to a site different from the site suggested by the Migration tool. But as I said, I wasn't able to get the script to work, so I'm kind of guessing about what it's supposed to do.

From there, I tried doing some manual filling in of Destination Paths to the CSV file for some M365 Group Containers and Companywide Channel containers. Generally it seemed to work well. It did not like one site that had double quotations in the container's name.

It does seem to me that this whole process is a bit limited by the fact that you have to move your containers to the Migrations tab just in order to be able to set destinations. I was hoping to set all my destinations now and migrate in waves later. I guess I can still do that, but I was hoping to only move things to the Migrations tab when I was actually ready to migrate them.

If you really need help with mapping your M365 Groups, I'd suggest you or someone who is an Exchange admin run the Get-UnifiedGroup command so you can find the appropriate group by PrimarySMTPAddress (as indicated in the Stream Inventory Report on the "ContainerEmailId" column) and locate its SharePointSiteURL to put into the MigrationDestinations.csv for the Destination Path column. Here's a sample of the command.

Get-UnifiedGroup -Resultsize Unlimited | Select Name, DisplayName, PrimarySmtpAddress, SharePointSiteUrl | Export-CSV AllUnifiedGroups.csv -NoTypeInformation
(other properties you might find helpful: Guid, GroupMemberCount, WhenCreatedUTC, ManagedBy)

Tip: if you haven't tried the "tagging" function of the SharePoint Stream Migration Tool yet, it works really well! It gives a nice visual on the tags and helps be able to filter your containers whether you're working from the Scans tab or the Migrations tab.

https://learn.microsoft.com/en-us/stream/streamnew/understand-the-tool#tags
https://learn.microsoft.com/en-us/sharepointmigration/mm-tagging

Tip: In my work with the Stream Migration, I've now run into issues with one Container that had a Pipe symbol in its name, and another with double quotes in its name. So if you're just getting started on all this, you might want to review all your Container names for things like that and consider changing them to eliminate headaches later, or be prepared to carefully scrutinize any import or export files you may use.

Here's my summary rewrite on how to work with the Destination Mapping.

To Download the Destination Mapping Template:
-Launch the Stream Migration Tool from Admin Center (Admin Center > Setup > Migrations > Mirosoft Stream)
-Select some containers you want to work with and scan them
-Once Scans are complete for each container, select them again and "Add to Migrations"
-Click the Migrations tab
-Once on the Migrations tab, click the "Upload Destinations" button
-On the popup\dialog box for Destination uploading, there's a link for "MigrationDestinations (.CSV)"
-Click that link, to download a CSV file that will list only the containers you've loaded into the Migrations Tab
-That MigrationDestinations.csv file has the following headers: Name (for reference only), Source Path (for reference only), Destination Path, Migration status (for reference only), Created on (for reference only), Task ID

To edit the Destination Mapping File
-Open in Excel or text editor and make changes to the Destination Path column only.

To upload a Destination Mapping File after editing:  
-From the Migrations tab, click the "Upload Destinations" button
-On the popup\dialog box for Destination uploading, Specify the CSV file containing the altered Destination Paths