Collaboration Experience FAQ

Currently, the product supports Microsoft Teams and Zoom. At this stage, we do not plan on adding more collaboration tools. However, this may change based on customer demand.​

Yes, we retrieve the same call quality data for online meetings, webinars and live events, but it isn’t possible to differentiate between the data of different event types.  ​

You can retrieve the call quality data for a mobile device if an employee ​used a mobile device to make a call through their company user account ​and they have another device with Nexthink Collector installed​ on it.

Call quality data is retrieved for Microsoft Teams meeting rooms that:

• are based in Windows.

• have the Nexthink collector installed.

• are registered in the Azure tenant used on the connector for Microsoft Teams configuration page, i.e. the tenant where you configured the required Azure app.

You can easily identify calls made by meeting rooms through the device type room_system which is accessible through the NQL field collaboration.session.participant_device.type.

The rate limits apply only to Zoom due to its API limitations: ​

• 30k calls per day for customers with a Zoom Pro account

• 60k calls per day for those with a Zoom Business+ account

If you are already pulling data from the same Meeting API, these rate limits apply both to requests that come from your organization and from Nexthink.

Yes, the API gives you access to all calls and online meetings within Microsoft, including PSTN data (external link), but this data is not stored by Nexthink.

• The connector for Microsoft Teams requires that you give Nexthink permission to CallRecords.Read.All to read call records for all calls and online meetings. Refer to the Get callRecord Microsoft documentation for more information.

• The Zoom connector requires you to configure the scopes meeting:read:admin to view all user meetings and dashboard_meetings:read:admin to view all user meeting information. These permissions give Nexthink access to several APIs:

  • 15 APIs listed in the meeting:read:admin Zoom documentation

  • 7 APIs listed in the dashboard_meetings:read:admin Zoom documentation

• The connector for Azure AD, which is necessary only in some cases, requires that you give Nexthink the User.Read.All permission to read the full set of profile properties, reports and managers of users in your organization. Refer to the Get a user Microsoft documentation for more information.

• The connector for Microsoft Teams retrieves all fields from the callRecord API. Refer to the Get callRecord Microsoft documentation for the list of fields.

• The connector for Zoom retrieves information from two APIs only, Get past meeting participants and List meeting participants QoS, to:

  • Gather information about the context and quality of calls.

  • Map a Zoom user email with the corresponding Nexthink user.

• The connector for Azure AD gathers:

  • The fields that are mapped to the connector's configuration. You are free to map any fields you wish, but you must configure at least one field for the connector to work, and if you are using Zoom, it must be the email address.

  • The user SIDs and UPNs from Azure AD. They are retrieved by default but only used internally.

• Nexthink Collector data, which is already available through the NQL data model. To achieve user identification, we leverage:

  • User SIDs that are retrieved from Collector.

  • User UPNs that are retrieved from Collector, if you activated them for macOS devices. Refer to Configuring Collector level anonymization for more information.

The system stores the data internally for 7 days. Only some of this data is available to users of the product and is accessible for a longer period of time.

• The system imports call-quality data from the connectors for Microsoft Teams and Zoom. The information is available in the NQL data model documentation under the Namespace collaboration section.

• For the connector for Azure AD, the fields mapped in the connector’s settings are available through NQL in the users table, in the fields starting with ad.

• Nexthink Collector data is available to users of the product through the NQL data model.

As a user of Collaboration Experience, you only have access to the data stored in Nexthink through the NQL data model. This data is managed according to the Nexthink data retention policy.

No, Nexthink discards all data of participants external to your organization. The product only stores the data of participants that the Nexthink platform can identify within your organization, i.e. those who have at least one device with Nexthink Collector installed on it.

You can correlate call quality data with:​

1. The usernames and UPNs retrieved by Collector​:

   1. These can be anonymized at the Collector level through a dedicated parameter. Refer to the ​Configuring Collector level anonymization for more information.

   2. These can be hidden in NQL results from certain user profiles. Refer to the Profiles documentation for more information about user permissions.​

2. User names, full names, distinguished names and email addresses imported through the connector for Azure AD:

   1. These are imported and visible in the NQL results only if mapped in the Azure AD connector settings​.

   2. These can be hidden in NQL results from certain user profiles. Refer to the Profiles documentation for more information about user permissions.

Data arrives each time a call ends.

No, once the connector is configured on a specific tenant, the product retrieves the call quality data for all users of this tenant. ​