Windows Update for Business deployment service

Applies to

  • Windows 10
  • Windows 11

The Windows Update for Business deployment service is a cloud service within the Windows Update for Business product family. It provides control over the approval, scheduling, and safeguarding of updates delivered from Windows Update. It's designed to work in harmony with your existing Windows Update for Business policies.

The deployment service is designed for IT Pros who are looking for more control than is provided through deferral policies and deployment rings. It provides the following abilities:

  • You can schedule deployment of updates to start on a specific date (for example, deploy 20H2 to specified devices on March 14, 2021).
  • You can stage deployments over a period of days or weeks by using rich expressions (for example, deploy 20H2 to 500 devices per day, beginning on March 14, 2021).
  • You can bypass pre-configured Windows Update for Business policies to immediately deploy a security update across your organization when emergencies arise.
  • You can benefit from deployments with automatic piloting tailored to your unique device population to ensure coverage of hardware and software in your organization.
  • You can use safeguards against likely update issues that have been identified by Microsoft machine-learning algorithms and automatically hold the deployment for any affected devices.

The service is privacy focused and backed by leading industry compliance certifications.

How it works

The deployment service complements existing Windows Update for Business capabilities, including existing device policies and Update Compliance.

Elements in following text.

Windows Update for Business comprises three elements:

  • Client policy to govern update experiences and timing – available through Group Policy and CSPs
  • Deployment service APIs to approve and schedule specific updates – available through the Microsoft Graph and associated SDKs (including PowerShell)
  • Update Compliance to monitor update deployment – available through the Azure Marketplace

Unlike existing client policy, the deployment service doesn't interact with devices directly. The service is native to the cloud and all operations take place between various Microsoft services. It creates a direct communication channel between a management tool (including scripting tools such as Windows PowerShell) and the Windows Update service so that the approval and offering of content can be directly controlled by an IT Pro.

Process described in following text.

Using the deployment service typically follows a common pattern:

  1. IT Pro uses a management tool to select devices and approve content to be deployed. This tool could be PowerShell, a Microsoft Graph app or a more complete management solution such as Microsoft Intune.
  2. The chosen tool conveys your approval, scheduling, and device selection information to the deployment service.
  3. The deployment service processes the content approval and compares it with previously approved content. Final update applicability is determined and conveyed to Windows Update, which then offers approved content to devices on their next check for updates.

The deployment service exposes these capabilities through Microsoft Graph REST APIs. You can call the APIs directly, through a Graph SDK, or integrate them with a management tool such as Microsoft Intune.


To work with the deployment service, devices must meet all these requirements:

  • Be running Windows 10, version 1709 or later (or Windows 11)
  • Be joined to Azure Active Directory (AD) or Hybrid AD
  • Have one of the following Windows 10 or Windows 11 editions installed:
    • Pro
    • Enterprise
    • Education
    • Pro Education
    • Pro for Workstations

Additionally, your organization must have one of the following subscriptions:

  • Windows 10/11 Enterprise E3 or E5 (included in Microsoft 365 F3, E3, or E5)
  • Windows 10/11 Education A3 or A5 (included in Microsoft 365 A3 or A5)
  • Windows Virtual Desktop Access E3 or E5
  • Microsoft 365 Business Premium

Getting started

To use the deployment service, you use a management tool built on the platform, script common actions using PowerShell, or build your own application.

Using Microsoft Intune

Intune integrates with the deployment service to provide Windows client update management capabilities. For more information, see Feature updates for Windows 10 and later policy in Intune.

Scripting common actions using PowerShell

The Microsoft Graph SDK includes a PowerShell extension that you can use to script and automate common update actions. For more information, see Get started with the Microsoft Graph PowerShell SDK.

Building your own application

Microsoft Graph makes deployment service APIs available through. Get started with these learning paths:

Once you're familiar with Microsoft Graph development, see Windows updates API overview in Microsoft Graph for more.

Deployment protections

The deployment service protects deployments through a combination of rollout controls and machine-learning algorithms that monitor deployments and react to issues during the rollout.

Schedule rollouts with automatic piloting

The deployment service allows any update to be deployed over a period of days or weeks. Once an update has been scheduled, the deployment service optimizes the deployment based on the scheduling parameters and unique attributes spanning the devices being updated. The service follows these steps:

  1. Determine the number of devices to be updated in each deployment wave, based on scheduling parameters.
  2. Select devices for each deployment wave so that earlier waves have a diversity of hardware and software, to function as pilot device populations.
  3. Start deploying to earlier waves to build coverage of device attributes present in the population.
  4. Continue deploying at a uniform rate until all waves are complete and all devices are updated.

This built-in piloting capability complements your existing ring structure and provides another support for reducing and managing risk during an update. Unlike tools such as Desktop Analytics, this capability is intended to operate within each ring. The deployment service doesn't provide a workflow for creating rings themselves.

You should continue to use deployment rings as part of the servicing strategy for your organization, but use gradual rollouts to add scheduling convenience and other protections within each ring.

Safeguard holds against likely and known issues

Microsoft uses safeguard holds to protect devices from encountering known quality or compatibility issues by preventing them from installing the update or upgrade. For Windows 11 deployments, the deployment service extends these safeguard holds to also protect devices that Microsoft identifies as being at a higher risk of experiencing problems after an update (such as operating system rollbacks, app crashes, or graphics issues). The service temporarily holds the deployment for these devices while Microsoft investigates the likely issue. Safeguard holds apply to deployments by default, but you can opt out.

To verify whether a device is affected by a safeguard hold, see Am I affected by a safeguard hold?

Monitoring deployments to detect rollback issues

During deployments of Windows 11 or Windows 10 feature updates, driver combinations can sometimes result in an unexpected update failure that makes the device revert to the previously installed operating system version. The deployment service can monitor devices for such issues and automatically pause deployments when this happens, giving you time to detect and mitigate issues.

How to enable deployment protections

Deployment scheduling controls are always available, but to take advantage of the unique deployment protections tailored to your population, devices must share diagnostic data with Microsoft.

Device prerequisites

  • Diagnostic data is set to Required or Optional.
  • The AllowWUfBCloudProcessing policy is set to 8.

Set the AllowWUfBCloudProcessing policy

To enroll devices in Windows Update for Business cloud processing, set the AllowWUfBCloudProcessing policy using mobile device management (MDM) policy or Group Policy.

Policy Sets registry key under HKLM\Software
GPO for Windows 10, version 1809 or later: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Allow WUfB Cloud Processing \Policies\Microsoft\Windows\DataCollection\AllowWUfBCloudProcessing
MDM for Windows 10, version 1809 or later: ../Vendor/MSFT/ Policy/Config/System/AllowWUfBCloudProcessing \Microsoft\PolicyManager\current\device\System\AllowWUfBCloudProcessing

Following is an example of setting the policy using Intune:

  1. Sign in to the Endpoint Manager admin center.

  2. Select Devices > Configuration profiles > Create profile.

  3. Select Windows 10 and later in Platform, select Templates in Profile type, select Custom in Template name, and then select Create.

  4. In Basics, enter a meaningful name and a description for the policy, and then select Next.

  5. In Configuration settings, select Add, enter the following settings, select Save, and then select Next.

    • Name: AllowWUfBCloudProcessing
    • Description: Enter a description.
    • OMA-URI: ./Vendor/MSFT/Policy/Config/System/AllowWUfBCloudProcessing
    • Data type: Integer
    • Value: 8
  6. In Assignments, select the groups that will receive the profile, and then select Next.

  7. In Review + create, review your settings, and then select Create.

  8. (Optional) To verify that the policy reached the client, check the value of the following registry entry:


Best practices

Follow these suggestions for the best results with the service.

Device onboarding

  • Wait until devices finish provisioning before managing with the service. If a device is being provisioned by Autopilot, it can only be managed by the deployment service after it finishes provisioning (typically one day).

  • Use the deployment service for feature update management without feature update deferral policy. If you want to use the deployment service to manage feature updates on a device that previously used a feature update deferral policy, it's best to set the feature update deferral policy to 0 days to avoid having multiple conditions governing feature updates. You should only change the feature update deferral policy value to 0 days after you've confirmed that the device was enrolled in the service with no errors.


Avoid using different channels to manage the same resources. If you use Microsoft Intune along with Microsoft Graph APIs or PowerShell, aspects of resources (such as devices, deployments, updatable asset groups) might be overwritten if you use both channels to manage the same resources. Instead, only manage each resource through the channel that created it.

Next steps

To learn more about the deployment service, try the following: