Kusto Analytics Assistant turns natural-language analytics questions into read-only KQL, runs them against Azure Data Explorer, and returns grounded results with the exact query used. A recurrence trigger can also run a scheduled query and email a summary of the top rows to the invoking user.
Agent
- The primary agent retains the selected cluster and database as conversation context and asks for either value when it is missing.
- The Kusto Query Interpreter skill translates analytics questions into KQL, rejects mutating or administrative requests, and reports tool failures without inventing results.
- The Kusto MCP tool executes queries with the invoking user’s connection.
- The Office 365 Outlook “Send an email (V2)” action sends the scheduled summary to the invoking user. It is send-only, so the agent cannot read, move, or delete mail. Because connector tools do not fix input values, the agent instructions limit the recipient to the invoking user’s own address.
Automation
The recurrence trigger invokes the agent with a prompt containing the target cluster, database, and table. The exported solution uses explicit placeholders for those values so contributors do not publish environment-specific data.
Import notes
After importing the unmanaged solution:
- Authorize the Azure Data Explorer, Office 365 Outlook, and Microsoft Copilot Studio connection references.
- Replace the
<cluster>,<region>,<database>, and<table>placeholders in the recurrence trigger prompt. - Configure the recurrence frequency, interval, start time, and time zone.
- Confirm the importing user has read access to the target Kusto database and permission to send mail from the selected mailbox.
- Review and test the generated KQL before publishing the agent and enabling the recurrence trigger.
The solution does not write to Kusto, send to arbitrary recipients, or create a dashboard.