From cafe43af4e02df6266bf4119a27ad6ce34d2e808 Mon Sep 17 00:00:00 2001
From: itsrlyAria <82474610+itsrlyAria@users.noreply.github.com>
Date: Tue, 28 Feb 2023 04:55:38 -0800
Subject: [PATCH] Update wufb-wsus.md

Adding the key needed if configuring regkeys directly.
---
 windows/deployment/update/wufb-wsus.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/windows/deployment/update/wufb-wsus.md b/windows/deployment/update/wufb-wsus.md
index 7feb6b10b2..ec39ae4a46 100644
--- a/windows/deployment/update/wufb-wsus.md
+++ b/windows/deployment/update/wufb-wsus.md
@@ -76,3 +76,7 @@ The policy can be configured using the following two methods:
 - [Update/SetPolicyDrivenUpdateSourceForFeatureUpdates](/windows/client-management/mdm/policy-csp-update#update-setpolicydrivenupdatesourceforfeature)
 - [Update/SetPolicyDrivenUpdateSourceForOtherUpdates](/windows/client-management/mdm/policy-csp-update#update-setpolicydrivenupdatesourceforother)
 - [Update/SetPolicyDrivenUpdateSourceForQualityUpdates](/windows/client-management/mdm/policy-csp-update#update-setpolicydrivenupdatesourceforquality)
+
+
+> [!NOTE]
+> Configuring registry keys directly to get the behavior of any Windows update policy is *not* recommended. However, if you are choosing to go this route, please also ensure you have configured the "UseUpdateClassPolicySource" registry key as well or the scan source will not be alterred. Again, it is recommended that you leverage the Group Policy (GP) or Configuration Service Provider (CSP) policy instead of directly writing these keys.