From 2cdf79009321e1032136ef927a806ced4c7deef0 Mon Sep 17 00:00:00 2001 From: "Andrea Bichsel (Aquent LLC)" Date: Wed, 2 May 2018 11:22:46 -0700 Subject: [PATCH] Fix formatting --- ...configure-block-at-first-sight-windows-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-antivirus/configure-block-at-first-sight-windows-defender-antivirus.md b/windows/security/threat-protection/windows-defender-antivirus/configure-block-at-first-sight-windows-defender-antivirus.md index c2f08b09d3..d5bdf282dc 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/configure-block-at-first-sight-windows-defender-antivirus.md +++ b/windows/security/threat-protection/windows-defender-antivirus/configure-block-at-first-sight-windows-defender-antivirus.md @@ -66,7 +66,7 @@ Block at First Sight requires a number of Group Policy settings to be configured ### Confirm Block at First Sight is enabled with Intune -1. In Intune, navigate to **Device configuration - Profiles | *Profile name* | Device restrictions | Windows Defender Antivirus**. +1. In Intune, navigate to **Device configuration - Profiles > *Profile name* > Device restrictions > Windows Defender Antivirus**. > [!NOTE] > The profile you select must be a Device Restriction profile type, not an Endpoint Protection profile type.