New-MgMigrationPlan -Directory “” -UpdatedFilePath “Path to new generated script” Scenario 4: Identify changes on a script(s) in a directory and generate a new v2 compliant script (s) in a new directory. In this scenario, the toolkit provides the user an option of generating a new script with the new suggested changes to the provided path. New-MgMigrationPlan -FilePath “” -UpdatedFilePath “Path to new generated script” Scenario 3: Identify changes on a script and generate a new v2 compliant script. This will subject the whole script to the naming convention of commands as per expectations with PowerShell v2 Scenario 2: Identify changes on a script to utilize one endpoint (either beta or V1) using -GraphProfile In the example below all commands under “Select-MgProfile -Name ‘beta’” will have commands updated with the Beta prefix. Scenario 1: Identify changes on your script that has both profiles (v1 & Beta profiles)

The “Location” column shows the script name and the line number while the “Original” and “After” columns show the current commands and the new suggested commands respectively. For all the scenarios, the output from the toolkit will give you suggestions on where to change your script. The Migration Toolkit has various capabilities depending on the arguments provided. To aid users in updating from Microsoft Graph PowerShell v1 to v2 we have a Migration Toolkit that identifies and resolves breaking changes. Microsoft Graph PowerShell v2 introduces changes that will require v1 users to change their scripts to address issues like naming conventions of command names if their scripts include directives for switching to beta profile.

Psn username booter