Manual App Registration for Teams and Channel Migration

This manual-registration page is for EdbMails migration of Teams document libraries, channels and channel messages. The destination is the corresponding Team sites in the Target tenant.

Register EdbMails Teams and Channel Migration Source in the Source tenant to read Teams, channel, site and file information. Register EdbMails Teams and Channel Migration Target in the destination tenant with the permissions needed to create Teams and channels and write migrated data.

Use the Microsoft Entra ID App Creation Guide for the shared Microsoft Entra portal actions. This page supplies the Teams-and-Channel-specific application names and the exact Source and Target permission sets.

Quick configuration summary

Before you configure the Teams and Channel apps

• Confirm the Source tenant that contains the Teams data and the Target tenant where the Team sites will be created or used.
• Use separate app registrations for the Teams and Channel Source and Target connections.
• Keep the Source Client ID, Tenant ID and Client Secret Value with the Source app; store the Target credentials with the Target app.
• Use the eight-permission Source list only for the Source app and the eleven-permission Target list only for the Target app.
• After each Teams and Channel permission set is complete, grant admin consent in that app tenant.

Steps to manually register an app for SharePoint Migration

Click the Source Teams and Channel app or Target Teams and Channel app accordion below based on the tenant you are configuring.

1. Source Teams and Channel app

   1. Create the Source Teams and Channel app

   Create the application in the Source tenant. Enter the application name as EdbMails Teams and Channel Migration Source.

   Click here to know the steps to create the app in Microsoft Entra ID.

   2. Create the Source client secret

   Create a client secret for EdbMails Teams and Channel Migration Source. Copy the Client Secret Value when it is displayed and keep it with the Source application details.

   Click here to know the steps to create a client secret.

   3. Add Source Teams and Channel permissions

   Set all these permissions in the EdbMails Teams and Channel Migration Source app.

   API: Microsoft GraphPermission type: Application permissions

   • Calendars.Read
   • Channel.ReadBasic.All
   • ChannelMessage.Read.All
   • ChannelSettings.Read.All
   • Files.Read.All
   • Group.Read.All
   • Sites.Read.All
   • Tasks.Read.All
   • User.Read.All

   After adding all eight Teams and Channel Source permissions, grant admin consent in the Source tenant.

   Click here to know steps to add Application permissions and grant admin consent.

2. Target Teams and Channel app

   1. Create the Target Teams and Channel app

   Create the application in the Target tenant. Enter the application name as EdbMails Teams and Channel Migration Target.

   Click here to know the steps to create the app in Microsoft Entra ID.

   2. Create the Target client secret

   Create a separate client secret for EdbMails Teams and Channel Migration Target. Copy and securely store its Client Secret Value.

   Click here to know the steps to create a client secret.

   3. Add Target Teams and Channel permissions

   Set all these permissions in the EdbMails Teams and Channel Migration Target app.

   API: Microsoft GraphPermission type: Application permissions

   • Calendars.ReadWrite
   • Channel.Create
   • ChannelSettings.ReadWrite.All
   • Files.ReadWrite.All
   • Group.Read.All
   • GroupMember.ReadWrite.All
   • Sites.Read.All
   • Tasks.ReadWrite.All
   • TeamsTab.Create
   • Teamwork.Migrate.All
   • User.Read.All

   After all eleven permissions are selected, grant admin consent for the Target tenant.

   Click here to know steps to add Application permissions and grant admin consent.

Why the Source and Target Teams permissions are different

The Source app reads information about Teams, members, channels, channel settings, channel messages, sites and files. The Target app also requires permissions that support creating Teams and channels and writing migrated content. Keep the two permission sets separate so the Source connection is not configured with unnecessary Target permissions and the Target app has the permissions needed for the migration.

1. Connect the Teams tenants in EdbMails

   Source connection

   When connecting the Source tenant in EdbMails for Teams and Channel migration, use the credentials created for EdbMails Teams and Channel Migration Source. Keep the Source Application (Client) ID, Directory (Tenant) ID and Client Secret Value ready.

   Target connection

   When connecting the Target tenant, use the credentials created for EdbMails Teams and Channel Migration Target. The Client ID, Tenant ID and Client Secret Value must all belong to the Target app in the Target tenant.

   Keep the credentials matched: Do not combine a Source Client ID with a Target Tenant ID or Target Client Secret Value.

   After the Source and Target connections are configured, continue with the EdbMails Microsoft Teams Migration Guide for site selection, mapping and migration.

Verify the Teams and Channel app registration before connecting EdbMails

• EdbMails Teams and Channel Migration Source is registered in the Source tenant.
• The Source registration contains all eight Microsoft Graph Application permissions listed in the Source section, including the channel-message read permission.
• EdbMails Teams and Channel Migration Target is registered in the Target tenant.
• The Target registration contains all eleven Microsoft Graph Application permissions listed in the Target section, including the Team and Channel creation permissions.
• Admin consent is granted in both tenants after each Teams permission set is complete.
• For each EdbMails connection, the Client ID, Tenant ID and Client Secret Value come from the same Teams and Channel app.

1. Troubleshooting manual app registration

   1. EdbMails cannot authenticate the Teams connection

      If the Teams and Channel connection does not authenticate, first verify whether you are connecting the Source or Target tenant. Then match the Client ID, Tenant ID and Client Secret Value to that exact Teams and Channel app and confirm its Microsoft Graph Application permissions have admin consent.

   2. The Target app cannot create Teams or channels

      Compare the Target app with the eleven permissions listed above. In particular, verify that Team.Create, Channel.Create and the other Target permissions are present and have admin consent.

   3. Channel messages are not available from the Source

      Verify that ChannelMessage.Read.All is configured under Microsoft Graph > Application permissions for the Source app and that admin consent has been granted.

   4. I copied the Client Secret ID instead of the Client Secret Value

      Use the Client Secret Value from the relevant Teams and Channel app. If Microsoft Entra ID no longer displays the Value, create a new client secret for that app and copy the new Value when it appears.

1. Frequently asked questions

   1. What does this Teams and Channel manual-registration page cover?

      It covers the Source and Target app registration requirements for Teams document libraries, channels and channel messages. The destination is Team sites in the Target tenant.

   2. Are the permissions on this page Application or Delegated permissions?

      For this Teams document library, channel and channel-message configuration, add the listed permissions as Microsoft Graph Application permissions.

   3. Do the Source and Target Teams apps use the same permissions?

      No. The Source app uses the eight permissions required for reading the migration scope, while the Target app uses the eleven permissions listed for creating or writing the destination content.

   4. Does this permission set also cover private and group chats?

      No. Use the separate Private and Group Chat manual app registration page for private (1:1) and group chat migration.

   5. Why is Teamwork.Migrate.All included in the Target permission list?

      It is part of the EdbMails Target permission set for the Teams and Channel migration scenario documented on this page.

   6. Where do I create the Teams Source and Target apps?

      Follow the registration steps in the Microsoft Entra ID App Creation Guide. When naming and configuring each app, use the Teams and Channel Source or Target values shown on this page.

   7. Can I use these Teams permissions for SharePoint or OneDrive migration?

      No. Use the dedicated SharePoint or OneDrive manual-registration page for those workloads.

---

Additional resources

• Open the Microsoft Entra ID App Creation Guide
• Explore EdbMails Microsoft Teams Migration
• Read the Microsoft Teams Migration Guide