Configuring AI tools
This Technical Preview is made available to customers free of charge for their evaluation and feedback; in general availability the functionalities of the preview may be subject to additional cost and/or licensing. As such, the Technical Preview, the documentation, and any updates are provided for limited evaluation only and on an ‘as-is’ and ‘as-available’ basis without warranty of any kind.
Define which AI tool requires monitoring for your organization for accurate visibility, labeling, and categorization of AI usage. Involve application and security stakeholders early to help streamline adoption and visibility of your AI portfolio.
Choosing AI tools to configure in Nexthink
Identify AI tools available for configuration in Nexthink:
Review telemetry or traffic data from the Nexthink Collector or your network security stack.
Consult your SSO provider or identity management platform to list active AI services.
Interview product owners to understand user segments and associated risks.
Prioritize the tools that require configuration by evaluating:
Widely used GenAI tools like ChatGPT, Microsoft Copilot, Gemini, or Claude.
Internal or custom AI agents, such as virtual assistants or chatbots developed for specific business functions.
AI applications embedded in productivity or communication platforms such as Copilot in Outlook or MS Teams.
Tools with rising adoption but uncertain compliance or business value.
Configuring AI tools for Nexthink monitoring
To configure a new AI tool:
Navigate to AI Tools > Manage AI tools from the main navigation.
Click the New AI tool button on the top-right corner (or select an existing tool from the table to edit).

From the AI tools configuration page, fill in the fields:
An AI tool name, such as ChatGPT DEV.
The system automatically generates NQL ID of the AI tool based on the name. In this case:
#chatgpt_dev
Description to provide AI tool details for internal use.
Choose one or both Application types: Web or Desktop.
For Web AI applications:
URL Name is a free-text label to identify the configuration. Example:
ChatGPT
URL pattern is the main domain of the web application. Defines where the AI tool is accessed. Example:
chatgpt.com
Conversation endpoint pattern is the specific path used to detect interactions with the AI tool. Helps Nexthink identify when an interaction is occurring. Refer to the Determining the Conversation endpoint pattern using your browser section below.
For Desktop AI applications define their respective Binaries.
Desktop applications represent binaries grouped with their associated subprocesses. As a result, application-related metrics, dashboards and AI insights include all subprocesses.
The system estimates AI usage on Desktop-type applications using the
focus_time
field from theexecution.events
table in the NQL data model.If the
focus_time
opt-in field is not enabled, Nexthink cannot monitor user interactions with AI tools on desktop applications.
Add available Licenses for the AI tool, if available.
Save AI tool configuration.

Exception: Configuring Microsoft 365 Copilot using API credentials
The system uses the Entra ID connector to collect user-license data and tag interaction events based on whether the employee uses a free or licensed version of Microsoft Copilot.
Nexthink AI Tools collects user-license data for MS Copilot by default, even if you do not configure the MS Copilot connector.
When monitoring usage of Microsoft Copilot, you can filter data by Copilot type:
The Microsoft 365 Copilot filter displays tool-specific data for licensed Copilot usage.
The Copilot chat filter displays tool-specific data for unlicensed Copilot usage.
Nexthink supports API-based setup only for Microsoft Copilot.
To set up MS Copilot in Nexthink:
Navigate to AI tools > Manage AI tools from the main navigation.
Click on the Copilot hyperlink listed in the table on the Manage AI tools page, or use the item's action menu to Edit Copilot settings.
From the AI tools configuration page, fill in the Description to provide AI tool details for internal use.
For MS Copilot, the name and NQL ID fields are predetermined—not editable.
Select the corresponding connector credentials preconfigured in Nexthink for the API credentials field.
Add available Licenses for MS Copilot, if available.
Save AI tool configuration.

RELATED TASKS
Last updated
Was this helpful?