Cotool + Microsoft Sentinel
Connect Microsoft Sentinel to Cotool so agents run KQL on analytics and data lake tables, triage incidents, and create Scheduled analytics rules.
The short answer
With Microsoft Sentinel connected, Cotool agents run KQL against a Sentinel workspace and its data lake tier, read and update incidents with their alerts, entities, and comments, and list or create Scheduled analytics rules.[1]
How it connects: Cotool signs in as a Microsoft Entra app registration with client credentials and calls Azure's REST APIs. Access comes from one Azure RBAC role on the resource group that holds the workspace; no Microsoft Graph or Log Analytics API application permissions are needed.[1]
What Cotool uses from Microsoft Sentinel
- Analytics-tier tables
- Agents run Kusto queries against any table in the Log Analytics workspace, such as
SigninLogs,SecurityEvent,OfficeActivity, and the DefenderDevice*tables.[1][7] - Data lake tables
- For data kept past the analytics retention window, agents query the Sentinel data lake tier through Microsoft's data lake KQL API, with the same app and workspace.[1][8]
- Incidents
- Agents list and read incidents together with their alerts, entities, and comments, which gives a triage agent the same context an analyst opens in the portal.[1]
- Analytics rules
- Agents list and read your analytics rules, and Cotool syncs them into its detection coverage views.[1]
Response actions
These change state in Microsoft Sentinel, so they are the steps teams usually gate behind approval.
Detections, hunts, and triage
Example query
SigninLogs
| where TimeGenerated > ago(24h)
| where UserPrincipalName =~ "jdoe@example.com"
| summarize attempts = count(), failures = countif(ResultType != "0"), ips = make_set(IPAddress) by AppDisplayName, Location
| order by failures descThe kind of query a triage agent runs against SigninLogs before deciding whether an identity alert is real. Microsoft's Logs query API runs the same KQL you would write in the portal.[1][7]
Setup and permissions
Register an app in Microsoft Entra ID, create a client secret, and assign the app a Microsoft Sentinel role on the resource group that contains the workspace. Microsoft recommends assigning Sentinel roles at the resource group level.[1][6]
| Permission | Access | Why |
|---|---|---|
| Microsoft Sentinel ReaderRead-only: KQL queries and reading incidents and analytics rules.[1][6] | Read | Read-only: KQL queries and reading incidents and analytics rules.[1][6] |
| Microsoft Sentinel ResponderReader plus managing incidents: comments, updates, and closing. Cotool's recommended role.[1][6] | Write | Reader plus managing incidents: comments, updates, and closing. Cotool's recommended role.[1][6] |
| Microsoft Sentinel ContributorResponder plus creating and updating analytics rules.[1][6] | Write | Responder plus creating and updating analytics rules.[1][6] |
| Log Analytics Reader (if data lake queries return 403)Grants access to the Log Analytics workspace when the Sentinel role alone doesn't authorize data lake queries.[1][6] | Read | Grants access to the Log Analytics workspace when the Sentinel role alone doesn't authorize data lake queries.[1][6] |
- Role assignments are cumulative, so an app with both Reader and Contributor has Contributor's permissions. Assign only the role you intend.[6]
- Microsoft recommends certificates over client secrets as the more secure credential type. Cotool's setup uses a client secret, which expires; rotate it in Cotool before the expiry date.[1][9]
How Cotool works with Microsoft Sentinel
- After you connect, Cotool runs a job that maps the workspace's analytics-tier tables, data lake tables, and analytics rules so agents know which data sources exist.[1]
- Cotool added Sentinel data lake queries and table mapping for long-retention investigations in release 0.74.0.[3]
- If KQL queries fail while incidents work, Cotool's docs point to the Workspace ID: it is the GUID on the workspace Overview page, not the Subscription ID.[1]
FAQ
- Which Sentinel role should I give Cotool?
- Cotool recommends Microsoft Sentinel Responder, which allows KQL queries plus updating, commenting on, and closing incidents. Use Reader for read-only access, and Contributor only if agents should create or update analytics rules.[1]
Sources
- Microsoft Sentinel Integration (Cotool docs) · accessed November 16, 2026
- Microsoft Graph Admin Integration (Cotool docs) · accessed November 16, 2026
- Changelog (Cotool docs) · accessed November 16, 2026
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Hunt threats continuously (Cotool Hunt) · accessed November 16, 2026
- Roles and permissions in the Microsoft Sentinel platform (Microsoft Learn) · accessed November 16, 2026
- Azure Monitor Logs query API overview (Microsoft Learn) · accessed November 16, 2026
- Run KQL queries on Microsoft Sentinel data lake using APIs (Microsoft Learn) · accessed November 16, 2026
- Add and manage app credentials in Microsoft Entra ID (Microsoft Learn) · accessed November 16, 2026


