Intelligently search your group’s Microsoft Groups knowledge supply with the Amazon Kendra connector for Microsoft Groups

Organizations use messaging platforms like Microsoft Teams to deliver the precise folks collectively to securely talk with one another and collaborate to get work completed. Microsoft Groups captures invaluable organizational information within the type of the knowledge that flows by means of it as customers collaborate. Nevertheless, making this data simply and securely obtainable to customers could be difficult because of the fragmented nature of conversations throughout teams, channels, and chats inside a company. Moreover, the conversational nature of Microsoft Groups communication renders a conventional keyword-based method to look ineffective when looking for correct solutions to questions from the content material and subsequently requires clever search capabilities which have the power to course of pure language queries.

Now you can use the Amazon Kendra connector for Microsoft Groups to index Microsoft Groups messages and paperwork, and search this content material utilizing clever search in Amazon Kendra, powered by machine studying (ML).

This publish exhibits easy methods to configure the Amazon Kendra connector for Microsoft Groups and make the most of the service’s clever search capabilities. We use an instance of an illustrative Microsoft Groups occasion the place customers focus on technical matters associated to AWS.

Resolution overview

Microsoft Groups content material for energetic organizations is dynamic in nature on account of steady collaboration. Microsoft Groups consists of public channels the place any person can take part, and personal channels the place solely these customers who’re members of those channels can talk with one another. Moreover, people can immediately talk with each other in one-on-one and advert hoc teams. This communication is within the type of messages and threads of replies, with non-obligatory doc attachments.

In our answer, we configure Microsoft Groups as a knowledge supply for an Amazon Kendra search index utilizing the Amazon Kendra connector for Microsoft Groups. Primarily based on the configuration, when the info supply is synchronized, the connector crawls and indexes all of the content material from Microsoft Groups that was created on or earlier than a selected date. The connector additionally indexes the Entry Management Listing (ACL) data for every message and doc. When entry management or person context filtering is enabled, the search outcomes of a question made by a person consists of outcomes solely from these paperwork that the person is permitted to learn.

The Amazon Kendra connector for Microsoft Groups can combine with AWS IAM Identity Center (Successor to AWS Single Signal-On). You first should allow IAM Identification Heart and create a company to sync customers and teams out of your energetic listing. The connector will use the person identify and group lookup for the person context of the search queries.

With Amazon Kendra Experience Builder, you’ll be able to construct and deploy a low-code, absolutely useful search software to look your Microsoft Groups knowledge supply.

Stipulations

To check out the Amazon Kendra connector for Microsoft Groups utilizing this publish as a reference, you want the next:

Word that the Microsoft Graph API locations throttling limits on the variety of concurrent calls to a service to forestall overuse of assets.

Configure Microsoft Groups

The next screenshot exhibits our instance Microsoft Groups occasion with pattern content material and the PDF file AWS_Well-Architect_Framework.pdf that we’ll use for our Amazon Kendra search queries.

The next steps describe the configuration of a brand new Amazon Kendra connector software within the Azure portal. This may create a person OAuth token for use in configuring the Amazon Kendra connector for Microsoft Groups.

1. Log in to Azure Portal together with your Microsoft credentials.
2. Register an software with the Microsoft Identity platform.

3. Subsequent to Consumer credentials, select Add a certificates or secret so as to add a brand new consumer secret.

4. For Description, enter an outline (for instance, KendraConnectorSecret).
5. For Expires, select an expiry date (for instance, 6 months).
6. Select Add.

7. Save the key ID and secret worth to make use of later when creating an Amazon Kendra knowledge supply.

8. Select Add a permission.

9. Select Microsoft Graph so as to add all needed Microsoft Graph permissions.

10. Select Software permissions.

The registered software ought to have the next API permissions to permit crawling all entities supported by the Amazon Kendra connector for Microsoft Groups:

• ChannelMessage.Learn.All
• Chat.Learn
• Chat.Learn.All
• Chat.ReadBasic
• Chat.ReadBasic.All
• ChatMessage.Learn.All
• Listing.Learn.All
• Information.Learn.All
• Group.Learn.All
• Mail.Learn
• Mail.ReadBasic
• Person.Learn
• Person.Learn.All
• TeamMember.Learn.All

Nevertheless, you’ll be able to choose a lesser scope based mostly on the entities chosen to be crawled. The next lists are the minimal units of permissions wanted for every entity:

• Channel Put up:
  • ChannelMessage.Learn.All
  • Group.Learn.All
  • Person.Learn
  • Person.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)
• Channel Attachment:
  • ChannelMessage.Learn.All
  • Group.Learn.All
  • Person.Learn
  • Person.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)
• Channel Wiki:
  • Group.Learn.All
  • Person.Learn
  • Person.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)
• Chat Message:
  • Chat.Learn.All
  • ChatMessage.Learn.All
  • ChatMember.Learn.All
  • Person.Learn
  • Person.Learn.All
  • Group.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)
• Assembly Chat:
  • Chat.Learn.All
  • ChatMessage.Learn.All
  • ChatMember.Learn.All
  • Person.Learn
  • Person.Learn.All
  • Group.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)
• Chat Attachment:
  • Chat.Learn.All
  • ChatMessage.Learn.All
  • ChatMember.Learn.All
  • Person.Learn
  • Person.Learn.All
  • Group.Learn.All
  • Information.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)
• Assembly File:
  • Chat.Learn.All
  • ChatMessage.Learn.All
  • ChatMember.Learn.All
  • Person.Learn
  • Person.Learn.All
  • Group.Learn.All
  • Information.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)
• Calendar Assembly:
  • Calendars.Learn
  • Group.Learn.All
  • TeamMember.Learn.All
  • Person.Learn
  • Person.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)
• Assembly Notes:
  • Group.Learn.All
  • Person.Learn
  • Person.Learn.All
  • Information.Learn.All
  • TeamMember.Learn.All (user-group mapping for id crawl)

11. Choose your permissions and select Add permissions.

Configure the info supply utilizing the Amazon Kendra connector for Microsoft Groups

So as to add a knowledge supply to your Amazon Kendra index utilizing the Microsoft Groups connector, you should use an current Amazon Kendra index, or create a new Amazon Kendra index. Then full the steps on this part. For extra data on this matter, consult with Microsoft Teams.

1. On the Amazon Kendra console, open the index and select Knowledge sources within the navigation pane.
2. Select Add knowledge supply.
3. Beneath Microsoft Groups connector, select Add connector.

4. Within the Specify knowledge supply particulars part, enter the main points of your knowledge supply and select Subsequent.
5. Within the Outline entry and safety part, for Tenant ID, enter the Microsoft Groups tenant ID from the Microsoft account dashboard.
6. Beneath Authentication, you’ll be able to both select Create so as to add a brand new secret with the consumer ID and consumer secret of the Microsoft Groups tenant, or use an current AWS Secrets Manager secret that has the consumer ID and consumer secret of the Microsoft Groups tenant that you really want the connector to entry.
7. Select Save.

8. Optionally, select the suitable payment model:
   • Mannequin A cost fashions are restricted to licensing and cost fashions that require safety compliance.
   • Mannequin B cost fashions are appropriate for licensing and cost fashions that don’t require safety compliance.
   • Use Analysis Mode (default) for restricted utilization analysis functions.
9. For IAM function, you’ll be able to select Create a brand new function or select an current IAM function configured with acceptable IAM insurance policies to entry the Secrets and techniques Supervisor secret, Amazon Kendra index, and knowledge supply.
10. Select Subsequent.

11. Within the Configure sync settings part, present data concerning your sync scope.

12. For Sync mode, select your sync mode (for this publish, choose Full sync).

With the Full sync possibility, each time the sync runs, Amazon Kendra will crawl all paperwork and ingest every doc even when ingested earlier. The total refresh lets you reset your Amazon Kendra index with out the necessity to delete and create a brand new knowledge supply. Should you select New or modified content material sync or New, modified, or deleted content material sync, each time the sync job runs, it’ll course of solely objects added, modified, or deleted because the final crawl. Incremental crawls might help cut back runtime and value when used with datasets that append new objects to current knowledge sources frequently.

13. For Sync run schedule, select Run on demand.
14. Select Subsequent.

15. Within the Set discipline mappings part, you’ll be able to optionally configure the sphere mappings, whereby Microsoft Groups discipline names could also be mapped to a distinct Amazon Kendra attribute or side.
16. Select Subsequent.

17. Evaluate your settings and ensure so as to add the info supply.
18. After the info supply is added, select Knowledge sources within the navigation pane, choose the newly added knowledge supply, and select Sync now to begin knowledge supply synchronization with the Amazon Kendra index.

The sync course of can take upwards of half-hour (relying on the quantity of knowledge to be crawled).

Now let’s allow entry management for the Amazon Kendra index.

19. Within the navigation pane, select your index.
20. On the Person entry management tab, select Edit settings and alter the settings to appear like the next screenshot.
21. Select Subsequent, then select Replace.

Carry out clever search with Amazon Kendra

Earlier than you attempt looking on the Amazon Kendra console or utilizing the API, make it possible for the info supply sync is full. To examine, view the info sources and confirm if the final sync was profitable.

Now we’re prepared to look our index.

1. On the Amazon Kendra console, navigate to the index and select Search listed content material within the navigation pane.
2. Let’s use the question “How do you detect safety occasions” and never present an entry token.

Primarily based on our entry management settings, a legitimate entry token is required to entry authenticated content material; subsequently, after we use this search question with out setting any person identify or group, no outcomes are returned.

3. Subsequent, select Apply token and set the person identify to a person within the area (for instance, usertest4) that has entry to the Microsoft Groups content material.

On this instance, the search will return a end result from the PDF file uploaded within the Microsoft Groups chat message.

4. Lastly, select Apply token and set the person identify to a distinct person within the area (for instance, usertest) that has entry to completely different Microsoft Groups content material.

On this instance, the search will return a distinct Microsoft Groups chat message.

This confirms that the ACLs ingested in Amazon Kendra by the connector for Microsoft Groups are being enforced within the search outcomes based mostly on the person identify.

Clear up

To keep away from incurring future prices, clear up the assets you created as a part of this answer. Should you created a brand new Amazon Kendra index whereas testing this answer, delete it. Should you solely added a brand new knowledge supply utilizing the Amazon Kendra connector for Microsoft Groups, delete that knowledge supply.

Conclusion

With the Amazon Kendra connector for Microsoft Groups, organizations could make invaluable data trapped of their Microsoft Groups cases obtainable to their customers securely utilizing clever search powered by Amazon Kendra. Moreover, the connector offers sides for Microsoft Groups attributes similar to channels, authors, and classes for the customers to interactively refine the search outcomes based mostly on what they’re searching for.

To be taught extra concerning the Amazon Kendra connector for Microsoft Groups, consult with Microsoft Teams.

For extra data on how one can create, modify, or delete metadata and content material when ingesting your knowledge from the Microsoft Groups, consult with Customizing document metadata during the ingestion process and Enrich your content and metadata to enhance your search experience with custom document enrichment in Amazon Kendra.

In regards to the Authors

Praveen Edem is a Senior Options Architect at Amazon Internet Providers. He works with main monetary companies clients, architecting and modernizing their crucial large-scale purposes whereas adopting AWS companies. He has over 20 years of IT expertise in software improvement and software program structure.

Gunwant Walbe is a Software program Improvement Engineer at Amazon Internet Providers. He’s an avid learner and eager to undertake new applied sciences. He develops advanced enterprise purposes, and Java is his major language of alternative.