From 112219efbdc8ace19d67bebb778e2d7bce9799df Mon Sep 17 00:00:00 2001
From: Meghan Stewart <33289333+mestew@users.noreply.github.com>
Date: Sat, 11 Feb 2023 15:27:12 -0800
Subject: [PATCH] overview and prereq edits

---
 .../update/deployment-service-drivers.md      |  2 +-
 .../deployment-service-expedited-updates.md   |  3 +++
 .../update/deployment-service-troubleshoot.md | 12 ++---------
 ...ufb-deployment-update-health-tools-logs.md | 21 +++++++++++++++++++
 4 files changed, 27 insertions(+), 11 deletions(-)
 create mode 100644 windows/deployment/update/includes/wufb-deployment-update-health-tools-logs.md

diff --git a/windows/deployment/update/deployment-service-drivers.md b/windows/deployment/update/deployment-service-drivers.md
index 637e1711d3..19692f9cba 100644
--- a/windows/deployment/update/deployment-service-drivers.md
+++ b/windows/deployment/update/deployment-service-drivers.md
@@ -114,7 +114,7 @@ To create a policy with additional settings, in the request body:
   - Define any [deployment settings](/graph/api/resources/windowsupdates-deploymentsettings).
   - Add the `content-length` header to the request if a status code of 411 occurs. The value should be the length of the request body in bytes. For information on error codes, see [Microsoft Graph error responses and resource types](/graph/errors).
 
-   In the following driver update policy example, any deployments created by a content approval will start 7 days after approval and will gradually roll out to 1000 devices per day for **Audience ID** `d39ad1ce-0123-4567-89ab-cdef01234567`:
+   In the following driver update policy example, any deployments created by a content approval will start 7 days after approval for **Audience ID** `d39ad1ce-0123-4567-89ab-cdef01234567`:
 
    ```msgraph-interactive
    POST https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies
diff --git a/windows/deployment/update/deployment-service-expedited-updates.md b/windows/deployment/update/deployment-service-expedited-updates.md
index bf265fead9..ae8c818be9 100644
--- a/windows/deployment/update/deployment-service-expedited-updates.md
+++ b/windows/deployment/update/deployment-service-expedited-updates.md
@@ -192,3 +192,6 @@ content-type: application/json
   }
 }
 ```
+
+<!--Using include for Update Health Tools log location-->
+[!INCLUDE [Windows Update for Business deployment service permissions using Graph Explorer](./includes/wufb-deployment-update-health-tools-logs.md)]
\ No newline at end of file
diff --git a/windows/deployment/update/deployment-service-troubleshoot.md b/windows/deployment/update/deployment-service-troubleshoot.md
index 272538a56c..de2a896cad 100644
--- a/windows/deployment/update/deployment-service-troubleshoot.md
+++ b/windows/deployment/update/deployment-service-troubleshoot.md
@@ -52,13 +52,5 @@ A more recent update is deployed when the following conditions are met:
 
 While expedite update deployments will override an update deferral for the update version that's specified, they don't override deferrals that are in place for any other update version.
 
-### Log location for the Update Health Tools
-
-The Update Health Tools are used when you deploy expedited updates. In some cases, you may wish to review the logs for the Update Health Tools.
-
-**Log location**: `%ProgramFiles%\Microsoft Update Health Tools\Logs`
-
-- The logs are in `.etl` format. 
-  - Microsoft offers [PerfView as a download on GitHub](https://github.com/Microsoft/perfview/blob/main/documentation/Downloading.md) which displays etl files.
-
-For more information, see [Troubleshooting expedited updates](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/troubleshooting-expedited-updates/ba-p/2595615).
\ No newline at end of file
+<!--Using include for Update Health Tools log location-->
+[!INCLUDE [Windows Update for Business deployment service permissions using Graph Explorer](./includes/wufb-deployment-update-health-tools-logs.md)]
diff --git a/windows/deployment/update/includes/wufb-deployment-update-health-tools-logs.md b/windows/deployment/update/includes/wufb-deployment-update-health-tools-logs.md
new file mode 100644
index 0000000000..e627c3c296
--- /dev/null
+++ b/windows/deployment/update/includes/wufb-deployment-update-health-tools-logs.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-expedite.md and the deployment-service-troubleshoot.md articles. Headings may be driven by article context. 7512398 -->
+## Log location for the Update Health Tools
+
+The Update Health Tools are used when you deploy expedited updates. In some cases, you may wish to review the logs for the Update Health Tools.
+
+**Log location**: `%ProgramFiles%\Microsoft Update Health Tools\Logs`
+
+- The logs are in `.etl` format. 
+  - Microsoft offers [PerfView as a download on GitHub](https://github.com/Microsoft/perfview/blob/main/documentation/Downloading.md) which displays etl files.
+
+For more information, see [Troubleshooting expedited updates](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/troubleshooting-expedited-updates/ba-p/2595615).
\ No newline at end of file