Organizations use messaging platforms like Microsoft Teams to carry the fitting folks collectively to securely talk with one another and collaborate to get work carried out. Microsoft Groups captures invaluable organizational data within the type of the data that flows by way of it as customers collaborate. Nevertheless, making this information simply and securely out there to customers might 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 go looking ineffective when looking for correct solutions to questions from the content material and subsequently requires clever search capabilities which have the flexibility 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 subjects associated to AWS.
Answer overview
Microsoft Groups content material for lively organizations is dynamic in nature on account of steady collaboration. Microsoft Groups contains 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 straight 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 resolution, we configure Microsoft Groups as a knowledge supply for an Amazon Kendra search index utilizing the Amazon Kendra connector for Microsoft Groups. Based mostly on the configuration, when the information 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 Checklist (ACL) info for every message and doc. When entry management or person context filtering is enabled, the search outcomes of a question made by a person contains outcomes solely from these paperwork that the person is allowed to learn.
The Amazon Kendra connector for Microsoft Groups can combine with AWS IAM Id Middle (Successor to AWS Single Signal-On). You first should allow IAM Id Middle and create a company to sync customers and teams out of your lively listing. The connector will use the person title and group lookup for the person context of the search queries.
With Amazon Kendra Expertise Builder, you may construct and deploy a low-code, absolutely purposeful search utility to go looking 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:
Be aware 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 are going to use for our Amazon Kendra search queries.
The next steps describe the configuration of a brand new Amazon Kendra connector utility within the Azure portal. This can create a person OAuth token for use in configuring the Amazon Kendra connector for Microsoft Groups.
- Log in to Azure Portal together with your Microsoft credentials.
- Register an utility with the Microsoft Identity platform.
- Subsequent to Shopper credentials, select Add a certificates or secret so as to add a brand new consumer secret.
- For Description, enter an outline (for instance,
KendraConnectorSecret
). - For Expires, select an expiry date (for instance, 6 months).
- Select Add.
- Save the key ID and secret worth to make use of later when creating an Amazon Kendra knowledge supply.
- Select Add a permission.
- Select Microsoft Graph so as to add all needed Microsoft Graph permissions.
- Select Utility permissions.
The registered utility 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 may choose a lesser scope primarily based 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 identification crawl)
- Channel Attachment:
ChannelMessage.Learn.All
Group.Learn.All
Person.Learn
Person.Learn.All
TeamMember.Learn.All
(user-group mapping for identification crawl)
- Channel Wiki:
Group.Learn.All
Person.Learn
Person.Learn.All
TeamMember.Learn.All
(user-group mapping for identification 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 identification 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 identification 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 identification 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 identification crawl)
- Calendar Assembly:
Calendars.Learn
Group.Learn.All
TeamMember.Learn.All
Person.Learn
Person.Learn.All
TeamMember.Learn.All
(user-group mapping for identification crawl)
- Assembly Notes:
Group.Learn.All
Person.Learn
Person.Learn.All
Information.Learn.All
TeamMember.Learn.All
(user-group mapping for identification crawl)
- Choose your permissions and select Add permissions.
Configure the information 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 need to use an current Amazon Kendra index, or create a brand new Amazon Kendra index. Then full the steps on this part. For extra info on this subject, seek advice from Microsoft Groups.
- On the Amazon Kendra console, open the index and select Knowledge sources within the navigation pane.
- Select Add knowledge supply.
- Below Microsoft Groups connector, select Add connector.
- Within the Specify knowledge supply particulars part, enter the small print of your knowledge supply and select Subsequent.
- Within the Outline entry and safety part, for Tenant ID, enter the Microsoft Groups tenant ID from the Microsoft account dashboard.
- Below Authentication, you may 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 and techniques Supervisor secret that has the consumer ID and consumer secret of the Microsoft Groups tenant that you really want the connector to entry.
- Select Save.
- Optionally, select the suitable payment model:
- Mannequin A fee fashions are restricted to licensing and fee fashions that require safety compliance.
- Mannequin B fee fashions are appropriate for licensing and fee fashions that don’t require safety compliance.
- Use Analysis Mode (default) for restricted utilization analysis functions.
- For IAM function, you may 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.
- Select Subsequent.
- Within the Configure sync settings part, present info concerning your sync scope.
- For Sync mode, select your sync mode (for this publish, choose Full sync).
With the Full sync choice, 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. In the event you select New or modified content material sync or New, modified, or deleted content material sync, each time the sync job runs, it’s going to course of solely objects added, modified, or deleted for the reason that final crawl. Incremental crawls can assist scale back runtime and price when used with datasets that append new objects to current knowledge sources regularly.
- For Sync run schedule, select Run on demand.
- Select Subsequent.
- Within the Set area mappings part, you may optionally configure the sphere mappings, whereby Microsoft Groups area names could also be mapped to a distinct Amazon Kendra attribute or side.
- Select Subsequent.
- Evaluation your settings and ensure so as to add the information supply.
- After the information supply is added, select Knowledge sources within the navigation pane, choose the newly added knowledge supply, and select Sync now to start out knowledge supply synchronization with the Amazon Kendra index.
The sync course of can take upwards of half-hour (relying on the quantity of information to be crawled).
Now let’s allow entry management for the Amazon Kendra index.
- Within the navigation pane, select your index.
- On the Person entry management tab, select Edit settings and alter the settings to seem like the next screenshot.
- 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 information supply sync is full. To verify, view the information sources and confirm if the final sync was profitable.
Now we’re prepared to go looking our index.
- On the Amazon Kendra console, navigate to the index and select Search listed content material within the navigation pane.
- Let’s use the question “How do you detect safety occasions” and never present an entry token.
Based mostly 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 title or group, no outcomes are returned.
- Subsequent, select Apply token and set the person title 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.
- Lastly, select Apply token and set the person title 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 primarily based on the person title.
Clear up
To keep away from incurring future prices, clear up the assets you created as a part of this resolution. In the event you created a brand new Amazon Kendra index whereas testing this resolution, delete it. In the event 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 info trapped of their Microsoft Groups cases out there to their customers securely utilizing clever search powered by Amazon Kendra. Moreover, the connector offers aspects for Microsoft Groups attributes similar to channels, authors, and classes for the customers to interactively refine the search outcomes primarily based on what they’re in search of.
To study extra concerning the Amazon Kendra connector for Microsoft Groups, seek advice from Microsoft Groups.
For extra info on how one can create, modify, or delete metadata and content material when ingesting your knowledge from the Microsoft Groups, seek advice from Customizing doc metadata in the course of the ingestion course of and Enrich your content material and metadata to boost your search expertise with customized doc 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 providers clients, architecting and modernizing their crucial large-scale purposes whereas adopting AWS providers. He has over 20 years of IT expertise in utility improvement and software program structure.
Gunwant Walbe is a Software program Growth Engineer at Amazon Internet Providers. He’s an avid learner and eager to undertake new applied sciences. He develops complicated enterprise purposes, and Java is his major language of alternative.