diff --git a/windows/deployment/update/deployment-service-drivers.md b/windows/deployment/update/deployment-service-drivers.md
index a511c7cde8..97477fbb0e 100644
--- a/windows/deployment/update/deployment-service-drivers.md
+++ b/windows/deployment/update/deployment-service-drivers.md
@@ -48,3 +48,9 @@ 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)]
 
+
+
+## Remove device enrollment
+
+<!--Using include for removing device enrollment-->
+[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-graph-unenroll.md)]
diff --git a/windows/deployment/update/deployment-service-feature-updates.md b/windows/deployment/update/deployment-service-feature-updates.md
index 1a703e5660..b9b6c71b1b 100644
--- a/windows/deployment/update/deployment-service-feature-updates.md
+++ b/windows/deployment/update/deployment-service-feature-updates.md
@@ -44,4 +44,10 @@ All of the [prerequisites for the Windows Update for Business deployment service
 As long as a device remains enrolled in feature update management, the device doesn't receive any other feature updates from Windows Update unless explicitly deployed using the deployment service.
 
 <!--Using include for enrolling devices using Graph Explorer-->
-[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-enroll-device-graph-explorer.md)]
\ No newline at end of file
+[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-enroll-device-graph-explorer.md)]
+
+
+## Remove device enrollment
+
+<!--Using include for removing device enrollment-->
+[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-graph-unenroll.md)]
\ No newline at end of file
diff --git a/windows/deployment/update/includes/wufb-deployment-enroll-device-graph-explorer.md b/windows/deployment/update/includes/wufb-deployment-enroll-device-graph-explorer.md
index 24f11868a3..5ea333f440 100644
--- a/windows/deployment/update/includes/wufb-deployment-enroll-device-graph-explorer.md
+++ b/windows/deployment/update/includes/wufb-deployment-enroll-device-graph-explorer.md
@@ -8,7 +8,7 @@ ms.topic: include
 ms.date: 02/14/2023
 ms.localizationpriority: medium
 ---
-<!--This file is shared by deployment-service-drivers.md, deployment-service-expedited-updates.md, and the deployment-service-feature-updates.md articles. Headings may be driven by article context. 7512398 -->
+<!--This file is shared by deployment-service-drivers.md and the deployment-service-feature-updates.md articles. Headings may be driven by article context. 7512398 -->
 
 You enroll devices based on the types of updates you want them to recieve.Currently, you can enroll devices to receive feature updates (`feature`) or drivers (`driver`). You can enroll devices to receive updates from multiple update classifications.
 
diff --git a/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md b/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md
new file mode 100644
index 0000000000..6fd26c4782
--- /dev/null
+++ b/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md
@@ -0,0 +1,41 @@
+---
+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 and the deployment-service-feature-updates.md articles. Headings may be driven by article context. 7512398 -->
+
+When a device no longer needs to be managed by the deployment service, remove the enrollment it. Just like [enrolling a device](#enroll-devices), specify either `driver` or `feature` as the value for the `updateCategory`. The device will no longer receive updates from the deployment service for the specfied update category, even if it's still assigned to an active deployment. Depending on the device's configuration, it may start to receive updates from Windows Update. For instance, if a device is still enrolled for feature updates, but the enrollment for drivers is removed:
+- Existing driver deployments from the service won't be installed
+- 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:
+- **Azure AD Device ID** as `id` for the device
+- Either `feature` or `driver` for the updateCategory
+
+The following example removes `driver` enrollment for two devices, `01234567-89ab-cdef-0123-456789abcdef` and `01234567-89ab-cdef-0123-456789abcde0`:
+
+```rest
+POST https://graph.microsoft.com/beta/admin/windows/updates/updatableAssets/unenrollAssets
+Content-Type: application/json
+
+{
+  "updateCategory": "driver",
+  "assets": [
+    {
+      "@odata.type": "#microsoft.graph.windowsUpdates.azureADDevice",
+      "id": "01234567-89ab-cdef-0123-456789abcdef"
+    },
+    {
+      "@odata.type": "#microsoft.graph.windowsUpdates.azureADDevice",
+      "id": "01234567-89ab-cdef-0123-456789abcde0"
+    }
+  ]
+}
+```