Microsoft Teams support

Last updated date:

Connect, reconnect, and troubleshoot Microsoft Teams without sharing credentials or customer content through support channels.

1. Before you start

  • Select exact teams and channels; do not infer selection from the current user.
  • On the Microsoft 365 connection, select teams and grant the team, channel, membership, and channel-message Microsoft Graph Application read roles without adding chat or write access.
  • Have the Teams and licensing administrators confirm that the selected tenant/users are eligible for the enabled export APIs. Private and group chats are outside V1.
  • Do not send Microsoft Teams credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Microsoft Graph permissionsMicrosoft's Graph permissions reference.

2. Connect Microsoft Teams

  1. Start with the Microsoft 365 connection in the intended Seedling workspace. If it is unavailable, contact Seedling support before creating credentials.
  2. Verify the immutable Entra tenant ID and tenant admin consent for the exact application-role bundle.
  3. In the Teams work or school client, open the team's More options menu, choose Get link to team, and copy only the UUID after groupId= from the link.
  4. Add that backing-group UUID as the exact team source. Do not enter a channel, chat, meeting, tenant, display name, or full URL.
  5. Add each Microsoft Teams source separately and confirm Seedling accepts the exact Microsoft ID before synchronization.

3. Authorization and connection problems

Setup unavailable
Microsoft 365 or Teams is not available for this Seedling workspace. Contact Seedling support; delegated access is not a fallback.
Chat unavailable
Teams private and group chats are intentionally unsupported in V1.

4. Missing or delayed data

  1. Verify the team and channel were explicitly selected.
  2. Review application roles, licensing, channel type, retention, and provider warnings.
  3. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  4. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Rotate the exact Entra application credential without changing the immutable tenant or application identity.
  2. Retain only the approved team, channel, membership, directory, and channel-message roles.
  3. Verify the replacement certificate and the same selected sources before retiring the previous credential.