Skip to main content

Cotool + Microsoft Graph (Admin)

Connect Microsoft Graph to Cotool for Entra ID, Microsoft 365, and Intune investigations, plus two containment actions: disable a user and revoke sessions.

Identity & Access
Updated

The short answer

The Microsoft Graph Admin integration gives Cotool agents organization-wide visibility into Microsoft Entra ID, Microsoft 365 activity, and Intune managed devices, plus two account containment actions: disabling a user and revoking their sign-in sessions.[1][2]

How it connects: A Microsoft administrator grants tenant-wide admin consent to Cotool's Entra application. Cotool then uses the OAuth 2.0 client credentials flow for app-only Graph tokens scoped to that tenant, so it never handles an end-user password.[1][6]

What Cotool uses from Microsoft Graph (Admin)

Sign-in and audit logs
Agents read Entra directory audit logs, sign-in logs, and provisioning events. Microsoft returns sign-ins only within the Entra ID default retention period.[1][7]
Users, groups, roles, and apps
Agents read users, groups, directory roles, transitive memberships, app role assignments, enterprise applications, and PIM role schedules to explain how a user got access.[1]
Identity Protection risk detections
Risk detections feed a log ingest stream in Cotool. Microsoft requires an Entra ID P1 or P2 license to use the risk detection API.[1][8]
Intune devices and audit log
Agents read Intune managed devices, including owner, compliance, encryption, and remote action history, and the Intune audit log to answer who wiped a device or changed a policy.[1]

Response actions

These change state in Microsoft Graph (Admin), so they are the steps teams usually gate behind approval.

Revoke sign-in sessions
Revoking sessions invalidates a user's refresh tokens and browser session cookies. Microsoft notes there can be a delay of a few minutes before tokens are revoked.[1][9]
Disable a user
Disabling sets accountEnabled to false. Microsoft lists User.EnableDisableAccount.All with User.Read.All as the least-privileged combination for that update.[1][10]

Detections, hunts, and triage

Explain a risky sign-inTriage
An agent pulls the user's sign-ins with applied conditional access outcomes, their roles and group paths, and their devices' compliance, then judges whether the sign-in fits.[1][3]
Find risky OAuth grantsHunt
A hunt lists applications holding delegated OAuth grants that can act as a user and enriches them with app names, IDs, roles, and scopes.[1][4]
Contain a compromised accountResponse
With approval, an agent disables the Entra user and revokes their sessions, both added as response actions in release 0.76.0.[2][5]

Setup and permissions

A Global Administrator or Privileged Role Administrator grants consent. The consent flow sends the admin to Microsoft's tenant admin consent endpoint and returns the result to the app.[1][6]

PermissionAccess
AuditLog.Read.AllRead sign-in logs, directory audits, and provisioning events.[7]Read
IdentityRiskEvent.Read.AllList Identity Protection risk detections.[8]Read
User.RevokeSessions.AllRevoke a user's sign-in sessions with the application permission.[9]Write
User.EnableDisableAccount.AllDisable or enable a user account, together with User.Read.All.[10]Write
  • Cotool's integration also requests Directory.Read.All, Application.Read.All, RoleManagement.Read.Directory, Policy.Read.ConditionalAccess, and two Intune read permissions; the docs list what each is used for.[1]

How Cotool works with Microsoft Graph (Admin)

  • Cotool requests only the .default scope at runtime, so the token carries just the application permissions the tenant admin consented to.[1]
  • Cotool improved Microsoft Graph admin investigations with richer user profiling in release 0.46.0.[2]

FAQ

Is this like Google Workspace domain-wide delegation?
No. Cotool's docs explain that Microsoft's equivalent is tenant-wide admin consent to an Entra application followed by app-only Graph access.[1]
Why are conditional access results missing from sign-ins?
Microsoft omits applied conditional access policies from sign-in responses unless the caller can read conditional access, which is why the integration requests Policy.Read.ConditionalAccess.[1]

Sources

  1. Microsoft Graph Admin integration (Cotool docs) · accessed November 16, 2026
  2. Changelog (Cotool docs) · accessed November 16, 2026
  3. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  4. Threat hunting (Cotool Hunt) · accessed November 16, 2026
  5. AI SOC (Cotool) · accessed November 16, 2026
  6. Admin consent protocols (Microsoft identity platform) · accessed November 16, 2026
  7. List signIns (Microsoft Graph) · accessed November 16, 2026
  8. List riskDetections (Microsoft Graph) · accessed November 16, 2026
  9. user: revokeSignInSessions (Microsoft Graph) · accessed November 16, 2026
  10. Update user (Microsoft Graph) · accessed November 16, 2026

Related integrations

All integrations

Use cases with Microsoft Graph (Admin)

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo