From a5000d9a87891ce37bd420a087da56251e8c8fab Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Thu, 15 Feb 2018 17:21:17 -0800 Subject: [PATCH] section rename --- ...ver-endpoints-windows-defender-advanced-threat-protection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-atp/configure-server-endpoints-windows-defender-advanced-threat-protection.md b/windows/security/threat-protection/windows-defender-atp/configure-server-endpoints-windows-defender-advanced-threat-protection.md index 808f13b4ca..6f8b1c72b7 100644 --- a/windows/security/threat-protection/windows-defender-atp/configure-server-endpoints-windows-defender-advanced-threat-protection.md +++ b/windows/security/threat-protection/windows-defender-atp/configure-server-endpoints-windows-defender-advanced-threat-protection.md @@ -30,7 +30,7 @@ Windows Defender ATP supports the onboarding of the following servers: - Windows Server 2012 R2 - Windows Server 2016 -## Onboard server endpoints [MICHAL - SHOULD THIS BE JUST FOR 2012R2?] +## Onboard Windows Server 2012 R2 and Windows Server 2016 [MICHAL - SHOULD I JUST RENAME?] To onboard your servers to Windows Defender ATP, you’ll need to: