Manual App Registration for Private and Group Chat Migration

Use this page for manual app registration when EdbMails is migrating Private (1:1) and Group Chats between Microsoft 365 users. The Source and Target are user-based Microsoft 365 connections, so this configuration is separate from the Teams and Channel migration setup.

Create EdbMails Groups and Teams Chat Migration Source to read the Source chat information and EdbMails Groups and Teams Chat Migration Target to create and write the destination chat data. Each app has its own Microsoft Graph Application permission list.

Complete the shared Entra registration actions with the Microsoft Entra ID App Creation Guide. Use the app names and chat-specific Source or Target permissions on this page when configuring the two registrations.

Quick configuration summary

Before you configure the Private and Group Chat apps

• Confirm the Microsoft 365 tenant that contains the Source users and the tenant that contains the Target users.
• Create the chat Source app and chat Target app as separate registrations in their corresponding tenants.
• Keep the Source chat Client ID, Tenant ID and Client Secret Value together, and keep the Target chat credentials separately.
• Apply only the eight Source chat permissions to the Source app and only the six Target chat permissions to the Target app.
• Grant admin consent in the appropriate tenant after the full Private and Group Chat permission set has been added.

Steps to manually register an app for SharePoint Migration

Click the Source Source Private and Group Chat app or Target Private and Group Chat app accordion below based on the tenant you are configuring.

1. Source Private and Group Chat app

   1. Create the Source Chat Migration app

   Create the application in the Source tenant. Enter the application name as EdbMails Groups and Teams Chat 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 Groups and Teams Chat 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 Private and Group Chat permissions

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

   API: Microsoft GraphPermission type: Application permissions

   • Calendars.Read
   • Chat.Read.All
   • ChatMember.Read.All
   • ChatMessage.Read.All
   • Files.Read.All
   • Group.Read.All
   • GroupMember.Read.All
   • Tasks.Read.All
   • TeamsTab.Read.All
   • User.Read.All

   After adding the eight Private and Group Chat Source permissions, grant admin consent in the Source tenant.

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

2. Target Private and Group Chat app

   1. Create the Target Chat Migration app

   Create the application in the Target tenant. Enter the application name as EdbMails Groups and Teams Chat 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 Groups and Teams Chat Migration Target. Copy and securely store its Client Secret Value.

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

   3. Add Target Private and Group Chat permissions

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

   API: Microsoft GraphPermission type: Application permissions

   • Calendars.ReadWrite
   • Chat.Create
   • Chat.Read.All
   • ChatMember.ReadWrite.All
   • Files.ReadWrite.All
   • Tasks.ReadWrite.All
   • TeamsTab.Create
   • Teamwork.Migrate.All
   • User.Read.All

   After all six 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 chat permission lists are different

The Source app reads the private and group chat data selected for migration, including chat messages, chat membership, related group and user information, files and calendar data. The Target app requires the permissions needed to create the destination chat structure and write the migrated data. Configure each list only in its corresponding Source or Target application.

1. Connect Private and Group Chat in EdbMails

   Source connection

   When connecting the Source tenant for Private and Group Chat Migration, use the credentials created for EdbMails Groups and Teams Chat 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 Groups and Teams Chat 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 Source app credentials with Target app credentials when connecting the Microsoft 365 users in EdbMails.

   After the Source and Target connections are configured, continue with the EdbMails Microsoft Teams Private and Group Chat Migration Guide for the complete migration workflow.

Verify the Private and Group Chat app registration before connecting EdbMails

• EdbMails Groups and Teams Chat Migration Source is registered in the tenant containing the Source users.
• The Source registration has all eight chat-migration Microsoft Graph Application permissions listed in the Source section.
• EdbMails Groups and Teams Chat Migration Target is registered in the tenant containing the Target users.
• The Target registration has all six Microsoft Graph Application permissions listed for Private and Group Chat migration.
• Admin consent is granted for each completed chat permission set in its corresponding tenant.
• The credentials supplied for each user-side connection come from the matching Source or Target chat migration app.

1. Troubleshooting manual app registration

   1. EdbMails cannot authenticate the chat migration connection

      For a Private or Group Chat connection, verify that you selected credentials from the chat app registered in that user's Source or Target tenant. The Client ID, Tenant ID and Client Secret Value must belong to the same chat registration, and its complete permission set must have admin consent.

   2. Private or group chats are not available from the Source

      Compare the Source app with all eight permissions listed above. Verify that ChatMessage.Read.All are configured under Microsoft Graph > Application permissions and have admin consent.

   3. The Target app is missing a required chat migration permission

      Compare the Target app with all six permissions on this page. Verify that Chat.Create, Teamwork.Migrate.All, Files.ReadWrite.All and the remaining Target permissions are present and have admin consent.

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

      Enter the Client Secret Value for the chat migration app, not its Secret ID. If the Value is no longer shown, create a replacement client secret in that Source or Target chat app and copy the displayed Value.

1. Frequently asked questions

   1. What does this manual-registration page cover?

      It covers Microsoft Entra ID app registration for EdbMails Private (1:1) and Group Chat Migration between Microsoft 365 users.

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

      The Private and Group Chat Source and Target lists on this page are configured as Microsoft Graph Application permissions.

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

      No. The Source chat app uses the eight permissions shown in the Source section, while the Target chat app uses the six permissions shown for the destination.

   4. Are the Source and Target both Microsoft 365 users?

      Yes. The migration scenario documented on this page uses Microsoft 365 users as both the Source and Target.

   5. Does this permission set also cover Teams channels and channel messages?

      No. Use the separate Teams and Channel manual app registration page for Teams document libraries, channels and channel messages.

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

      Use the Microsoft Entra ID App Creation Guide for the common registration procedure. Enter the exact chat Source or Target app name from this page and apply its corresponding permission list.

   7. Where do I continue after app registration?

      Continue with the EdbMails Microsoft Teams Private and Group Chat Migration Guide for the complete chat migration workflow.

---

Additional resources

• Microsoft Entra ID App Creation Guide
• Explore EdbMails Microsoft Teams Migration
• Read the Private and Group Chat Migration Guide