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.
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.
Detections, hunts, and triage
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]
| Permission | Access | Why |
|---|---|---|
AuditLog.Read.AllRead sign-in logs, directory audits, and provisioning events.[7] | Read | Read sign-in logs, directory audits, and provisioning events.[7] |
IdentityRiskEvent.Read.AllList Identity Protection risk detections.[8] | Read | List Identity Protection risk detections.[8] |
User.RevokeSessions.AllRevoke a user's sign-in sessions with the application permission.[9] | Write | Revoke a user's sign-in sessions with the application permission.[9] |
User.EnableDisableAccount.AllDisable or enable a user account, together with User.Read.All.[10] | Write | Disable or enable a user account, together with User.Read.All.[10] |
- 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)
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
- 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
- Threat hunting (Cotool Hunt) · accessed November 16, 2026
- AI SOC (Cotool) · accessed November 16, 2026
- Admin consent protocols (Microsoft identity platform) · accessed November 16, 2026
- List signIns (Microsoft Graph) · accessed November 16, 2026
- List riskDetections (Microsoft Graph) · accessed November 16, 2026
- user: revokeSignInSessions (Microsoft Graph) · accessed November 16, 2026
- Update user (Microsoft Graph) · accessed November 16, 2026
