Skip to content

Commit 3f6661f

Browse files
committed
Connect XDR connector - fix acrolinx, add links, edits
1 parent 90bb618 commit 3f6661f

File tree

2 files changed

+64
-56
lines changed

2 files changed

+64
-56
lines changed

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

Lines changed: 21 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,14 @@ author: yelevin
55
ms.author: yelevin
66
ms.topic: conceptual
77
ms.date: 06/11/2023
8+
appliesto:
9+
- Microsoft Sentinel in the Azure portal and the Microsoft Defender portal
10+
ms.collection: usx-security
811
---
912

1013
# Connect data from Microsoft Defender XDR to Microsoft Sentinel
1114

12-
The Microsoft Defender XDR connector for Microsoft Sentinel allows you to stream all Microsoft Defender XDR incidents and alerts into Microsoft Sentinel. This connector keeps the incidents synchronized between both portals. Microsoft Defender XDR incidents include all their alerts, entities, and other relevant information. The incidents can also include alerts from the Microsoft Defender products and services. For more information, see [Microsoft Defender XDR integration with Microsoft Sentinel](microsoft-365-defender-sentinel-integration.md#advanced-hunting-event-collection).
15+
The Microsoft Defender XDR connector for Microsoft Sentinel allows you to stream all Microsoft Defender XDR incidents, alerts, and advanced hunting events into Microsoft Sentinel. This connector keeps the incidents synchronized between both portals. Microsoft Defender XDR incidents include all their alerts, entities, and other relevant information. The incidents can also include alerts from the Microsoft Defender products and services. For more information, see [Microsoft Defender XDR integration with Microsoft Sentinel](microsoft-365-defender-sentinel-integration.md#advanced-hunting-event-collection).
1316

1417
[!INCLUDE [unified-soc-preview](includes/unified-soc-preview.md)]
1518

@@ -44,37 +47,33 @@ The **Configuration** section has three parts:
4447

4548
1. [**Connect events**](#connect-events) enables the collection of raw advanced hunting events from Defender components.
4649

47-
For more information, see [Microsoft Defender XDR integration with Microsoft Sentinel](microsoft-365-defender-sentinel-integration.md) for more information.
50+
For more information, see [Microsoft Defender XDR integration with Microsoft Sentinel](microsoft-365-defender-sentinel-integration.md).
4851

4952
### Connect incidents and alerts
5053

51-
To ingest and synchronize Microsoft Defender XDR incidents, with all their alerts, to your Microsoft Sentinel incidents queue:
54+
To ingest and synchronize Microsoft Defender XDR incidents with all their alerts to your Microsoft Sentinel incidents queue, complete the following steps.
5255

53-
1. Mark the check box labeled **Turn off all Microsoft incident creation rules for these products. Recommended**, to avoid duplication of incidents.
54-
(This check box will not appear once the Microsoft Defender XDR connector is connected.)
56+
1. Mark the check box labeled **Turn off all Microsoft incident creation rules for these products. Recommended**, to avoid duplication of incidents. This check box doesn't appear once the Microsoft Defender XDR connector is connected.
5557

5658
1. Select the **Connect incidents & alerts** button.
59+
1. Verify that Microsoft Sentinel is collecting Microsoft Defender XDR incident data. In Microsoft Sentinel **Logs** in the Azure portal, run the following statement in the query window:
5760

61+
```kusto
62+
SecurityIncident
63+
| where ProviderName == "Microsoft 365 Defender"
64+
```
5865

59-
> [!NOTE]
60-
> When you enable the Microsoft Defender XDR connector, all of the Microsoft Defender XDR components’ connectors (the ones mentioned at the beginning of this article) are automatically connected in the background. In order to disconnect one of the components’ connectors, you must first disconnect the Microsoft Defender XDR connector.
61-
62-
To query Microsoft Defender XDR incident data, use the following statement in the query window:
63-
64-
```kusto
65-
SecurityIncident
66-
| where ProviderName == "Microsoft 365 Defender"
67-
```
66+
When you enable the Microsoft Defender XDR connector, all of the Microsoft Defender XDR components’ connectors are automatically connected in the background. In order to disconnect one of the components’ connectors, you must first disconnect the Microsoft Defender XDR connector.
6867

6968
### Connect entities
7069

7170
Use Microsoft Defender for Identity to sync user entities from your on-premises Active Directory to Microsoft Sentinel.
7271

73-
Verify that you've satisfied the [prerequisites](#prerequisites-for-active-directory-sync-via-mdi) for syncing on-premises Active Directory users through Microsoft Defender for Identity (MDI).
72+
Verify that you satisfied the [prerequisites](#prerequisites-for-active-directory-sync-via-mdi) for syncing on-premises Active Directory users through Microsoft Defender for Identity (MDI).
7473

7574
1. Select the **Go the UEBA configuration page** link.
7675

77-
1. In the **Entity behavior configuration** page, if you haven't yet enabled UEBA, then at the top of the page, move the toggle to **On**.
76+
1. In the **Entity behavior configuration** page, if you didn't enable UEBA, then at the top of the page, move the toggle to **On**.
7877

7978
1. Mark the **Active Directory (Preview)** check box and select **Apply**.
8079

@@ -107,7 +106,7 @@ If you want to collect advanced hunting events from Microsoft Defender for Endpo
107106
|-|-|
108107
| **[EmailAttachmentInfo](/microsoft-365/security/defender/advanced-hunting-emailattachmentinfo-table)** | Information about files attached to emails |
109108
| **[EmailEvents](/microsoft-365/security/defender/advanced-hunting-emailevents-table)** | Microsoft 365 email events, including email delivery and blocking events |
110-
| **[EmailPostDeliveryEvents](/microsoft-365/security/defender/advanced-hunting-emailpostdeliveryevents-table)** | Security events that occur post-delivery, after Microsoft 365 has delivered the emails to the recipient mailbox |
109+
| **[EmailPostDeliveryEvents](/microsoft-365/security/defender/advanced-hunting-emailpostdeliveryevents-table)** | Security events that occur post-delivery, after Microsoft 365 delivered the emails to the recipient mailbox |
111110
| **[EmailUrlInfo](/microsoft-365/security/defender/advanced-hunting-emailurlinfo-table)** | Information about URLs on emails |
112111

113112
# [Defender for Identity](#tab/MDI)
@@ -134,13 +133,13 @@ If you want to collect advanced hunting events from Microsoft Defender for Endpo
134133

135134
---
136135

137-
1. Click **Apply Changes**.
136+
1. Select **Apply Changes**.
138137

139-
1. To query the advanced hunting tables in Log Analytics, enter the table name from the list above in the query window.
138+
1. To query the advanced hunting tables in Log Analytics, enter the table name in the query window.
140139

141140
## Verify data ingestion
142141

143-
The data graph in the connector page indicates that you are ingesting data. You'll notice that it shows one line each for incidents, alerts, and events, and the events line is an aggregation of event volume across all enabled tables. Once you have enabled the connector, you can use the following KQL queries to generate more specific graphs.
142+
The data graph in the connector page indicates that you're ingesting data. Notice that it shows one line each for incidents, alerts, and events, and the events line is an aggregation of event volume across all enabled tables. Once you enabled the connector, use the following KQL queries to generate more specific graphs.
144143

145144
Use the following KQL query for a graph of the incoming Microsoft Defender XDR incidents:
146145

@@ -175,11 +174,8 @@ let Now = now();
175174
| render timechart
176175
```
177176

178-
In the **Next steps** tab, you’ll find some useful workbooks, sample queries, and analytics rule templates that have been included. You can run them on the spot or modify and save them.
179-
180177
## Next steps
181178

182-
In this document, you learned how to integrate Microsoft Defender XDR incidents, and advanced hunting event data from Microsoft Defender component services, into Microsoft Sentinel, using the Microsoft Defender XDR connector. To learn more about Microsoft Sentinel, see the following articles:
179+
In this document, you learned how to integrate Microsoft Defender XDR incidents, alerts, and advanced hunting event data from Microsoft Defender services, into Microsoft Sentinel, by using the Microsoft Defender XDR connector.
183180

184-
- Learn how to [get visibility into your data, and potential threats](get-visibility.md).
185-
- Get started [detecting threats with Microsoft Sentinel](./detect-threats-built-in.md).
181+
To use Microsoft Sentinel integrated with Defender XDR in the unified security operations platform, see [Connect data from Microsoft Defender XDR to Microsoft Sentinel](connect-microsoft-365-defender.md).

0 commit comments

Comments
 (0)