Documentation

For a general introduction to the connector, please refer to RheinInsights Microsoft Teams Search and RAG Connector.

Entra Id Configuration

Application Registration

The connector acts as an Entra Id application. This application must be registered as follows

1. Navigate to https://portal.azure.com

2. Open Entra Id

3. Open App registrations

   

4. Click on New registration

   

5. Give it a name

   

6. Click on Register

7. Click on API permissions

   

8. Add a Permission

9. Click on Microsoft Graph

   

10. Choose Application Permissions

    

11. Please search for the following permissions and check the respective boxes:

    1. Channel.ReadBasic.All

    2. ChannelMember.Read.All

    3. ChannelMessage.Read.All

    4. Chat.ManageDeletion.All

    5. Chat.Read.All

    6. Chat.ReadBasic.All

    7. Directory.Read.All

    8. TeamMember.Read.All

    9. User.Read

12. Click on Add permissions

    

13. Grant the consent

14. Got to certificates and secrets

15. Generate a new Client Secret

    

16. Give it a name and an expiration date

17. Create the secret

18. Then make a note of the value

    

19. Click on Overview and make a note of client Id and tenant Id

    

Content Source Configuration

The content source configuration of the connector comprises the following mandatory configuration fields.

Within the connector’s configuration please add the following information:

1. Tenant Id. Is the tenant Id information from Step 19 above.

2. Client Id. Is the client Id information from Step 19 above.

3. Client secret is the client secret from Step 18 above.

4. Include archived channels from crawling. If checked, only active channels and teams are indexed.
   This does not apply to 1:1 messages which have been removed from their history by the user(s).

5. Maximum age for documents (in days). This determines if messages should be dropped in incremental crawls, if they exceed the specified age in days. If everything should be indexed, then please add -1.

6. Include 1:1 chat messages into crawling. If enabled, also personal messages between users are indexed.

7. Rate limit: You can specify the number of API calls per second.

8. Included teams. Here you can add team ids or team names as Java regular expressions. If given, only these teams and their channels will be crawled. All previously indexed teams which are not included anymore will be deleted from the search index.

9. Excluded teams. Here you can add team ids or team names as Java regular expressions. If given, these sites will be not be crawled. Then all previously indexed teams which are not included anymore will be deleted from the search index.

10. Included private chat messages. Here you can add user names or mail addresses as Java regular expressions. If given, only 1:1 messages where this user participates, are indexed.

11. Excluded private chat messages. Here you can add user names or mail addresses as Java regular expressions. If given, 1:1 messages where this user participates, are not indexed.

After entering the configuration parameters, click on validate. This validates the content crawl configuration directly against the content source. If there are issues when connecting, the validator will indicate these on the page. Otherwise, you can save the configuration and continue with Content Transformation configuration.

Recommended Crawl Schedules

Content Crawls

The connector supports incremental crawls. These are based on the information the Teams API provides. This includes also deletions.

The change log might not be complete and factor in all permission changes (for instance, if a channel is switched from public to private). Therefore depending on your requirements, we recommend to run a Full Scan every week.

For more information see Crawl Scheduling .

Principal Crawls

Depending on your requirements, we recommend to run a Full Principal Scan every day or less often.

For more information see Crawl Scheduling .