From 211cddd5580fcc8ae662054f5ff38d32645640d8 Mon Sep 17 00:00:00 2001
From: Meghan Stewart <33289333+mestew@users.noreply.github.com>
Date: Tue, 14 Feb 2023 11:08:50 -0800
Subject: [PATCH] add policy considerations include

---
 .../wufb-deployment-policy-considerations.md  | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 windows/deployment/update/includes/wufb-deployment-policy-considerations.md

diff --git a/windows/deployment/update/includes/wufb-deployment-policy-considerations.md b/windows/deployment/update/includes/wufb-deployment-policy-considerations.md
new file mode 100644
index 0000000000..d94f08d213
--- /dev/null
+++ b/windows/deployment/update/includes/wufb-deployment-policy-considerations.md
@@ -0,0 +1,21 @@
+---
+author: mestew
+ms.author: mstewart
+manager: aaroncz
+ms.technology: itpro-updates
+ms.prod: windows-client
+ms.topic: include
+ms.date: 02/14/2023
+ms.localizationpriority: medium
+---
+<!--This file is shared by deployment-service-drivers.md, deployment-service-troubleshoot.md, and the deployment-service-prerequisites.md articles. Headings may be driven by article context. 7512398 -->
+
+## Policy considerations
+
+It's possible for the service to receive content approval but the content doesn't get installed on the device because of a Group Policy, CSP, or registry setting on the device. In some cases, organizations specifically configure policies to fit their needs. For instance, they may want to review applicable driver content, but not approve it for install through the deployment service. Configuring this sort of behavior can be useful, especially when transitioning driver update management due to changing organizational needs.
+
+| Policy | Behavior |
+|---|---|
+| 
+
+