Skip to content

Commit 4feb72c

Browse files
Merge pull request #310861 from MicrosoftDocs/main
Auto Publish – main to live - 2026-01-25 12:00 UTC
2 parents 8b3d0bb + a8af241 commit 4feb72c

2 files changed

Lines changed: 4 additions & 6 deletions

File tree

articles/sentinel/microsoft-365-defender-sentinel-integration.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: Microsoft Defender XDR integration with Microsoft Sentinel
33
description: Learn how using Microsoft Defender XDR together with Microsoft Sentinel lets you use Microsoft Sentinel as your universal incidents queue.
4-
author: batamig
5-
ms.author: bagol
4+
author: guywi-ms
5+
ms.author: guywild
66
ms.topic: conceptual
77
ms.date: 10/25/2025
88
appliesto:
@@ -120,7 +120,7 @@ If you want to sync Defender XDR data to Microsoft Sentinel in the Azure portal,
120120

121121
- First, install the **Microsoft Defender XDR** solution for Microsoft Sentinel from the **Content hub**. Then, enable the **Microsoft Defender XDR** data connector to collect incidents and alerts. For more information, see [Connect data from Microsoft Defender XDR to Microsoft Sentinel](connect-microsoft-365-defender.md).
122122

123-
- After you enable alert and incident collection in the Defender XDR data connector, Defender XDR incidents appear in the Microsoft Sentinel incidents queue shortly after they're generated in Defender XDR. It can take up to five minutes from the time an incident is generated in Defender XDR to the time it appears in Microsoft Sentinel. In these incidents, the **Alert product name** field contains **Microsoft Defender XDR** or one of the component Defender services' names.
123+
- After you enable alert and incident collection in the Defender XDR data connector, Defender XDR incidents appear in the Microsoft Sentinel incidents queue shortly after they're generated in Defender XDR. Under normal operating conditions, incidents generated in Defender XDR typically appear in the Microsoft Sentinel UI and API within five minutes. Ingestion into the `securityIncident` table might take a few more minutes. In these incidents, the **Alert product name** field contains **Microsoft Defender XDR** or one of the component Defender services' names.
124124

125125
### Ingestion costs
126126

articles/sentinel/whats-new.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,9 +47,7 @@ You can now enable UEBA for supported data sources directly from the data connec
4747

4848
This integration allows you to see which data sources feed into UEBA and enable that feed directly from the connector configuration.
4949

50-
For more information, see:
51-
52-
- [Connect data sources to Microsoft Sentinel by using data connectors](configure-data-connector.md#enable-user-and-entity-behavior-analytics-ueba-from-supported-connectors)
50+
For more information, see [Connect data sources to Microsoft Sentinel by using data connectors](configure-data-connector.md#enable-user-and-entity-behavior-analytics-ueba-from-supported-connectors).
5351

5452

5553
### New detections for Sentinel solution for SAP BTP

0 commit comments

Comments
 (0)