Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Migration Current - User Guide

About On Demand Migration Before You Start Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Microsoft 365 Groups Migration Troubleshooting Finalizing the Migration

Teams migration from a Commercial tenant to a GCC High tenant

The table below lists the content types in Microsoft Teams that are available for migration from a Commercial tenant to a GCC High tenant with the On Demand Migration for Teams service.

Content type Available in
GCC High
Supported by
On Demand Migration
Team owners and team members (Creation of Microsoft 365 Groups)
Public channels
Private channels
Conversations
Associated SharePoint document libraries (files)
Team picture
Timestamps
Custom tags for teams
Guest accounts and conversations
Planner (including Planner tab app)
Custom website tab
OneNote
Chats
Applications
Wiki sections and pages
Bots  
Applications including shifts for schedule management
Calendars
Group mailbox associated with team
Formatted text
Authorship
Link preview of public sites
Mentions
  • Users
  • Channels
  • Teams
Images posted inline from buffer
Emoji, Teams GIFs, memes
Link preview of public images
Attached images, media files, documents
Email attachments
Code snippets
Meeting conversations
Announcements

 

Prerequisites

Verify the following requirements are met before migrating Microsoft Teams. If these actions are not performed, discovery, provision and migration tasks will fail or some data might be lost!

  • Consents are already granted for source and target tenants.
    The following consents should be granted before Teams migration feature can be used
    • Migration - Basic,
    • Migration - Mailbox Migration
    • Migration - SharePoint,
    • Migration - Teams.

TIP: If the admin consents are not granted or expired, Discover Teams action is disabled and the following notification is displayed: Grant admin consent to the following Migration sub modules on the Tenants page for both source and target tenants: Basic, SharePoint, and Teams. Open Tenants page and grant the necessary Required Consents and Permissions so that the product can access the source and target tenants. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is granted, you can start discovering Teams. On Demand for Migration uses the global administrator account to grant consent because the ‘admin consent flow’ which it uses requires it; read more about the admin consent flow experience.

  • User must be matched or migrated before using the On Demand Migration for Teams service.
  • Images, media files and documents referenced in one-on-one or group chats are stored in your OneDrive for Business folder. They must be migrated using the On Demand Migration for OneDrive service, before you migrate the chats.
  • It is recommended to create or use dedicated (not added as owner or member to any team) source and the target Azure AD administrator accounts.

IMPORTANT: It is not recommended to use existing user accounts as source and target Azure AD administrator accounts, because it is recommended to remove them for safety reasons after the migration will be completed. These accounts can be removed from teams as described in Finalizing the Migration.

  • Azure AD administrator accounts should have Teams license.
  • It is not recommended that you change your Azure AD administrator accounts before completing the migration project.
  • Azure AD administrator accounts should be granted the Global Administrator or Teams Administrator role on the tenants for which these account are used.
  • Azure AD administrator accounts should be granted Application Impersonation role on the tenants for which these account are used.
  • Accounts joined to existing teams should be matched or migrated in the migration project.

Required permissions

Feature Required permissions
Migrate conversations Read all channel messages
  Have full access to the Chat Service Aggregator
  Have full access to the Skype Teams Service
  Create chat and channel messages with anyone's identity and with any time stamp
Migrate private chats Read all chat messages
  Read and write user chat messages
Provision groups and teams Read and write directory data
  Read and write all groups
Migrate files and OneNote items Read and write all OneNote notebooks
  Read and write items in all site collections
  View and modify notes for all users
Migrate groups and teams membership Read all users' full profiles
  Read or write user region
  Add and remove members from all teams
  Add and remove members from all channels

 

Azure AD administrator accounts

It is strongly recommended to create dedicated accounts as the source and target Azure AD administrator accounts. These accounts should not be an owner or member of any team. For security reasons it is recommended to remove these accounts once the migration is complete.

The target Azure AD administrator account use is in and not limited to the following scenarios:

  • The target Azure AD administrator account that is used to perform Teams provisioning creates and owns these provisioned target teams.
  • The target Azure AD administrator account is added to all target teams and Microsoft 365 Groups as a member and an owner, and to all target private channels as an owner.
  • The target Azure AD administrator account is used to perform the Teams migration and displayed as the owner of all migrated conversation and chat messages and planner tasks on the target.
  • The target Azure AD administrator account is added to all the chats (both group chats and private chats) as a participant during chats migration, and then removed from the migrated chats as soon as the chat migration is complete. All migrated chats of the target Azure AD administrator account are hidden when the chat migration is complete.

Teams Migration Interface Walkthrough

Using this new intuitive interface you can:

  • Keep track of your location within project and quickly return to the main project dashboard using breadcrumbs on the top of the pane
  • View list of discovered teams with last information, completed workflows, team information, and last events related to the teams
  • Switch to assessment view to track potential problems, misconfiguration, and risks that might adversely affect the migration
  • Quickly navigate to the event lists
  • Quickly navigate to the tasks list
  • Create discovery task, provision tasks, and teams migration tasks
  • Organize the teams into collections that act as “projects within project”. The collections allow you to structure teams.
  • Export feature data into comma-separated file and use this file for manual mapping
  • Search teams
  • Filter teams by workflow, team state or size
  • Select a team to view details on the right pane. See this pane for extended details related to the selected object .

Assessment View for Microsoft Teams

See the Pre-Migration Assessment for Teams for the complete list of available reports.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation