diff --git a/windows/deployment/update/deployment-service-drivers.md b/windows/deployment/update/deployment-service-drivers.md
index 3a4f67a79d..1310226a09 100644
--- a/windows/deployment/update/deployment-service-drivers.md
+++ b/windows/deployment/update/deployment-service-drivers.md
@@ -75,9 +75,10 @@ Update policies define how content is deployed to a deployment audience. An [upd
 
 To create a policy without any deployment settings, in the request body specify the **Audience ID** as `id`. In the following example, the **Audience ID** is `d39ad1ce-0123-4567-89ab-cdef01234567`, and the `id` given in the response is the **Policy ID**:
 
-   ```http
+   ```msgraph-interactive
    POST https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies
-   Content-type: application/json
+   content-type: application/json
+   
    {
      "audience": {
        "@odata.id": "d39ad1ce-0123-4567-89ab-cdef01234567"
@@ -115,9 +116,10 @@ To create a policy with additional settings, in the request body:
 
    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`:
 
-   ```http
+   ```msgraph-interactive
    POST https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies
-   Content-Type: application/json
+   content-type: application/json
+   
    Content-length: 967
    {
      "@odata.type": "#microsoft.graph.windowsUpdates.updatePolicy",
@@ -156,15 +158,14 @@ To create a policy with additional settings, in the request body:
 
 To review the policy settings, run the following query using the **Policy ID**, for example `9011c330-1234-5678-9abc-def012345678`:
 
-   ```http
-    GET https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678
+   ```msgraph-interactive
+   GET https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678
    ```
 
 To edit the policy settings, **PATCH** the policy using the **Policy ID**. Run the following **PATCH** to automatically approve driver content that's recommended by `Microsoft`for deployment for **Policy ID** `9011c330-1234-5678-9abc-def012345678`:
 
-``` http
-   PATCH https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678
-   Content-Type: application/json
+``` msgraph-interactive
+PATCH https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678
 
 {
     "complianceChangeRules": [
@@ -196,7 +197,7 @@ Once Windows Update for Business deployment service has scan results from device
 
 To display [applicable content](/graph/api/resources/windowsupdates-applicablecontent), run a query using the  **Audience ID**, for example `d39ad1ce-0123-4567-89ab-cdef01234567`:  
 
-```http
+```msgraph-interactive
 GET https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/applicableContent
 ```
 
@@ -237,9 +238,9 @@ Each driver update is associated with a unique [catalog entry](/graph/api/resour
 
 Add a content approval to an existing policy, **Policy ID** `9011c330-1234-5678-9abc-def012345678` for the driver update with the **Catalog ID** `5d6dede684ba5c4a731d62d9c9c2a99db12c5e6015e9f8ad00f3e9387c7f399c`. Schedule the start date for February 14, 2023 at 1 AM UTC:
 
-```http
+```msgraph-interactive
 POST https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678/complianceChanges
-Content-type: application/json
+content-type: application/json
 
 {
     "@odata.type": "#microsoft.graph.windowsUpdates.contentApproval",
@@ -261,7 +262,7 @@ Content-type: application/json
 
 The response for a content approval returns content and deployment settings along with an `id`, which is the **Compliance Change ID**. The **Compliance Change ID** is `c03911a7-9876-5432-10ab-cdef98765432` in the following truncated response:
 
-```http
+```json
     "@odata.type": "#microsoft.graph.windowsUpdates.contentApproval",
     "id": "c03911a7-9876-5432-10ab-cdef98765432",
     "createdDateTime": "2023-02-02T17:54:39.173292Z",
@@ -281,7 +282,7 @@ The response for a content approval returns content and deployment settings alon
 
 Review all of the compliance changes to a policy with the most recent changes listed in the response first. The following example returns the compliance changes for a policy with the **Policy ID** `9011c330-1234-5678-9abc-def012345678` and sorts by `createdDateTime` in descending order:
 
-   ```http
+   ```msgraph-interactive
    GET https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678/complianceChanges?orderby=createdDateTime desc
    ```
 
@@ -290,7 +291,7 @@ Review all of the compliance changes to a policy with the most recent changes li
 
 To retrieve the deployment ID, use the [expand parameter](/graph/query-parameters#expand-parameter) to review the deployment information related the content approval. The following example displays the content approval and the deployment information for **Compliance Change ID** `c03911a7-9876-5432-10ab-cdef98765432` in update **Policy ID** `9011c330-1234-5678-9abc-def012345678`:
 
-   ```http
+   ```msgraph-interactive
    GET https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678/complianceChanges/c03911a7-9876-5432-10ab-cdef98765432/$/microsoft.graph.windowsUpdates.contentApproval?$expand=deployments
    ```
 
@@ -298,8 +299,9 @@ To retrieve the deployment ID, use the [expand parameter](/graph/query-parameter
 
 Since content approval is a compliance change for the policy, when you [update a content approval](/graph/api/resources/windowsupdates--contentapproval-update), you're editing the compliance change for the policy. The following example changes the `startDateTime` for the **Compliance Change ID** of `c03911a7-9876-5432-10ab-cdef98765432` in the update **Policy ID** `9011c330-1234-5678-9abc-def012345678` to February 28, 2023 at 5 AM UTC:
 
-```http
+```msgraph-interactive
 PATCH https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678/complianceChanges/c03911a7-9876-5432-10ab-cdef98765432
+content-type: application/json
 
 {
     "@odata.type": "#microsoft.graph.windowsUpdates.contentApproval",
@@ -318,9 +320,10 @@ PATCH https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011
 Approval for content can be revoked by setting the `isRevoked` property of the [compliance change](/graph/api/resources/windowsupdates-compliance) to true. This setting can be changed while a deployment is in progress. However, revoking will only prevent the content from being offered to devices if they haven't already received it. To resume offering the content, a new [approval](#approve-driver-content-for-deployment) will need to be created.
 
 
-```http
+```msgraph-interactive
 PATCH https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678/complianceChanges/c03911a7-9876-5432-10ab-cdef98765432
-Content-type: application/json
+content-type: application/json
+
 {
     "@odata.type": "#microsoft.graph.windowsUpdates.contentApproval",
     "isRevoked": true
@@ -329,7 +332,7 @@ Content-type: application/json
 
 To display all deployments with the most recently created returned first, order deployments based on the `createdDateTime`:
 
-```http
+```msgraph-interactive
 GET https://graph.microsoft.com/beta/admin/windows/updates/deployments?orderby=createdDateTime desc
 ```
 
diff --git a/windows/deployment/update/deployment-service-expedited-updates.md b/windows/deployment/update/deployment-service-expedited-updates.md
index f67447f315..68c6abfee9 100644
--- a/windows/deployment/update/deployment-service-expedited-updates.md
+++ b/windows/deployment/update/deployment-service-expedited-updates.md
@@ -79,6 +79,7 @@ When creating a deployment, there are [multiple options](/graph/api/resources/wi
 
 ```msgraph-interactive
 POST https://graph.microsoft.com/beta/admin/windows/updates/deployments
+content-type: application/json
 
 {
     "@odata.type": "#microsoft.graph.windowsUpdates.deployment",
@@ -157,6 +158,7 @@ The following example adds two devices to the deployment audience using the **Az
 
 ```msgraph-interactive
 POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/updateAudience
+content-type: application/json
 
 {
   "addMembers": [
@@ -180,6 +182,7 @@ The following example pauses the deployment with a **Deployment ID** of `de910e1
 
 ```msgraph-interactive
 PATCH https://graph.microsoft.com/beta/admin/windows/updates/deployments/de910e12-3456-7890-abcd-ef1234567890
+content-type: application/json
 
 {
   "@odata.type": "#microsoft.graph.windowsUpdates.deployment",
diff --git a/windows/deployment/update/deployment-service-feature-updates.md b/windows/deployment/update/deployment-service-feature-updates.md
index 41387215a9..18903a0866 100644
--- a/windows/deployment/update/deployment-service-feature-updates.md
+++ b/windows/deployment/update/deployment-service-feature-updates.md
@@ -55,8 +55,8 @@ All of the [prerequisites for the Windows Update for Business deployment service
 When you enroll devices into feature update management, the deployment service becomes the authority for feature updates coming from Windows Update.
 As long as a device remains enrolled in feature update management through the deployment service, the device doesn't receive any other feature updates from Windows Update unless explicitly deployed using the deployment service. A device is offered the specified feature update if it hasn't already received the update. For example, if you deploy Windows 11 feature update version 22H2 to a device that's enrolled into feature update management and is currently on an older version of Windows 11, the device updates to version 22H2. If the device is already running version 22H2 or a later version, it stays on its current version.
 
-   > [!TIP]
-   > Windows Update for Business reports has a [workbook](wufb-reports-workbook.md#feature-updates-tab) that displays the current operating system version for devices. In the workbook, go to the **Feature updates** tab and in the **In Service feature update** tile, select the **View details** link to open the details flyout. The OS version and Azure AD ID of devices can easily be exported into a .csv file or opened in [Azure Monitor Logs](/azure/azure-monitor/logs/log-query-overview) to help when creating a deployment audience.
+> [!TIP]
+> Windows Update for Business reports has a [workbook](wufb-reports-workbook.md#feature-updates-tab) that displays the current operating system version for devices. In the workbook, go to the **Feature updates** tab and in the **In Service feature update** tile, select the **View details** link to open the details flyout. The OS version and Azure AD ID of devices can easily be exported into a .csv file or opened in [Azure Monitor Logs](/azure/azure-monitor/logs/log-query-overview) to help when creating a deployment audience.
 
 <!--Using include for enrolling devices using Graph Explorer-->
 [!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-enroll-device-graph-explorer.md)]
@@ -65,7 +65,7 @@ As long as a device remains enrolled in feature update management through the de
 
 Each feature update is associated with a unique [catalog entry](/graph/api/resources/windowsupdates-catalogentry). The `id` returned is the **Catalog ID** and is used to create a deployment. Feature updates are deployable until they reach their support retirement dates. For more information, see the support lifecycle dates for [Windows 10](/lifecycle/products/windows-10-enterprise-and-education) and [Windows 11](/lifecycle/products/windows-11-enterprise-and-education) Enterprise and Education editions. The following query lists all deployable feature update catalog entries:
 
-```http
+```msgraph-interactive
 GET https://graph.microsoft.com/beta/admin/windows/updates/catalog/entries?$filter=isof('microsoft.graph.windowsUpdates.featureUpdateCatalogEntry')
 ```
 
@@ -97,9 +97,10 @@ When creating a deployment for a feature update, there are multiple options avai
 - Default [safeguard hold](/graph/api/resources/windowsupdates-safeguardprofile) behavior of applying all applicable safeguards to devices in a deployment
   - When safeguard holds aren't explicitly defined, the default safeguard hold behavior is applied automatically
 
-```http
+```msgraph-interactive
 POST https://graph.microsoft.com/beta/admin/windows/updates/deployments
-Content-type: application/json
+content-type: application/json
+
 {
     "content": {
         "@odata.type": "#microsoft.graph.windowsUpdates.catalogContent",
@@ -193,9 +194,9 @@ The response body will contain:
 
 To [update deployment](/graph/api/windowsupdates-deployment-update), PATCH the deployment resource by its **Deployment ID** and supply the updated settings in the request body. The following example keeps the existing gradual rollout settings that were defined when creating the deployment but changes the deployment start date to February 28, 2023 at 5 AM UTC:
 
-```http  
+```msgraph-interactive  
 PATCH https://graph.microsoft.com/beta/admin/windows/updates/deployments/de910e12-3456-7890-abcd-ef1234567890
-Content-type: application/json
+content-type: application/json
 
 {
     "settings": {
@@ -215,7 +216,7 @@ Content-type: application/json
 
 Verify the deployment settings for the deployment with a **Deployment ID** of `de910e12-3456-7890-abcd-ef1234567890`:
 
-```http
+```msgraph-interactive
 GET https://graph.microsoft.com/beta/admin/windows/updates/deployments/de910e12-3456-7890-abcd-ef1234567890
 ```
 
@@ -225,9 +226,9 @@ The **Audience ID**, `d39ad1ce-0123-4567-89ab-cdef01234567`, was created when th
 
 The following example adds three devices to the deployment audience using the **Azure AD ID** for each device:
 
-   ```http
+   ```msgraph-interactive
    POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/updateAudience
-   Content-type: application/json
+   content-type: application/json
 
    {
      "addMembers": [
@@ -253,10 +254,10 @@ To pause a deployment, PATCH the deployment to have a `requestedValue` of `pause
 
 The following example pauses the deployment with a **Deployment ID** of `de910e12-3456-7890-abcd-ef1234567890`:
 
-```http
+```msgraph-interactive
 
 PATCH https://graph.microsoft.com/beta/admin/windows/updates/deployments/de910e12-3456-7890-abcd-ef1234567890
-Content-Type: application/json
+content-type: application/json
 
 {
   "@odata.type": "#microsoft.graph.windowsUpdates.deployment",
diff --git a/windows/deployment/update/includes/wufb-deployment-audience-graph-explorer.md b/windows/deployment/update/includes/wufb-deployment-audience-graph-explorer.md
index 4bd33058e7..9d5e531e42 100644
--- a/windows/deployment/update/includes/wufb-deployment-audience-graph-explorer.md
+++ b/windows/deployment/update/includes/wufb-deployment-audience-graph-explorer.md
@@ -13,9 +13,8 @@ A deployment audience is a collection of devices that you want to deploy updates
 
 1. To create a new audience, **POST** to the [deployment audience](/graph/api/resources/windowsupdates-deploymentaudience) resource with a request body of `{}`.
 
-   ```http
-   POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences
-   content-type: application/json
+   ```msgraph-interactive
+   POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences   
 
    {}
    ```
@@ -34,9 +33,8 @@ A deployment audience is a collection of devices that you want to deploy updates
 
 1. Add devices, using their **Azure AD ID**, to the deployment audience so they become audience members. Specify the deployment **Audience ID** in the URL field and the devices to add in the request body. The `id` property specifies the **Azure AD ID** of the device.
 
-   ```http
-   POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/updateAudience
-   Content-type: application/json
+   ```msgraph-interactive
+   POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/updateAudience   
 
    {
      "addMembers": [
@@ -58,6 +56,6 @@ A deployment audience is a collection of devices that you want to deploy updates
 
 1. To verify the devices were added to the audience, run the following query using the **Audience ID** of `d39ad1ce-0123-4567-89ab-cdef01234567`:
 
-   ```http
+   ```msgraph-interactive
    GET https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/members
    ```
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 26f1f077a7..03e32e5950 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
@@ -14,13 +14,13 @@ Use the [device](/graph/api/resources/device) resource type to find clients to e
 
 - Displays the **AzureAD Device ID** and **Name** of all devices:
 
-   ```http
+   ```msgraph-interactive
   GET https://graph.microsoft.com/v1.0/devices?$select=deviceid,displayName
    ```
 
 - Displays the **AzureAD Device ID** and **Name** for devices that have a name starting with `Test`:
 
-   ```http
+   ```msgraph-interactive
   GET https://graph.microsoft.com/v1.0/devices?$filter=startswith (displayName,'Test')&$select=deviceid,displayName
    ```
 
@@ -37,13 +37,13 @@ For the next requests, set the **ConsistencyLevel** header to `eventual`. For mo
 
 - Display the **Name** and **Operating system version** for the device that has `01234567-89ab-cdef-0123-456789abcdef` as the **AzureAD Device ID**:
 
-   ```http
+   ```msgraph-interactive
    GET https://graph.microsoft.com/v1.0/devices?$search="deviceid:01234567-89ab-cdef-0123-456789abcdef"?$select=displayName,operatingSystemVersion`
    ```
 
 - To find devices that likely aren't virtual machines, filter for devices that don't have virtual machine listed as the model but do have a manufacturer listed. Display the **AzureAD Device ID**, **Name**, and **Operating system version** for each device:
 
-   ```http
+   ```msgraph-interactive
    GET https://graph.microsoft.com/v1.0/devices?$filter=model ne 'virtual machine' and NOT(manufacturer eq null)&$count=true&$select=deviceid,displayName,operatingSystemVersion`
    ```
 
diff --git a/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md b/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md
index f3a3b6f229..f85f158a63 100644
--- a/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md
+++ b/windows/deployment/update/includes/wufb-deployment-graph-unenroll.md
@@ -22,9 +22,9 @@ To unenroll a device, POST to [updatableAssets](/graph/api/resources/windowsupda
 
 The following example removes `driver` enrollment for two devices, `01234567-89ab-cdef-0123-456789abcdef` and `01234567-89ab-cdef-0123-456789abcde0`:
 
-```http
+```msgraph-interactive
 POST https://graph.microsoft.com/beta/admin/windows/updates/updatableAssets/unenrollAssets
-Content-Type: application/json
+content-type: application/json
 
 {
   "updateCategory": "driver",