Skip to content

Commit deda31f

Browse files
authored
Moving the : to preceed the image, after the new step.
1 parent 3353c9c commit deda31f

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

memdocs/intune/protect/includes/security-config-mgt-prerequisites.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -116,8 +116,8 @@ To support Microsoft Defender for Endpoint security configuration management thr
116116

117117
1. Sign in to [Microsoft 365 Defender portal](https://security.microsoft.com/) and go to **Settings** > **Endpoints** > **Configuration Management** > **Enforcement Scope** and enable the platforms for security settings management:
118118
:::image type="content" source="../media/mde-security-integration/enable-mde-settings-management-defender.png" alt-text="Enable Microsoft Defender for Endpoint settings management in the Microsoft 365 Defender portal.":::
119-
1. Configure Pilot Mode and Configuration Manager authority settings to fit your organization needs:
120-
2. Uncheck both **Windows Client devices** and **Windows Server devices** to be able to use Pilot Mode using tagging.
119+
1. Configure Pilot Mode and Configuration Manager authority settings to fit your organization needs.
120+
1. Uncheck both **Windows Client devices** and **Windows Server devices** to be able to use Pilot Mode using tagging:
121121
:::image type="content" source="../media/mde-security-integration/pilot-CMAuthority-mde-settings-management-defender.png" alt-text="Configure Pilot mode for Endpoint settings management in the Microsoft 365 Defender portal.":::
122122
> [!TIP]
123123
> Use pilot mode and the proper device tags to test and validate your rollout on a small number of devices. Without using pilot mode, any device that falls into the scope configured will automatically be enrolled.

0 commit comments

Comments
 (0)