You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sentinel/connect-microsoft-365-defender.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,9 @@
2
2
title: Connect Microsoft 365 Defender data to Microsoft Sentinel| Microsoft Docs
3
3
description: Learn how to ingest incidents, alerts, and raw event data from Microsoft 365 Defender into Microsoft Sentinel.
4
4
author: yelevin
5
-
ms.topic: conceptual
6
-
ms.date: 03/23/2022
7
5
ms.author: yelevin
8
-
ms.service: microsoft-sentinel
6
+
ms.topic: conceptual
7
+
ms.date: 02/01/2023
9
8
---
10
9
11
10
# Connect data from Microsoft 365 Defender to Microsoft Sentinel
@@ -20,7 +19,7 @@ For more information about incident integration and advanced hunting event colle
20
19
21
20
> [!IMPORTANT]
22
21
>
23
-
> The Microsoft 365 Defender connector is currently in **PREVIEW**. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
22
+
> The Microsoft 365 Defender connector is now generally available!
24
23
25
24
## Prerequisites
26
25
@@ -30,6 +29,8 @@ For more information about incident integration and advanced hunting event colle
30
29
31
30
- Your user must have read and write permissions on your Microsoft Sentinel workspace.
32
31
32
+
- To make any changes to the connector settings, your user must be a member of the same Azure Active Directory tenant with which your Microsoft Sentinel workspace is associated.
33
+
33
34
### Prerequisites for Active Directory sync via MDI
34
35
35
36
- Your tenant must be onboarded to Microsoft Defender for Identity.
@@ -38,7 +39,7 @@ For more information about incident integration and advanced hunting event colle
38
39
39
40
## Connect to Microsoft 365 Defender
40
41
41
-
In Microsoft Sentinel, select **Data connectors**, select **Microsoft 365 Defender (Preview)** from the gallery and select **Open connector page**.
42
+
In Microsoft Sentinel, select **Data connectors**, select **Microsoft 365 Defender** from the gallery and select **Open connector page**.
Copy file name to clipboardExpand all lines: articles/sentinel/microsoft-365-defender-cloud-support.md
+68-44Lines changed: 68 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
title: Support for Microsoft 365 Defender connector data types in Microsoft Sentinel for different clouds (GCC environments)
3
3
description: This article describes support for different Microsoft 365 Defender connector data types in Microsoft Sentinel across different clouds, including Commercial, GCC, GCC-High, and DoD.
4
4
author: limwainstein
5
-
ms.topic: reference
6
-
ms.date: 11/14/2022
7
5
ms.author: lwainstein
6
+
ms.topic: reference
7
+
ms.date: 02/01/2023
8
8
---
9
9
10
10
# Support for Microsoft 365 Defender connector data types in different clouds
@@ -13,64 +13,88 @@ The type of cloud your environment uses affects Microsoft Sentinel's ability to
13
13
14
14
Read more about [data type support for different clouds in Microsoft Sentinel](data-type-cloud-support.md).
15
15
16
-
## Microsoft Defender for Endpoint
16
+
## Connector data
17
+
18
+
### Incidents
19
+
20
+
| Data type | Commercial / GCC<br>(Azure Commercial) | GCC-High / DoD<br>(Azure Government) |
|SecurityIncident |Microsoft Sentinel: Public Preview |Microsoft Sentinel: Public Preview |Microsoft Sentinel: Public Preview |Microsoft Sentinel: Public Preview |
75
+
| Data type | Commercial / GCC<br>(Azure Commercial) | GCC-High / DoD<br>(Azure Government) |
Copy file name to clipboardExpand all lines: articles/sentinel/microsoft-365-defender-sentinel-integration.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,9 @@
2
2
title: Microsoft 365 Defender integration with Microsoft Sentinel | Microsoft Docs
3
3
description: Learn how using Microsoft 365 Defender together with Microsoft Sentinel lets you use Microsoft Sentinel as your universal incidents queue while seamlessly applying Microsoft 365 Defender's strengths to help investigate Microsoft 365 security incidents. Also, learn how to ingest Defender components' advanced hunting data into Microsoft Sentinel.
4
4
author: yelevin
5
-
ms.topic: conceptual
6
-
ms.date: 03/23/2022
7
5
ms.author: yelevin
8
-
ms.service: microsoft-sentinel
6
+
ms.topic: conceptual
7
+
ms.date: 02/01/2023
9
8
---
10
9
11
10
# Microsoft 365 Defender integration with Microsoft Sentinel
@@ -14,10 +13,10 @@ Microsoft Sentinel's [Microsoft 365 Defender](/microsoft-365/security/mtp/micros
14
13
15
14
This integration gives Microsoft 365 security incidents the visibility to be managed from within Microsoft Sentinel, as part of the primary incident queue across the entire organization, so you can see – and correlate – Microsoft 365 incidents together with those from all of your other cloud and on-premises systems. At the same time, it allows you to take advantage of the unique strengths and capabilities of Microsoft 365 Defender for in-depth investigations and a Microsoft 365-specific experience across the Microsoft 365 ecosystem. Microsoft 365 Defender enriches and groups alerts from multiple Microsoft 365 products, both reducing the size of the SOC’s incident queue and shortening the time to resolve. The component services that are part of the Microsoft 365 Defender stack are:
16
15
17
-
-**Microsoft Defender for Endpoint** (formerly Microsoft Defender ATP)
18
-
-**Microsoft Defender for Identity** (formerly Azure ATP)
19
-
-**Microsoft Defender for Office 365** (formerly Office 365 ATP)
20
-
-**Microsoft Defender for Cloud Apps** (formerly Microsoft Cloud App Security)
16
+
-**Microsoft Defender for Endpoint (MDE)**
17
+
-**Microsoft Defender for Identity (MDI)**
18
+
-**Microsoft Defender for Office 365 (MDO)**
19
+
-**Microsoft Defender for Cloud Apps (MDA)**
21
20
22
21
Other services whose alerts are collected by Microsoft 365 Defender include:
23
22
@@ -27,7 +26,7 @@ Other services whose alerts are collected by Microsoft 365 Defender include:
27
26
In addition to collecting alerts from these components and other services, Microsoft 365 Defender generates alerts of its own. It creates incidents from all of these alerts and sends them to Microsoft Sentinel.
28
27
29
28
> [!IMPORTANT]
30
-
> The Microsoft 365 Defender connector is currently in **PREVIEW**. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
29
+
> The Microsoft 365 Defender connector is now generally available!
31
30
32
31
## Common use cases and scenarios
33
32
@@ -58,9 +57,6 @@ Once the Microsoft 365 Defender integration is connected, the connectors for all
58
57
59
58
- To avoid creating duplicate incidents for the same alerts, we recommend that customers turn off all **Microsoft incident creation rules** for Microsoft 365 Defender-integrated products (Defender for Endpoint, Defender for Identity, Defender for Office 365, Defender for Cloud Apps, and Azure Active Directory Identity Protection) when connecting Microsoft 365 Defender. This can be done by disabling incident creation in the connector page. Keep in mind that if you do this, any filters that were applied by the incident creation rules will not be applied to Microsoft 365 Defender incident integration.
60
59
61
-
> [!NOTE]
62
-
> All Microsoft Defender for Cloud Apps alert types are now being onboarded to Microsoft 365 Defender.
63
-
64
60
## Working with Microsoft 365 Defender incidents in Microsoft Sentinel and bi-directional sync
65
61
66
62
Microsoft 365 Defender incidents will appear in the Microsoft Sentinel incidents queue with the product name **Microsoft 365 Defender**, and with similar details and functionality to any other Sentinel incidents. Each incident contains a link back to the parallel incident in the Microsoft 365 Defender portal.
@@ -89,4 +85,5 @@ The Microsoft 365 Defender connector also lets you stream **advanced hunting** e
89
85
In this document, you learned how to benefit from using Microsoft 365 Defender together with Microsoft Sentinel, using the Microsoft 365 Defender connector.
90
86
91
87
- Get instructions for [enabling the Microsoft 365 Defender connector](connect-microsoft-365-defender.md).
92
-
- Create [custom alerts](detect-threats-custom.md) and [investigate incidents](investigate-cases.md).
88
+
- Check [availability of different Microsoft 365 Defender data types](microsoft-365-defender-cloud-support.md) in the different Microsoft 365 and Azure clouds.
89
+
- Create [custom alerts](detect-threats-custom.md) and [investigate incidents](investigate-incidents.md).
0 commit comments