Send Microsoft Defender XDR logs to LogPulse

Alerts from every Defender product through Microsoft Graph, and the advanced hunting tables (process, registry, logon, email, identity) through the Streaming API.

In short
To send Microsoft Defender XDR logs to LogPulse, add Microsoft Defender XDR under Configure → Sources → Cloud. LogPulse reads the Microsoft Graph and the Defender Streaming API itself, without an agent. Events land in the endpoint, network, email, iam indexes with source microsoft_defender and fill the Endpoint, Email, Alert data models.

Overview

How Microsoft Defender XDR data reaches LogPulse
Vendor
Microsoft Graph and the Defender Streaming API
Collect
Integration pollerreads new events, maps the fields
Store
index=endpoint
index=network
index=email
index=iam
  1. Microsoft Graph and the Defender Streaming API to Integration poller
  2. Integration poller to index=endpoint
  3. Integration poller to index=network
  4. Integration poller to index=email
  5. Integration poller to index=iam

LogPulse signs in to Microsoft Defender XDR 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 permission SecurityAlert.Read.All (Microsoft Graph) with admin consent
  • For events: the Streaming API sending to a storage account, and an account SAS URL with List and Read
  • Defender for Office 365 Plan 2 or E5 for the email tables
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in Microsoft Defender XDR

Field in LogPulseWhere you find it
Tenant IDYour Microsoft Entra directory (tenant) ID.
Client ID (Application ID)The Application (client) ID of the app registration.
Client SecretNeeds the SecurityAlert.Read.All application permission on Microsoft Graph with admin consent. Stored encrypted and never shown again.
Storage account SAS URL (optional)For device, email and identity events. In the Defender portal: Settings, Microsoft Defender XDR, Streaming API, add a storage account destination. Then create an account SAS on that account: Blob service, Container and Object, List and Read. Only needed when you turn on a Streaming API source. Stored encrypted and never shown again.
Isolation app: Client ID (optional)A separate app with the Machine.Isolate and Machine.Read.All application permissions on WindowsDefenderATP (APIs my organization uses), with admin consent.
Isolation app: Client Secret (optional)Stored encrypted and never shown again.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose Microsoft Defender XDR. 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
Alerts (all Defender products)endpointmicrosoft_defenderms_defender_alertEvery Defender XDR alert via Microsoft Graph: Endpoint, Office 365, Identity, Cloud Apps and Entra ID Protection.
Process eventsendpointmicrosoft_defenderms_defender_processDeviceProcessEvents from the Streaming API: every process start on onboarded devices.
Registry eventsendpointmicrosoft_defenderms_defender_registryDeviceRegistryEvents: keys and values set or deleted.
Logon eventsendpointmicrosoft_defenderms_defender_logonDeviceLogonEvents: local, network and RDP logons, success and failure.
Other device eventsendpointmicrosoft_defenderms_defender_eventDeviceEvents and DeviceImageLoadEvents: scheduled tasks, services, antivirus detections, tampering, loaded modules.
Network events (off by default)networkmicrosoft_defenderms_defender_networkDeviceNetworkEvents: connections per process. High volume.
File events (off by default)endpointmicrosoft_defenderms_defender_fileDeviceFileEvents: files created, changed, renamed and deleted. High volume.
Defender for Office 365emailmicrosoft_defenderms_defender_emailEmailEvents, attachments, URLs, post-delivery actions (ZAP) and Safe Links clicks. Needs Defender for Office 365 Plan 2 or E5.
Defender for Identity (off by default)iammicrosoft_defenderms_defender_identityIdentityLogonEvents: logons against domain controllers and cloud apps.
Alert tables (Streaming API) (off by default)endpointmicrosoft_defenderms_defender_alertAlertInfo and AlertEvidence via the Streaming API, for when you do not want to grant SecurityAlert.Read.All.

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

Note: The Streaming API writes to a storage account in your own Azure subscription. LogPulse reads new lines from it with a read-only SAS URL; without a SAS URL only the alerts are read.
Note: The email tables need Defender for Office 365 Plan 2 or E5.
Note: The isolation app is optional and separate: it is only used when you let LogPulse isolate a device as a response action.

Fields and data models

Data modelWhat you get
EndpointProcess, registry, file, network and task events with the same fields as the Windows agent, so the endpoint rules fire unchanged.
EmailMail flow with direction, verdict, DMARC, attachments, ZAP and URL clicks.
AlertOne alert shape for every EDR: alert_id, alert_name, severity, hostname, user, techniques.

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

The original record of Microsoft Defender XDR is kept with each event under raw, so nothing the vendor sent is lost.

3. Check the data

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

earliest=-1h index IN (endpoint, network, email, iam) source IN (microsoft_defender)
| 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
Authentication failed. Check the Tenant ID, Client ID and Client Secret.Copy the three values again from the app registration. A client secret expires; create a new one when it has.
The app lacks the SecurityAlert.Read.All application permission on Microsoft Graph, or admin consent is missing.Add SecurityAlert.Read.All as an application permission (not delegated) and press Grant admin consent.
The SAS URL was refused: it needs the Blob service, Container and Object resource types, List and Read permissions, and must not be expired.Create a new account SAS on the storage account with exactly those settings and an end date far enough ahead.
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 Defender XDR may also simply have had nothing new.

Frequently asked questions

How do I send Microsoft Defender XDR logs to LogPulse?
Add the Microsoft Defender XDR cloud integration under Configure, Sources, Cloud in LogPulse and fill in Tenant ID, Client ID (Application ID), Client Secret. LogPulse reads the Microsoft Graph and the Defender Streaming API itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in Microsoft Defender XDR?
Entra ID app registration (Tenant ID, Client ID, Client Secret). Application permission SecurityAlert.Read.All (Microsoft Graph) with admin consent. For events: the Streaming API sending to a storage account, and an account SAS URL with List and Read. Defender for Office 365 Plan 2 or E5 for the email tables. Read access is enough for collecting logs.
Which index does Microsoft Defender XDR data go to?
The index is the kind of data: endpoint, network, email, iam. The source is the product: microsoft_defender. Each data source has its own sourcetype, listed on this page.
Which data models does Microsoft Defender XDR fill?
Endpoint, Email, Alert. Detection rules and dashboards written for a data model work on Microsoft Defender XDR without changes.
Why is a data source off by default?
To keep your daily ingest down until you need it: Network events, File events, Defender for Identity, Alert tables (Streaming API) are high volume or of use to fewer teams. Tick the data source in the integration to switch it on.
Do I need the Streaming API for Defender alerts?
No. Alerts come through Microsoft Graph with only the app registration. The Streaming API and the storage account SAS URL are for the process, registry, logon, email and identity events.