In this article, we will review connection account requirements for the MS Planner -> MS Planner migration scenario.
Planner source account
The connection account for migration from Planner (source account) should meet the following requirements:
- The account should have access to all necessary existing Microsoft 365 groups, Planner Plans, and users.
- The account should be added as a member to the public and private groups and Plans that need to be migrated (only these groups and Plans will be available to select for the migration).
To connect to Microsoft Planner for the first time, tenant Global Administrator consent is required to allow Project Migrator to access your Microsoft 365 tenant.
Admin consent should be granted only once before adding the first Planner connection account. Once the consent is granted, any user account credentials without admin permissions can be used for connecting to Planner.
Project Migrator application for Planner migrations will be added to the Microsoft 365 tenant. For Project Migrator to transfer data using Microsoft Graph API, the administrator must grant the app the correct permissions via a consent process.
The following Microsoft Graph API permissions are required:
For the source Planner migration account:
- Group.Read.All
- User.ReadBasic.All
- Directory.Read.All
Project Migrator will have the following permissions for reading data from Microsoft Planner:
- Read data from existing Microsoft 365 groups such as basic information, email addresses, membership
- Read data from existing Plans in Microsoft Planner
- Read sites of Microsoft 365 groups, linked to Planner Plans (required for file attachments migration).
Planner target account
The connection account for migration to Planner (target account) should meet the following requirements:
- The account should have access to all necessary existing Microsoft 365 groups, Planner Plans, and users.
- If the migration is performed to existing Microsoft 365 groups and Plans, the account should be added as a member or an owner to those groups. The account should be a member and an owner of the existing target Private groups.
- The target Planner migration account should have an Exchange Online license to be able to add task Comments (if the source Plan tasks have Comments to migrate).
To connect to Microsoft Planner for the first time, tenant Global Administrator consent is required to allow Project Migrator to access your Microsoft 365 tenant.
Admin consent should be granted only once before adding the first Planner connection account. Once the consent is granted, any user account credentials without admin permissions can be used for connecting to Planner.
Project Migrator application for Planner migrations will be added to the Microsoft 365 tenant. For Project Migrator to transfer data using Microsoft Graph API, the administrator must grant the app the correct permissions via a consent process.
For the target Planner migration account:
- Group.ReadWrite.All
- Directory.Read.All
- Sites.ReadWrite.All
- User.ReadBasic.All
Project Migrator will have the following permissions for data migration to Microsoft Planner:
- Read permissions as required for the source migration account
- Create new Microsoft 365 groups (Write permissions)
- Create new and update existing Plans in Microsoft Planner (Write permissions)
- Read and update sites of Microsoft 365 groups, linked to Planner Plans (Write permissions, required for attachments migration).