This documentation references external sources. Nexthink does not have control over the accuracy of third-party documentation, nor any external updates or changes that might create inconsistencies with the information presented on this page. Please report any errors or inconsistencies to Nexthink Support.
The connector for Microsoft Teams provides IT professionals with a way to view call quality data in the context of MS Teams users and their devices. Nexthink users can detect, investigate and diagnose individual low-quality call issues and problems with multiple devices. The integration of call quality data offers a more detailed and holistic view of the IT infrastructure, allowing IT teams to make informed decisions on how to optimize the digital employee experience (DEX).
Users must be part of Microsoft Azure Active Directory (Azure AD).
The connector for Microsoft Teams is part of Collaboration Experience, which requires a separate license.
To retrieve the call quality data (CQD) you must configure the application using the Azure portal and the Nexthink web interface.
Registering an Azure app
Connect to the Azure portal to register a new application.
Register a new application.
During the registration process, select the Single tenant option.
For the Redirect URI select Web.
If the application already exists in the Azure portal, you can reuse it to assign the permissions to read the call records.
Click on the Register button to confirm the app registration.
Access the API Permissions option from the left-side menu.
Add permission for Microsoft Graph.
When asked for the application permissions, select CallRecords.Read.All
Add the API permission.
If the account you are using doesn’t have proper privileges, it will be highlighted in the Status column on the permissions list.
For more information regarding the process, refer to the Microsoft documentation website.
Configuring the Nexthink web interface
Select Administration from the main menu.
Click Inbound Connectors in the navigation panel under Integrations.
Select Microsoft Teams from the list of inbound connectors.
To activate the connection between your Nexthink web instance and Microsoft Teams, Nexthink needs the following 3 Azure AD credentials.
Azure Tenant ID: Directory (tenant) ID in the Overview section of the Azure portal.
Azure Client ID: Application (tenant ID in the Overview section of the Azure portal.
Azure Client Secret: Generate the client secret in the Azure portal using the Certificates and secret option.
Click on New client secret.
Fill in the Description and Expiration values.
Note: You need to update the client secret both in the Azure portal and for the Nexthink connector after the expiration date.
Click Add and copy the content of the Value column.
Enter the three values gathered from the Azure portal into the configuration page of the connector for Microsoft teams in the Nexthink web interface.
For more information on how to generate an application key, refer to the Microsoft documentation website.
We are aware of the following limitations:
The system cannot retrieve call quality data for macOS devices that are not joined with an on-premise Active Directory. We are currently working to resolve this limitation.
Generally, Nexthink retrieves Call Quality Data for calls from a virtual machine as long as Collector is running on it. In some cases, however, the system does not link calls to the virtual machine because the Microsoft Teams connector identifies devices based on the MAC address, which is not always reliable for virtual machines.
The classification of the audio and video call quality is based on Microsoft’s definition of good versus poor call quality. For more information, refer to the Microsoft Stream Classification in Call Quality Dashboard documentation.
Not necessarily. If all users only authenticate through Azure Active Directory (cloud), the connector for Azure Active Directory is not needed.
You must enable the connector for Azure Active Directory only for Hybrid Azure AD joined devices, for example, when some users authenticate against (on-premises) Active Directory.
Nexthink associates the call quality data information with the device as long as Collector is running on it. When the user has a Microsoft Teams call on a Mobile phone, the Nexthink web interface provides information such as the
device_type and the type of connection but no device information.
Use the Test Credentials button on the connector page to validate that the Azure Tenant ID, Azure Client ID, and Azure Client Secret values are correct.
The current mechanism uses a subscription to receive the data from Graph API. Every time a call ends, the system pushes the call details to the Nexthink web platform. The process is not instant, and new data typically arrive 5 to 10 minutes after the end of the call.
Generally, yes, as long as Collector is running on the virtual machine. In some cases, the system does not link calls to the virtual machine because the Microsoft Teams connector identifies devices based on the MAC address, which is not always reliable for virtual machines.