Microsoft Teams
Microsoft Teams is an enterprise collaboration tool for messaging, meetings and file sharing. If you are a Microsoft Teams user, you can use Amazon Kendra to index your Microsoft Teams data source.
You can connect Amazon Kendra to your Microsoft Teams data source using the Amazon Kendra console
For troubleshooting your Amazon Kendra Microsoft Teams data source connector, see Troubleshooting data sources.
Supported features
-
Field mappings
-
User context filtering
-
Inclusion/exclusion filters
-
Virtual private cloud (VPC)
-
Identity crawler
-
Sync all documents/Sync only new, modified, or deleted documents
Prerequisites
Before you can use Amazon Kendra to index your Microsoft Teams data source, make these changes in your Microsoft Teams and AWS accounts.
In Microsoft Teams, make sure you have:
-
Created a Microsoft Teams account in Office 365.
-
Copied your Microsoft 365 tenant ID. You can find your tenant ID in the Properties of your Azure Active Directory Portal.
-
Configured an OAuth 2.0 credential token containing a client ID and client secret.
-
Added the necessary permissions. You can choose to add all permissions, or you can limit the scope by selecting fewer permissions based on which entities you'd like to be crawled. Below is the table of permissions by corresponding entity:
Entity Required Permissions for Data Sync Required Permissions for Identity Sync Channel Post -
ChannelMessage.Read.All
-
Group.Read.All
-
User.Read
-
User.Read.All
TeamMember.Read.All Channel Attachment -
ChannelMessage.Read.All
-
Group.Read.All
-
User.Read
-
User.Read.All
TeamMember.Read.All Channel Attachment -
ChannelMessage.Read.All
-
Group.Read.All
-
User.Read
-
User.Read.All
TeamMember.Read.All Channel Wiki -
Group.Read.All
-
User.Read
-
User.Read.All
TeamMember.Read.All Chat Message -
Chat.Read.All
-
ChatMessage.Read.All
-
ChatMember.Read.All
-
User.Read
-
User.Read.All
-
Group.Read.All
TeamMember.Read.All Meeting Chat -
Chat.Read.All
-
ChatMessage.Read
-
ChatMember.Read.All
-
User.Read
-
User.Read.All
-
Group.Read.All
TeamMember.Read.All Chat Attachment -
Chat.Read.All
-
ChatMessage.Read
-
ChatMember.Read.All
-
User.Read
-
User.Read.All
-
Group.Read.All
TeamMember.Read.All Meeting File -
Chat.Read.All
-
ChatMessage.Read.All
-
ChatMember.Read.All
-
User.Read
-
User.Read.All
-
Group.Read.All
-
Files.Read.All
TeamMember.Read.All Calendar Meeting -
Chat.Read.All
-
ChatMessage.Read.All
-
ChatMember.Read.All
-
User.Read
-
User.Read.All
-
Group.Read.All
-
Files.Read.All
TeamMember.Read.All Meeting Notes -
User.Read
-
User.Read.All
-
Group.Read.All
-
Files.Read.All
TeamMember.Read.All -
-
Checked each document is unique in Microsoft Teams and across other data sources you plan to use for the same index. Each data source that you want to use for an index must not contain the same document across the data sources. Document IDs are global to an index and must be unique per index.
In your AWS account, make sure you have:
-
Created an Amazon Kendra index and, if using the API, noted the index ID.
-
Created an IAM role for your data source and, if using the API, noted the ARN of the IAM role.
-
Stored your Microsoft Teams authentication credentials in an AWS Secrets Manager secret and, if using the API, noted the ARN of the secret.
Note Be sure to regularly refresh or rotate your credentials and secret. Provide only the necessary access level for your own security.
If you don’t have an existing IAM role or secret, you can use the console to create a new IAM role and Secrets Manager secret when you connect your Microsoft Teams data source to Amazon Kendra. If you are using the API, you must provide the ARN of an existing IAM role and Secrets Manager secret, and an index ID.
Connection instructions
To connect Amazon Kendra to your Microsoft Teams data source, you must provide the necessary details of your Microsoft Teams data source so that Amazon Kendra can access your data. If you have not yet configured Microsoft Teams for Amazon Kendra see Prerequisites.