Support

Connector for Microsoft Copilot

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 Microsoft Copilot tool allows you to measure and view AI interactions data and use the Nexthink web interface to investigate Microsoft Copilot interactions for well-informed decisions when optimizing the digital employee experience (DEX).

Prerequisites

Configuring the Azure application

Configure the application from the Azure page to retrieve call quality data:

  1. Sign in using your Azure credentials.

  2. Register a new application.

    • During the registration process, select the Single tenant option.

  3. For the Redirect URL, select Web.

    • If the application already exists in the Azure portal, you can reuse the application to assign the permissions to read the call records.

  4. Register the application.

  5. Access the API Permissions option from the left-side menu.

  6. Add permission for Microsoft Graph.

    • Select AiEnterpriseInteraction.Read.All and add the API permission. See the images below.

    The Status column on the permissions list indicates if the Azure account you are using lacks proper privileges. Refer to the Register an application with the Microsoft identity platform documentation from Microsoft for more information on the steps listed above.

  7. Access the Overview section of the configured application to copy and save Azure AD credentials for the Nexthink connector configuration.

    • Application (client) ID

    • Directory (tenant) ID

    • Generate and copy the client secret Value in the Azure portal using the Certificates and secret option for the Nexthink tool configuration.

      • Select New client secret.

      • Fill in the Description and Expiration values.

      • Select Add and copy the Value.

After the expiration date, you need to update the client secret in the Azure portal and for the Nexthink connector credentials.

Configuring the MS Copilot connector credentials in Nexthink

From the connector credential configuration page, fill out the fields using the information from the connection you created in Azure.

  1. Choose the HTTPS option from the Protocol drop-down.

  2. Paste the Microsoft API https://graph.microsoft.com into the URL address field.

  3. Choose the OAuth 2.0 - Client Credentials option from the Authorization drop-down.

  4. Copy the verification token from the Copilot connection and paste it into the Access token URL field.

  5. Enter the Client ID and Client secret you obtained from configuring the Azure application.

  6. Select Header under Authorization information. Nexthink advises against selecting Body based on Request for Comments (RFC) standards.

  7. Save the credential.

FAQ

Do I always need to use the connector for Microsoft Entra ID to obtain the call quality data?

Not necessarily. If all users only authenticate through Entra ID, the connector for Microsoft Entra ID is not needed.

You should enable the connector for Entra ID only for Hybrid Entra ID joined devices. For example, when some users authenticate against (on-premises) Entra ID.

How can I verify that I have properly configured the subscription?

From the Nexthink web interface, use the Test Credentials button on the connector page to validate the Azure Tenant ID, Azure Client ID, and Azure Client Secret values.

How often is the Copilot AI interaction data refreshed? Is it instant?

The current mechanism uses a subscription to receive the data from Graph API. Every time an AI interaction happens, the system pushes the interaction details to the Nexthink platform.

The process is not instant, as the data typically arrives less than 1 minute after the interaction happens, but Microsoft Graph API has a maximum latency of 60 minutes for AI interactions.

Last updated

Was this helpful?