Skip to main content
Back to Search AI connectors list Microsoft Teams (MS Teams) is a collaboration and communication platform used in remote and hybrid work environments. Search AI ingests content from MS Teams channels, making conversations easily searchable.

​
Connector Specifications

​
Prerequisites

  • Azure account with Admin rights

​
Register an Application

Search AI interacts with MS Teams through its APIs. You must register Search AI as an OAuth app in Microsoft Entra ID to enable this communication.
  1. Sign in to the Microsoft Entra Admin Center.
  2. Navigate to App registrations and click New Registration.
  3. Enter a Name and choose an appropriate Supported account type.
  4. Enter the Redirect URI that matches your region and deployment:
    • JP Region: https://jp-bots-idp.kore.ai/workflows/callback
    • DE Region: https://de-bots-idp.kore.ai/workflows/callback
    • Prod: https://idp.kore.com/workflows/callback
  5. Click Register to create the app. A client ID is generated.
  6. Go to Certificates & secrets and click New Client Secret.
  7. Copy the client ID, client secret, and tenant ID for use in Search AI.

​
Configure the MS Teams Connector in Search AI

Go to the Connectors home page in Search AI. Click Add Connector and select MS Teams. Provide the following details under the Authorization tab and click Connect.
To access channel conversations, Search AI requires the following Microsoft Graph permissions: Group.Read.All, Team.ReadBasic.All, ChannelMessage.Read.All, offline_access, Channel.ReadBasic.All, ChannelMember.Read.All, TeamMember.Read.All, User.Read.All.

​
Content Ingestion

After connecting the connector, go to the Configuration tab to set up content synchronization. Use Sync Now for an immediate sync, or Schedule Sync to configure a recurring schedule. Search AI ingests conversations from MS Teams channels for the past 90 days. Messages are ingested as follows:
  • Thread messages: Messages in a thread are concatenated during ingestion to preserve conversation context and maintain dialogue flow.
  • Direct messages: Two or more consecutive messages in a channel may be concatenated based on similarity score, retaining relevant context. A maximum of three consecutive messages can be concatenated.
Each ingested item’s content field includes the message timestamp, author, channel name, and message text. If the message has an attachment, the attachment’s name and URL are also captured. Example content field:
Reactions and mentions are captured as metadata. When two or more messages are concatenated, the URL links to the first message. To view ingested content, go to the Content tab.

​
RACL Support

Search AI automatically resolves permission entities for chat messages ingested from different channel types, using the team ID or channel ID based on the channel’s access model.