Teams Migration – Migrate GCC High Tenants

Migrating to or from a GCC High tenant requires a specialized command to allow MigrationWiz to connect. Failing to use these options will result in login errors.

  • Due to Microsoft limitations, private channels are not migrated for GCC High Tenants.
  • Conversation History will not be migrated to a tab in the destination. Instead, a message will be posted in the channel with a link to the conversation history HTML file.
  • Due to limitations in the Microsoft system, images will not be migrated as part of the conversation(s). They will still appear in the conversation history HTML file.

Support Options

In the Advanced Options of the project, under Support Options, add one or both of the commands below, depending on the specific migration scenario:

If migrating from a U.S. Government Tenant, add: OneDriveProExportEnvironment=AzureUSGovernment 

If migrating to a U.S. Government Tenant, add: OneDriveProImportEnvironment=AzureUSGovernment 

 

Advanced Permissions

Admin Permissions

When performing a Teams migration, the Admin account must be either a Teams or Global Administrator in order to complete the migration.

As U.S. Government Tenant does not natively support Application Permissions, to make sure that the migrating accounts are Global Admin, add: UseDelegatePermission=1This is also required to use the following advanced options.

App Based Permissions

For a successful migration, authorize the use of our delegate permission app on Microsoft. The steps for doing this are outlined in Using App-based Authentication. However, it is important to note that you must use the "For Teams Government" link for your migration, otherwise the migration will fail.

If application permissions can only be used at the source or the destination, use the following advanced options as applicable:

Source: UseApplicationPermissionAtSource=1

Destination: UseApplicationPermissionAtDestination=1

For example, to use the Application Permission on the source, and the Delegate Permission at the destination, you would enter UseApplicationPermissionAtSource=1 and UseDelegatePermission=1.

 

 

Was this article helpful?
1 out of 1 found this helpful