Azure AD Administrative Accounts
It is strongly recommended to create dedicated accounts as the source and target Azure AD administrative 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 administrative account use is in and not limited to the following scenarios:
- The target Azure AD administrative account that is used to perform Teams provisioning creates and owns these provisioned target teams.
- The target Azure AD administrative account is added to all target teams and Office 365 Groups as a member and an owner, and to all target private channels as an owner.
- The target Azure AD administrative 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 administrative 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 administrative account are hidden when the chat migration is complete.
Before proceeding with the migration, retrieve the list of teams and Microsoft Office 365 groups from the source tenant.
Caution: Don’t start the migration before the discovery is finished. It might result in incorrect processing of migrated objects.
- Go to the main migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the Teams migration Dashboard, go to step 3.
- Click Teams widget.
- Click Discover on the dashboard to create a new discovery task.
- Select objects to discover:
- All Office 365 Groups and Teams ( select this option to discover all Office 365 Groups including groups without Teams functionality)
- All Teams and associated Office 365 Groups
- Office 365 Groups without Teams functionality only
- Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
- Check scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.
TIP: Give informative names for the tasks. It will greatly simplify the project management and event filtering in the future.
- Click Finish. You can monitor the task status using task widget on project dashboard.
- Click the task name on the widget to see the details or use Show all link.
Once the discovery task is complete, you will see the source tenant’s teams summary on the Microsoft Teams Migration Project Dashboard.
Discovery also checks the target tenant for potential conflicts (the identical team names on the source and target tenants.) The conflicting teams are marked with "Target team exists" in the Teams list. To see all conflicts, click Needs your attention on the left.
The conflicts are resolved during the provisioning.
Using Collections for Teams
You can use collections to streamline the provision and migration process. There are two approaches:
- You can select discovered teams and create a new collection for them
- You can create a new empty collection and then populate it with discovered teams using comma-separated CSV file.
To create a new collection based on selected teams:
- Click Teams on necessary migration project
- Select teams you want to combine into the collection. You can use search for filtering out the teams by certain criteria or simply hand-pick the individual teams from the grid.
- Click +New Collection in the top right corner of the list view and enter the informative collection name. Click Save to add this collection to the project.
To create a new empty collection and then populate it with teams:
- On the dashboard click Add To Collection.
- Enter the informative collection name. Click Save to add this collection to the project.
- Populate it using comma-separated values (CSV) file as specified in Populating Collections.
You can populate any existing collection using a comma-separated values (CSV) file with team attributes.
- CSV file can contain one or more columns. There are no special requirements for header names.
- One of column must contain case sensitive mail nickname data that will be used for matching.
- File names with non-ASCII characters are not supported.
To populate collection from CSV file
- Prepare a comma-separated values (CSV) file with data of discovered teams you want to add to the collection. File can contain teams that have not been discovered, but these teams won't be added to the collection. One of the columns should contain the mail nicknames. For example:
- Select a collection you want to populate on Dashboard and click it to open the Collection Dashboard.
- Click Fill from File to populate the collection with discovered objects you specified in the file created on Step 1.
- Click Browse to open the comma-separated CSV file created on Step 1.
- Browse for file and click Open. Selected file name appears next to the Browse button.
- Click Populate to populate the collection.
The collection is populated. You can see added objects on the Collection Dashboard.
NOTE: The objects that do not exist in the source and/or target tenants and the source teams that are not enumerated during the Discovery are ignored without producing an event.