Microsoft.Graph.Beta.Migrations Module

Microsoft Graph PowerShell Cmdlets

Microsoft.Graph.Beta.Migrations Cmdlets

Cmdlet Description
Get-MgBetaCrossTenantMigrationJob

Read the properties and relationships of crossTenantMigrationJob object. Includes details of the crossTenantMigrationJob , but not details of the individual crossTenantMigrationTasks of the crossTenantMigrationJob.

Get-MgBetaCrossTenantMigrationJobUser

Read the properties and relationships of crossTenantMigrationTask, which shows the details of the migration task for a single user of a crossTenantMigrationJob. The crossTenantMigrationTask contains the status details of migrations for the workloads specified in the crossTenantMigrationJob.

Move-MgBetaCrossTenantMigrationJob

Migrate a cross-tenant migration job asynchronously. The job must pass validation before migration can start. After a job is created by using the Create crossTenantMigrationJob method and validated by using the validate action, call this action to start the migration of user data from the source tenant to the target tenant for the specified workloads. Validation results expire after seven days; if expired, revalidate the job before you call the migrate API. This action is asynchronous. After you call the migrate API, poll the Get crossTenantMigrationJob endpoint to check for a terminal status of completed, completedWithErrors, or failed.

New-MgBetaCrossTenantMigrationJob

Create a new crossTenantMigrationJob. A job defines the migration batch but doesn't start validation or migration. After you create the job, call validate to verify tenant and resource configuration, then call migrate to begin the actual migration.

Remove-MgBetaCrossTenantMigrationJob

Delete navigation property crossTenantMigrationJobs for solutions

Stop-MgBetaCrossTenantMigrationJob

Cancel a crossTenantMigrationJob. All tasks within the job that were in a Sync state are canceled. If the job can't be canceled, a 409 Conflict response is returned and the migrations continue. This response happens when a migration is already in progress or is in a terminal state.

Stop-MgBetaCrossTenantMigrationJobUser

Cancel a specific crossTenantMigrationTask for a User within a CrossTenantMigrationJob. If the User migration can't be canceled or is in a terminal state, a 409 CONFLICT response code is returned, and the migration continues.

Test-MgBetaCrossTenantMigrationJob

Validate the configuration of a cross-tenant migration job asynchronously. This action doesn't migrate any content, but goes through validation for the specified workloads to find any errors or misconfigurations that affect an actual migration job. The job must be in a submitted or validateFailed status before you can call this action. This action is asynchronous. After you call the validate API, poll the Get crossTenantMigrationJob endpoint to check for a terminal status of validatePassed or validateFailed.

Update-MgBetaCrossTenantMigrationJob

Update the completeAfterDateTime of a crossTenantMigrationJob object. Only updates to the completeAfterDateTime are supported. Use this function to change when the crossTenantMigrationJob starts processing. If completeAfterDateTime is set to the past, the crossTenantMigrationJob starts processing.