Microsoft Search Chat Message

About

Microsoft Search Chat Message backend uses the Graph API search chat messages in a channel or individual chat.

Limitations

The following are limitations for the Microsoft Search Chat Messages backend. If a feature is not supported by the Microsoft Search Graph API, it will also be not supported by a Microsoft Search Graph backend. For more information, refer to the Microsoft Graph API documentation.

  • Refiners are not supported by the Microsoft Search Chat Message Backend

  • If you are upgrading from an older version of SmartHub, the Microsoft Search backends must be removed and re-added. For more information on upgrading, see How to Upgrade SmartHub.

Set Azure Active Directory Authentication

Client ID Requirements

  • The Client ID specified in Azure Active Directory Authentication above, must belong to an application with the following permissions, set in Azure:

    1. Microsoft Graph

      • Chat.Read or Chat.ReadWrite

      • ChannelMessage.Read.All

How to Add the Microsoft Search Chat Message Backend to SmartHub

Use the following instructions to add the Microsoft Search Chat Message backend to SmartHub:

  1. Navigate to the SmartHub Administration page: http(s)://[web-app-url]/_admin
  2. Click Add New Backend.
  3. The Backend Settings dialogue box appears.
  4. Enter a Backend Name.
  5. Select the Backend Type "MSSearchChatMessagesBackend"
  6. Authentication
    1. Impersonate - true
      1. Security trims the results using the current user running the search
    2. Impersonate - false
      1. Client Id:
        1. Enter the Application ID from Azure App Registrations.
      2. Client Secret:
        1. Enter the Key's value from Azure App Registrations.
      3. Microsoft Login Endpoint:
        1. Example: https://login.microsoftonline.com
      4. Access Token:
        1. Enter the access token from SmartHub's OAuth page.

      5. Refresh Token:

        1. Enter the refresh token from SmartHub's OAuth page.

        2. To get AccessToken and Refresh token, "Authorize" button must be clicked, but all above fields must be completed (GraphUrl, ClientId, ClientSecret, MicrosoftLoginEndpoint).

  7. Click OK.

How to Register an App in Azure and Configure It

If you use SmartHub with Azure Active Directory authentication you can reuse the same App and jump to step 5.

  1. Navigate to portal.azure.com and log in.
  2. From the left side menu go to Azure Active Directory > App registrations > New registration.
  3. On the Register an application window, specify the following:
    • Name: Enter the name of the application.
    • Application type: Select Web app / API.
    • Sign-on URL: Enter the SmartHub's URL.
  4. Select API Permissions to open the settings menu panel.
  5. Click Add a Permission.
  6. Select APIs my organization uses and add the following permissions (as you type the name, it appears):
    1. Microsoft Graph

      1. Chat.Read or Chat.ReadWrite

      2. ChannelMessage.Read.All

  7. Click Certificates & secrets > New client secret to generate a client secret key.
  8. In the window that appears (shown below) enter the following information.
    1. Description:
      1. Enter a name for the client secret.
      2. Note: The name is your client secret
    2. Expires: Select the period until expires.
    3. A Value is generated after you click Add.

Metadata

In order to use the properties received from Microsoft Graph, properties are flattened. BA Insight does this because Microsoft Graph API returns properties in this format:

"from":{"emailAddress":{"name":"ExampleName","address":"no-reply@examplename.com"}}}}

In this case, if you want to use the address property, you need to add this property in SmartHub: from.emailAddress.address. Microsoft calls this type of property "recipient" as it contains information about the user sending the email. If the property from the Microsoft Graph API returns a collection of recipient's, the values for the specific property in SmartHub will be returned as a string with ";" used as a delimiter.

The format for Recipient collection must be the same as above: propertyName.emailAddress.name / propertyName.emailAddress.address. For more information on all the properties for the chatMessage resource type from Microsoft Graph, see chatMessage resource type in the Microsoft documentation

The following metadata is available for your results:

  • @data.type

  • id

  • createdDateTime

  • lastModifiedDateTime

  • subject

  • importance

  • webLink

  • from.emailAddress.address

  • from.emailAddress.name

  • channelIdentity.channelId

  • etag

  • chatId