Configuring MS Teams Settings in Operations Monitor User Interface

Once the MS Teams App is registered, follow the instructions in this section to configure the information in the Operations Monitor User Interface:

Configuring MS Teams Settings in the Operations Monitor User Interface:

1. Provide the Application (client) ID and Directory (tenant) ID retrieved from Microsoft Entra where your app is registered.

   Figure 7-7 MS Teams Configuration

   
   
   
2. In the Scope field, provide the Microsoft graph service URL. The default value is https://graph.microsoft.com/.default
3. In the Thumb print field, provide the thumbprint generated after uploading certificates as part of app registration.
4. In the MSGraph API Version field, select the version available from the drop down.
5. In the Private Key field, upload the private key file generated while creating the certificate, same certificate was uploaded while registering the app.
6. In the Data Source Latency (minutes ) field, enter the maximum number of minutes Session Monitor waits to receive the teams call correlation data from MS Graph API. The default value is 20 (minimum limit: 5 and maximum limit: 60).
   The Data Source Latency field reflects the time delay after which the MS Teams Direct Routing call data is available using the MS Graph API, once the call is finished. The value of this field should be set to a value more than the maximum delay observed in the receiving call data, to ensure that no DR calls are dropped/not correlated.
7. Select the Display Null Values check box to view null values in the Meta Data tab of Call Info. By default null values are not shown.
8. 8. Click Save.

   Note:

   Operations Monitor recommends a default value of 20 minutes based on the observations in the lab test of fetching data from Microsoft Graph. The minimum value of 5 minutes helps if Microsoft starts providing call data early, so that users also get ‘correlated’ data in Session Monitor early.