Configure Event Collection
In brief
The documentation now states that Microsoft Defender identity security detections require millisecond data and updates the page date. The QRadar agentless Windows event collection prerequisite and reference link remain.
What Defender admins need to know
Administrators can more clearly understand why millisecond event data is required when configuring QRadar collection.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
QRadar enables event collection via an agent. If the data is gathered using an agent, the time format is gathered without millisecond data.
Because identity security detections in Microsoft Defender for Identity needsrequire millisecond data, you must first configure QRadar to use agentless Windows event collection. For more information, see QRadar: Agentless Windows Events Collection using the MSRPC Protocol.
The following example shows a complete QRadar syslog message for Windows Security event 4776, collected agentlessly to preserve millisecond timestamp fidelity. Use this message syntax to configure your standalone sensor to listen for QRadar events:
@@ -13,7 +13,7 @@ ms.service: microsoft-defender-for-identity uhfHeaderId: MSDocsHeader-MicrosoftDefender ms.suite: ems description: Configure a Microsoft Defender for Identity standalone sensor to listen for supported SIEM event types, including the required message syntax and guidance for using extra Windows events to improve detections.-ms.date: 2026-07-02T00:00:00.0000000Z+ms.date: 2026-11-11T00:00:00.0000000Z ms.topic: how-to ms.reviewer: martin77s ai-usage: ai-assisted@@ -151,7 +151,7 @@ Error Code: 0x0
QRadar enables event collection via an agent. If the data is gathered using an agent, the time format is gathered without millisecond data.
-Because Defender for Identity needs millisecond data, you must first configure QRadar to use agentless Windows event collection. For more information, see [QRadar: Agentless Windows Events Collection using the MSRPC Protocol](https://www.ibm.com/support/pages/qradar-agentless-windows-events-collection-using-msrpc-protocol-msrpc-faq).
+Because identity security detections in Microsoft Defender require millisecond data, first configure QRadar to use agentless Windows event collection. For more information, see [QRadar: Agentless Windows Events Collection using the MSRPC Protocol](https://www.ibm.com/support/pages/qradar-agentless-windows-events-collection-using-msrpc-protocol-msrpc-faq).
The following example shows a complete QRadar syslog message for Windows Security event 4776, collected agentlessly to preserve millisecond timestamp fidelity. Use this message syntax to configure your standalone sensor to listen for QRadar events:
