Send Microsoft Entra ID logs to LogPulse

Sign-in logs and directory audit logs from Microsoft Entra ID through the Microsoft Graph API.

In short
To send Microsoft Entra ID logs to LogPulse, add Microsoft Entra ID under Configure → Sources → Cloud. LogPulse reads the Microsoft Graph API itself, without an agent. Events land in the iam index with source azure and fill the Authentication, Cloud Audit data models.

Overview

How Microsoft Entra ID data reaches LogPulse
Vendor
Microsoft Graph API
Collect
Integration pollerreads new events, maps the fields
Store
index=iam
  1. Microsoft Graph API to Integration poller
  2. Integration poller to index=iam

LogPulse signs in to Microsoft Entra ID with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.

What you need

  • Entra ID app registration (Tenant ID, Client ID, Client Secret)
  • Application permissions: AuditLog.Read.All and Directory.Read.All
  • Admin consent granted for the application permissions
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in Microsoft Entra ID

Field in LogPulseWhere you find it
Tenant IDYour Entra ID Directory (tenant) ID.
Client ID (application ID)The Application (client) ID of an app registration.
Client secretA client secret of that app registration. It needs the application permissions AuditLog.Read.All and Directory.Read.All with admin consent. Stored encrypted and never shown again.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose Microsoft Entra ID. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.

Tip: Secrets are stored encrypted and never shown again. To change one, paste a new value; the rest stays.

What arrives

Data sourceIndexSourceSourcetypeWhat it holds
Sign-in Logsiamazureazure:signinInteractive and non-interactive user sign-ins: user, source IP, location, app, MFA, and success/failure. Normalized to the Authentication data model.
Directory Audit Logsiamazureazure:auditDirectory changes: user/group/role management, policy changes, application and credential events. Normalized to the Cloud Audit data model.

The index is the kind of data and the source is the product, so detection rules for that kind of data find Microsoft Entra ID without changes.

Note: Sign-ins and directory audit land in the same index, source and sourcetypes as the Azure Event Hub integration, so rules fire on both. Use one of the two for Entra ID, not both, or you get every event twice.

Fields and data models

Data modelWhat you get
AuthenticationUser sign-ins with user, action, source IP, country, app, MFA and user agent.
Cloud AuditDirectory changes (users, groups, roles, policies) with action, outcome, actor and resource.

Events are mapped to the data models above, with the same field names as other sources of the same kind. See field names.

3. Check the data

The first events arrive within a few minutes. Check what came in:

earliest=-1h index IN (iam) source IN (azure)
| stats count by index, source, sourcetype

The integration page in LogPulse shows when it last read events and the last error, if any.

Troubleshooting

The connection test names what is wrong. These are the answers you are most likely to see.

What you seeWhat to do
App registration lacks the "AuditLog.Read.All" (and "Directory.Read.All") application permission, or admin consent has not been granted.Add both as application permissions on Microsoft Graph and press Grant admin consent.
Could not reach Microsoft Entra ID.Check the tenant ID, client ID and client secret. A client secret expires; create a new one when it has.
The test passes but no events arrive.Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Microsoft Entra ID may also simply have had nothing new.

Frequently asked questions

How do I send Microsoft Entra ID logs to LogPulse?
Add the Microsoft Entra ID cloud integration under Configure, Sources, Cloud in LogPulse and fill in Tenant ID, Client ID (application ID), Client secret. LogPulse reads the Microsoft Graph API itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in Microsoft Entra ID?
Entra ID app registration (Tenant ID, Client ID, Client Secret). Application permissions: AuditLog.Read.All and Directory.Read.All. Admin consent granted for the application permissions. Read access is enough for collecting logs.
Which index does Microsoft Entra ID data go to?
The index is the kind of data: iam. The source is the product: azure. Each data source has its own sourcetype, listed on this page.
Which data models does Microsoft Entra ID fill?
Authentication, Cloud Audit. Detection rules and dashboards written for a data model work on Microsoft Entra ID without changes.
Entra ID integration or Azure Event Hub?
This integration needs only an app registration and reads sign-ins and directory audit through Microsoft Graph. The Azure Event Hub integration also brings the Activity Log, Azure Firewall and other resource logs. Both write sign-ins to the same index and sourcetype, so use one of them for Entra ID.