From 4639ae48f001b340d087d831fbe43fd61c199720 Mon Sep 17 00:00:00 2001
From: isbrahm <43386070+isbrahm@users.noreply.github.com>
Date: Fri, 31 Jul 2020 12:45:39 -0700
Subject: [PATCH] Correct server availability information

MI is not available on Server 2016
---
 ...ndows-defender-application-control-with-managed-installer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/threat-protection/windows-defender-application-control/use-windows-defender-application-control-with-managed-installer.md b/windows/security/threat-protection/windows-defender-application-control/use-windows-defender-application-control-with-managed-installer.md
index 8ad3ce6f98..2b4dd900b3 100644
--- a/windows/security/threat-protection/windows-defender-application-control/use-windows-defender-application-control-with-managed-installer.md
+++ b/windows/security/threat-protection/windows-defender-application-control/use-windows-defender-application-control-with-managed-installer.md
@@ -22,7 +22,7 @@ ms.date: 06/13/2018
 **Applies to:**
 
 - Windows 10
-- Windows Server 2016 and above
+- Windows Server 2019
 
 Creating and maintaining application execution control policies has always been challenging, and finding ways to address this issue has been a frequently-cited request for customers of AppLocker and Windows Defender Application Control (WDAC).
 This is especially true for enterprises with large, ever changing software catalogs.