Skip to content

Commit 6093c77

Browse files
authored
Merge pull request #6153 from Brenduns/quick-fix
minor edit to ease cross-repo include use
2 parents f7b1384 + 30662f3 commit 6093c77

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

memdocs/intune/protect/mde-security-integration.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,7 @@ This scenario extends the Microsoft Endpoint Manager Endpoint Security surface t
4545

4646
:::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":::
4747

48-
## Prerequisites
49-
50-
Review the following sections for requirements for the Security Management for Microsoft Defender for Endpoint Scenario:
51-
52-
### High-level flow
48+
**High-level flow**:
5349

5450
When a device onboards to Microsoft Defender for Endpoint and security management is enabled:
5551

@@ -59,6 +55,10 @@ When a device onboards to Microsoft Defender for Endpoint and security managemen
5955
- Azure Active Directory trust is used to communicate with Endpoint Manager (Intune) and retrieve policies
6056
- Policy retrieve from Endpoint Manager is enforced on the device by Microsoft Defender for Endpoint
6157

58+
## Prerequisites
59+
60+
Review the following sections for requirements for the Security Management for Microsoft Defender for Endpoint Scenario:
61+
6262
### Active Directory Requirements
6363

6464
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

Comments
 (0)