Cotool + Azure Event Hub
Stream Azure Activity Logs, resource diagnostic logs, Entra ID diagnostic logs, Defender for Cloud alerts, and Intune logs into Cotool through Azure Event Hubs.
The short answer
The Azure Event Hub integration ingests Azure platform logs into Cotool Logs continuously. You point Azure diagnostic settings and Defender for Cloud Continuous Export at an event hub, and Cotool reads five separately toggled streams from it for search and detections.[1]
How it connects: Cotool reads the hub as a consumer. The recommended mode is a user-assigned managed identity with workload identity federation, so no secret is created or stored; a SAS connection string with only the Listen claim also works.[1][8]
What Cotool uses from Azure Event Hub
- Activity Log
- Subscription control-plane audit events, such as role assignments, resource writes and deletes, key listings, and policy and security events, land in
azure_activity.[1] - Resource logs
- Data-plane diagnostic logs from Azure Firewall, Application Gateway and Front Door WAF, AKS
kube-audit, Storage, Key Vault, Container Registry, PostgreSQL, and Azure OpenAI land inazure_resource_logs.[1] - Entra ID diagnostic logs
- Tenant-level categories not available through the Graph reporting API, mainly
MicrosoftGraphActivityLogsandEnrichedOffice365AuditLogs, land inazure_entra_logs.[1] - Defender for Cloud alerts and Intune logs
- Security alerts from Continuous Export land in
azure_defender_alerts. Intune audit, operational, device, and compliance categories land inazure_intune_logs.[1]
Detections, hunts, and triage
- Detect risky Azure control-plane changesDetection
- Python detections run on
azure_activityfor events such as new role assignments or key listings, and an agent investigates each alert they raise.[1][3] - Hunt in Entra diagnostic categoriesHunt
- A hunt can use
MicrosoftGraphActivityLogs, one of the Entra categories the Graph reporting API doesn't offer. It requires Entra ID P1 or P2 and is high volume: roughly 60k events per month per 1,000 users.[1]
Setup and permissions
Create a user-assigned managed identity, give it the Azure Event Hubs Data Receiver role on the namespace, and add a federated credential that trusts Cotool's identity with the issuer, subject, and audience shown on Cotool's connect form.[1][5][8]
| Permission | Access | Why |
|---|---|---|
| Azure Event Hubs Data ReceiverLets the managed identity receive events from the hubs. Assign it on the namespace or a narrower scope.[1][5] | Read | Lets the managed identity receive events from the hubs. Assign it on the namespace or a narrower scope.[1][5] |
ListenThe only claim the SAS policy needs if you use a connection string instead of a managed identity.[1][6] | Read | The only claim the SAS policy needs if you use a connection string instead of a managed identity.[1][6] |
| Diagnostic settings on each sourceSet by your admins, not Cotool: they stream each subscription, resource, Entra tenant, and Intune tenant to the hub.[1][7] | Write | Set by your admins, not Cotool: they stream each subscription, resource, Entra tenant, and Intune tenant to the hub.[1][7] |
- Event hubs must be in the same region as the regional resources that stream to them, so multi-region estates need one hub or namespace per region.[1][7]
- Use a dedicated consumer group named
cotoolif another tool already reads the same hub. Cotool suggests 4 partitions and 7-day retention, which is your replay buffer if ingest pauses.[1]
How Cotool works with Azure Event Hub
- Cotool routes each record by its content, not by the hub it arrived on, so every source can share one hub.[1]
- Every event is archived in full before indexing, and each table keeps the complete provider record in
raw_payload.[1] - Intune and Entra both name a category
AuditLogs; Cotool tells them apart by content and collapses re-delivered Intune records.[1]
FAQ
Sources
- Azure Event Hub Integration (Cotool docs) · accessed November 16, 2026
- Microsoft Graph Admin Integration (Cotool docs) · accessed November 16, 2026
- Detections are code (Cotool Detect) · accessed November 16, 2026
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Authorize access with Microsoft Entra ID (Azure Event Hubs docs) · accessed November 16, 2026
- Shared access signature authorization for Event Hubs (Microsoft Learn) · accessed November 16, 2026
- Diagnostic settings in Azure Monitor (Microsoft Learn) · accessed November 16, 2026
- Configure a user-assigned managed identity to trust an external identity provider (Microsoft Learn) · accessed November 16, 2026
