From a153eb774efb07f6410fdeae4db9ba4cd5f2e54e Mon Sep 17 00:00:00 2001 From: jcaparas Date: Tue, 3 Apr 2018 11:25:41 -0700 Subject: [PATCH] fix numbering --- ...hine-groups-windows-defender-advanced-threat-protection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-atp/machine-groups-windows-defender-advanced-threat-protection.md b/windows/security/threat-protection/windows-defender-atp/machine-groups-windows-defender-advanced-threat-protection.md index b4e6bdb23d..64234e4330 100644 --- a/windows/security/threat-protection/windows-defender-atp/machine-groups-windows-defender-advanced-threat-protection.md +++ b/windows/security/threat-protection/windows-defender-atp/machine-groups-windows-defender-advanced-threat-protection.md @@ -66,8 +66,8 @@ As part of the process of creating a machine group, you'll: 5. Assign the user groups that can access the machine group you created. ->[!NOTE] ->You can only grant access to Azure AD user groups with assigned RBAC roles. + >[!NOTE] + >You can only grant access to Azure AD user groups with assigned RBAC roles. 6. Click **Close**.