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: memdocs/intune/protect/mde-security-integration.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,20 +45,20 @@ This scenario extends the Microsoft Endpoint Manager Endpoint Security surface t
45
45
46
46
:::image type="content" source="./media/mde-security-integration/endpoint-security-overview.png" alt-text="Conceptual diagram of the MDE-Attach solution." lightbox="./media/mde-security-integration/endpoint-security-overview.png":::
47
47
48
-
**High-level flow**:
48
+
## Prerequisites
49
+
50
+
Review the following sections for requirements for the Security Management for Microsoft Defender for Endpoint Scenario:
51
+
52
+
### Environment
49
53
50
-
When a device onboards to Microsoft Defender for Endpoint and security management is enabled:
54
+
When a device onboards to Microsoft Defender for Endpoint:
51
55
52
56
- The device is surveyed for an existing Endpoint Manager presence, which is a mobile device management (MDM) enrollment to Intune
53
57
- Devices without an Endpoint Manager presence will enable the Security Management feature
54
58
- A trust is created with Azure Active Directory if one doesn't already exist
55
59
- Azure Active Directory trust is used to communicate with Endpoint Manager (Intune) and retrieve policies
56
60
- Policy retrieve from Endpoint Manager is enforced on the device by Microsoft Defender for Endpoint
57
61
58
-
## Prerequisites
59
-
60
-
Review the following sections for requirements for the Security Management for Microsoft Defender for Endpoint Scenario:
61
-
62
62
### Active Directory Requirements
63
63
64
64
When a device that is domain joined creates a trust with Azure Active Directory, this scenario is referred to as a *Hybrid Azure Active Directory Join* scenario. The Security Management for MDE fully supports this scenario with the following requirements:
0 commit comments