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.
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
- Microsoft Graph and the Defender Streaming API to Integration poller
- Integration poller to index=endpoint
- Integration poller to index=network
- Integration poller to index=email
- 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 LogPulse | Where you find it |
|---|---|
| Tenant ID | Your Microsoft Entra directory (tenant) ID. |
| Client ID (Application ID) | The Application (client) ID of the app registration. |
| Client Secret | Needs 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.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| Alerts (all Defender products) | endpoint | microsoft_defender | ms_defender_alert | Every Defender XDR alert via Microsoft Graph: Endpoint, Office 365, Identity, Cloud Apps and Entra ID Protection. |
| Process events | endpoint | microsoft_defender | ms_defender_process | DeviceProcessEvents from the Streaming API: every process start on onboarded devices. |
| Registry events | endpoint | microsoft_defender | ms_defender_registry | DeviceRegistryEvents: keys and values set or deleted. |
| Logon events | endpoint | microsoft_defender | ms_defender_logon | DeviceLogonEvents: local, network and RDP logons, success and failure. |
| Other device events | endpoint | microsoft_defender | ms_defender_event | DeviceEvents and DeviceImageLoadEvents: scheduled tasks, services, antivirus detections, tampering, loaded modules. |
| Network events (off by default) | network | microsoft_defender | ms_defender_network | DeviceNetworkEvents: connections per process. High volume. |
| File events (off by default) | endpoint | microsoft_defender | ms_defender_file | DeviceFileEvents: files created, changed, renamed and deleted. High volume. |
| Defender for Office 365 | email | microsoft_defender | ms_defender_email | EmailEvents, 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) | iam | microsoft_defender | ms_defender_identity | IdentityLogonEvents: logons against domain controllers and cloud apps. |
| Alert tables (Streaming API) (off by default) | endpoint | microsoft_defender | ms_defender_alert | AlertInfo 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.
Fields and data models
| Data model | What you get |
|---|---|
| Endpoint | Process, registry, file, network and task events with the same fields as the Windows agent, so the endpoint rules fire unchanged. |
| Mail flow with direction, verdict, DMARC, attachments, ZAP and URL clicks. | |
| Alert | One 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, sourcetypeThe 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 see | What 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.