From deec52f36cc60b85e6e88912b7f31c74677bbe42 Mon Sep 17 00:00:00 2001
From: Charles Inglis <32555877+cinglis-msft@users.noreply.github.com>
Date: Tue, 11 May 2021 12:29:58 -0400
Subject: [PATCH] Removing reference to registry keys

After conferring with SMEs on registry key vs. configuring thru GP/MDM, while it is best practice to configure through GP/MDM (because it can be audited), there isn't strictly any issue with configuring devices straight thru regkey (this is what the script does).
---
 .../update/update-compliance-configuration-manual.md           | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/windows/deployment/update/update-compliance-configuration-manual.md b/windows/deployment/update/update-compliance-configuration-manual.md
index beb8b237cd..ccdb293504 100644
--- a/windows/deployment/update/update-compliance-configuration-manual.md
+++ b/windows/deployment/update/update-compliance-configuration-manual.md
@@ -31,9 +31,6 @@ The requirements are separated into different categories:
 
 ## Required policies
 
-> [!NOTE]
-> Windows 10 MDM and Group Policies are backed by registry keys. It is not recommended you set these registry keys directly for configuration as it can lead to unexpected behavior, so the exact registry key locations are not provided, though they are referenced for troubleshooting configuration issues with the [Update Compliance Configuration Script](update-compliance-configuration-script.md).
-
 Update Compliance has a number of policies that must be appropriately configured in order for devices to be processed by Microsoft and visible in Update Compliance. They are enumerated below, separated by whether the policies will be configured via [Mobile Device Management](/windows/client-management/mdm/) (MDM) or Group Policy. For both tables:
 
 - **Policy** corresponds to the location and name of the policy.