From bf80138e9ac9c3e10d1cf355956877ff84f3ea71 Mon Sep 17 00:00:00 2001 From: amirsc3 <42802974+amirsc3@users.noreply.github.com> Date: Mon, 2 Nov 2020 16:53:57 +0200 Subject: [PATCH 1/4] Update commercial-gov.md Fixing typo to avoid customer confusion. Some customers have opened support tickets because they could not understand from the above phrase which "patch" is referred to in this note. --- .../threat-protection/microsoft-defender-atp/commercial-gov.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md b/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md index d4c8c750c8..66906b90f1 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md +++ b/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md @@ -40,7 +40,7 @@ The following OS versions are supported: - Windows Server, 2019 (with [KB4490481](https://support.microsoft.com/en-us/help/4490481)) >[!NOTE] ->A patch must be deployed before device onboarding in order to configure Microsoft Defender ATP to the correct environment. +>The above mentioned patch level must be deployed before device onboarding in order to configure Microsoft Defender ATP to the correct environment. The following OS versions are supported via Azure Security Center: - Windows Server 2008 R2 SP1 From ee532821ad7be217dfc5ddbfca6c4fdc85f99957 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Mon, 2 Nov 2020 11:54:30 -0800 Subject: [PATCH 2/4] update loc tag as per request --- .../microsoft-defender-smartscreen-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md b/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md index b39153d62c..386550279a 100644 --- a/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md +++ b/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md @@ -9,7 +9,7 @@ ms.pagetype: security author: mjcaparas ms.author: macapara audience: ITPro -ms.localizationpriority: medium +ms.localizationpriority: high ms.date: 11/27/2019 ms.reviewer: manager: dansimp From 644d5672a7f6260ed491cb7e678873d228f947a1 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Mon, 2 Nov 2020 13:48:09 -0800 Subject: [PATCH 3/4] Removed "/en-us" --- .../microsoft-defender-atp/commercial-gov.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md b/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md index 66906b90f1..b4b47744f4 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md +++ b/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md @@ -34,10 +34,10 @@ This offering is currently available to US Office 365 GCC High customers and is The following OS versions are supported: - Windows 10, version 1903 -- Windows 10, version 1809 (OS Build 17763.404 with [KB4490481](https://support.microsoft.com/en-us/help/4490481)) +- Windows 10, version 1809 (OS Build 17763.404 with [KB4490481](https://support.microsoft.com/help/4490481)) - Windows 10, version 1803 (OS Build 17134.799 with [KB4499183](https://support.microsoft.com/help/4499183)) - Windows 10, version 1709 (OS Build 16299.1182 with [KB4499147](https://support.microsoft.com/help/4499147)) -- Windows Server, 2019 (with [KB4490481](https://support.microsoft.com/en-us/help/4490481)) +- Windows Server, 2019 (with [KB4490481](https://support.microsoft.com/help/4490481)) >[!NOTE] >The above mentioned patch level must be deployed before device onboarding in order to configure Microsoft Defender ATP to the correct environment. From c6b904db8394d5c1aba067499716eb7498e81e22 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Mon, 2 Nov 2020 13:55:49 -0800 Subject: [PATCH 4/4] update supported endpoint --- .../microsoft-defender-atp/configure-endpoints-vdi.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md b/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md index 03c9870858..95305f3a79 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md +++ b/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md @@ -39,9 +39,9 @@ ms.date: 04/16/2020 Microsoft Defender ATP supports non-persistent VDI session onboarding. >[!Note] ->To onboard non-persistent VDI sessions, VDI devices must be on Windows 10. +>To onboard non-persistent VDI sessions, VDI devices must be Windows 10 or Windows Server 2019. > ->While other Windows versions might work, only Windows 10 is supported. +>While other Windows versions might work, only Windows 10 and Windows Server 2019 are supported. There might be associated challenges when onboarding VDIs. The following are typical challenges for this scenario: