Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page outlines the steps required to setup Microsoft (MS) Teams as a chat channel for Luma. Please reach out to the Serviceaide support team and raise a support ticket asking them to create the Luma channel connector for MS Teams and provide a package; include your Luma tenant ID in the ticket information. Please also specify name for your bot in MS Teams. This is how users will identify the contact in MS Teams once all the configuration steps are completed. After raising the support ticket, Administrators can complete the setup by following the steps mentioned in this article. Once the setup is complete, users will be able to send and receive messages from Luma using Microsoft Teams. 

Table of Contents

Info
titleNote

To configure MS Teams, you must have an account in Microsoft Office 365 portal and Microsoft Teams portal.

...

Users using MS Teams to communicate with Luma can be auto authenticated using Channel Source Data. Administrators can need to follow the below steps to enable auto authentication:

Configuration Changes on Azure Portal

  1. Login to Azure portal with login credentials and navigate to your Bot.
  2. Navigate to Bot Management→Settings. Click on Manage to open Microsoft Apps settings.

Image Removed

...

  1. Azure Active Directory.                                                                                                                                   Image Added
  2. Click on 'New Registration' to register a new application.Image Added
  3. On 'Register an application' screen, add display name for your application. On Support account types, select 'Accounts in this organizational directory only' and click 'Register'.       Image Added
  4. A new Application will now be available. System will auto generate Client/Application ID, Directory/Tenant ID and Object ID for the application.Image Added
  5. Next step is to create a new Client Secret Key. Click on 'Certificates & secret'. On 'Certificate & secret' screen, click on 'New Client secret' to generate a new secret key. Add a name to the secret key to identify the key and select Expires ‘Never’. Click 'Add'.                                                                                                               Image Added
  6. A new secret key will be auto generated. This secret key will be used in Luma to enable auto authentication. The key would be encrypted later, Copy the key and save it for later use. This ID will be used in Channel configuration setting in Luma.                                                                                                                                                                   Image Added

  7. Now, navigate to API permissions and click on Add a permission button to request permissions for your application to communicate with Luma.

4. On Request API permission screen, Click on Microsoft Graph.

...

5.  Click Application permissions,select the below permissions:

  • User.Read
  • Under AccessReview, select AccessReview:Read.All

...

 6. Requested permissions will now appear on in the API Permission list. Click 'Grant admin consent ' button. 

7.  System now prompt prompts a message to grant consent for requested permissions. Click Yes to update.

...

8.  Once the permissions are added, Success message "Successfully granted  admin consent for the requested permissions." will appears.

Image Added

9.  Copy the Application Id from Application screen and save it for later use. This ID will be used in Channel configuration setting in Luma.Image AddedUsers can

Configuration Changes in Luma

  1. Login to Luma with admin credentials and navigate to Tenant Settings.
  2. On Settings screen→ Manage Channel ID section, select 'MS_Teams' Channel for configuration. Set User attributes to 'channelSourceData'. Add User App id and Secret key copied from Azure portal (in previous steps) and click on Save.

Image Added

Users will now be auto authenticated using channel specific source data.