From 4386d5f09700175f484aafc60ed314b92592cdd2 Mon Sep 17 00:00:00 2001
From: Meghan Stewart <33289333+mestew@users.noreply.github.com>
Date: Wed, 25 Jan 2023 16:41:22 -0800
Subject: [PATCH] edits, add new incluyde

---
 .../update/deployment-service-drivers.md        | 17 +++++++++++++++++
 .../deployment-service-feature-updates.md       |  3 +++
 ...eployment-find-device-name-graph-explorer.md |  2 +-
 .../includes/wufb-deployment-graph-unenroll.md  |  2 +-
 4 files changed, 22 insertions(+), 2 deletions(-)

diff --git a/windows/deployment/update/deployment-service-drivers.md b/windows/deployment/update/deployment-service-drivers.md
index 97477fbb0e..dd3b3a7828 100644
--- a/windows/deployment/update/deployment-service-drivers.md
+++ b/windows/deployment/update/deployment-service-drivers.md
@@ -22,6 +22,7 @@ In this tutorial, you will:
 > * [Enroll devices](#enroll-devices)
 > * Do Z
 > * Do Z
+> * [Remove device enrollment](#remove-device-enrollment)
 
 ## Prerequisites
 
@@ -48,8 +49,24 @@ When you enroll devices into driver management, the deployment service becomes t
 <!--Using include for enrolling devices using Graph Explorer-->
 [!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-enroll-device-graph-explorer.md)]
 
+## Create an audience
 
+```rest
+POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences
+content-type: application/json
 
+{}
+```
+
+Returns a [201 Created] response with the following body:
+```json
+{
+    "@odata.context": "https://graph.microsoft.com/beta/$metadata#admin/windows/updates/deploymentAudiences/$entity",
+    "id": "f0ec689b-fa10-4e45-965c-ce753f7d4363",
+    "reportingDeviceCount": 0,
+    "applicableContent": []
+}
+```
 ## Remove device enrollment
 
 <!--Using include for removing device enrollment-->
diff --git a/windows/deployment/update/deployment-service-feature-updates.md b/windows/deployment/update/deployment-service-feature-updates.md
index b9b6c71b1b..5c6a7a72c0 100644
--- a/windows/deployment/update/deployment-service-feature-updates.md
+++ b/windows/deployment/update/deployment-service-feature-updates.md
@@ -19,7 +19,10 @@ In this tutorial, you will:
 > [!div class="checklist"]
 > * [Open Graph Explorer](#open-graph-explorer) 
 > * [Run queries to identify test devices](#run-queries-to-identify-test-devices)
+> * [Enroll devices](#enroll-devices)
 > * Do Z
+> * Do Z
+> * [Remove device enrollment](#remove-device-enrollment)
 
 ## Prerequisites
 
diff --git a/windows/deployment/update/includes/wufb-deployment-find-device-name-graph-explorer.md b/windows/deployment/update/includes/wufb-deployment-find-device-name-graph-explorer.md
index 3e64a0ecf5..457be3217f 100644
--- a/windows/deployment/update/includes/wufb-deployment-find-device-name-graph-explorer.md
+++ b/windows/deployment/update/includes/wufb-deployment-find-device-name-graph-explorer.md
@@ -29,7 +29,7 @@ GET https://graph.microsoft.com/v1.0/devices?$filter=startswith(displayName,'Tes
 For the next requests, set the **ConsistencyLevel** header to `eventual`. For more information about advanced query parameters, see [Advanced query capabilities on Azure AD directory objects](/graph/aad-advanced-queries).
 
 1. In Graph Explorer, select the **Request headers** tab.
-1. For **Key** type in `ConsistencyLevel` and for **Value**, type `eventual`. 
+1. For **Key** type in `ConsistencyLevel` and for **Value**, type `eventual`.
 1. Select the **Add** button. When you're finished, remove the request header by selecting the trash can icon.
 
     :::image type="content" source="../media/7512398-deployment-service-graph-modify-header.png" alt-text="Screenshot of the request headers tab in Graph Explorer" lightbox="../media/7512398-deployment-service-graph-modify-header.png":::
diff --git a/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md b/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md
index 6fd26c4782..9b026473fa 100644
--- a/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md
+++ b/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md
@@ -15,7 +15,7 @@ When a device no longer needs to be managed by the deployment service, remove th
 - The device will continue to receive feature updates from the deployment service
 - Drivers may start being installed from Windows Update depending on the device's configuration
 
-To remove device enrollment,POST to [updatableAssets](/graph/api/resources/windowsupdates-updatableasset) using [unenrollAssets](/graph/api/windowsupdates-updatableasset-unenrollassets). In the request body, specify:
+To remove device enrollment, POST to [updatableAssets](/graph/api/resources/windowsupdates-updatableasset) using [unenrollAssets](/graph/api/windowsupdates-updatableasset-unenrollassets). In the request body, specify:
 - **Azure AD Device ID** as `id` for the device
 - Either `feature` or `driver` for the updateCategory