Windows Update reports for Microsoft Intune

With Intune, you can deploy updates to Windows 10/11 devices by using policies for:

• Update rings for Windows 10 and later
• Feature updates for Windows 10 and later
• Windows Driver updates for Windows 10 and later

Reports for these policy types are available to help you monitor and troubleshoot update deployments, Intune supports the following report options:

• Reports in Intune:

  • Windows 10 update rings – Use a built-in report that's ready by default when you deploy update rings to your devices.
  • Windows 10 feature updates – Use two built-in reports that work together to gain a deep picture of update status and issues. These reports require you to configure data collection from devices before the reports can display data about feature updates.
  • Windows Driver updates – Use the built-in reports to understand which driver updates are applicable to your devices and which of those updates have been approved, installed, or paused.

• Windows Update for Business reports:

  Use Windows Update for Business reports with Intune to monitor Windows update rollouts. Windows Update for Business reports is a free service built on Azure Monitor and Log Analytics.

For more information, see Monitor Windows Updates with Windows Update for Business reports in the Windows documentation.

Reports for Update rings for Windows 10 and later policy

Intune offers integrated report views for the Windows update ring policies you deploy. These views display details about the update ring deployment and status. To access reports, in the Intune admin center go to Devices > Windows > Update rings for Windows 10 and later > and select an update ring policy. Intune displays details similar to the following for the selected policy:

Tip

For details about the policy actions at the top of the policy view, like Delete, Pause, and Extend, see Manage your Windows Update rings in the Update rings for Windows 10 and later policy in Intune article.

On the policy page view:

• Device and user check-in status: The default report view for this policy. This default view includes a high-level bar chart that displays a count of devices reporting four status values for this policy, and a color bar that visually represents the percentage of devices reporting each status by color. This view displays the following four status results for the policy:

  • Succeeded
  • Error
  • Conflict
  • Not applicable

• View report: This button opens a more detailed report view for Device and user check-in status. The detailed report view includes a chart and color bar similar to that from the preceding high-level view, but reports one the additional status of In progress.

  This view also includes device specific details that include:

  • Device name
  • Logged in user
  • Check-in status
  • Last report modification time

  

  From this report view, you can select a device to drill in to view the list of the settings in the policy, and the status of the selected device for each of those settings. Additional drill-in is available by selecting a setting to open the Setting details. The Setting details display the name of the setting, the devices status (State) for that setting, and a list of profiles that manage the setting and that are assigned to the device. This is useful to help identify the source of a settings conflict.

• Two additional report tiles: You can select the tiles for the following reports to view additional details:

  • Device assignment status – This report shows all the devices that are targeted by the policy, including devices in a pending policy assignment state.

    For this report, you can select one or more status details you are interested in, and then select Generate report to update the view with only that information. In this following image, we have generated a report that displays only the devices that were successfully assigned this policy:

    

    This report supports drilling in to view the list of settings, with subsequent drill-in as seen in for the full report view available from the View report button.

  • Per setting status – View the configuration status of each setting for this policy across all devices and users. This view present a simple view of each setting in the policy, and the count of assigned devices that have success, error, or conflict. This report view doesn't support drilling in for additional detail.

Reports for Windows 10 and later feature updates policy

Intune offers integrated reports to view detailed Windows update deployment status for devices using Feature updates for Windows 10 and later policies. To use reports for this feature, you must first configure prerequisites and policies that support data collection from devices.

The data in the Intune reports for Feature updates for Windows 10 and later policy is used only for these reports and doesn't surface in other Intune reports.

• Windows 10 feature updates (Organizational)- This report provides an overall view of compliance for devices on a per-policy basis.
• Feature update failures report (Operational) – This report provides details on Alerts – errors, warnings, information, and recommendations – on a per-policy basis to help troubleshoot and optimize your devices.

Before you can use the feature updates policy reports, you must configure prerequisites for the report.

Prerequisites

• Data collection:

  Before a device can send the reporting data that's used in the Windows 10 feature updates report for Intune, you must Configure data collection:

  • Service-based data is collected for all feature update versions and doesn't require you to configure data collection.
  • Client-based data is collected from devices only after data collection is configured.

  Service and client-based data is described in Use the Windows 10 feature updates (Organizational) report later in this article.

• Devices:

  Devices must:

  • Meet the prerequisites for Windows 10 and later feature updates policy as documented in Feature updates for Windows 10 and later policy in Intune.
  • Be Azure Active Directory Joined, or Hybrid Azure Active Directory Joined to support submitting of data for reporting.
  • Run Windows 10 1903 or later, or Windows 11. Although Windows 10 and later feature updates policy supports earlier versions of Windows, earlier versions don't support reporting of the data that Intune uses for the feature updates reports.

Configure data collection

The data that powers Intune's Windows feature updates reports isn't collected by the typical device sync with Intune. Instead, it's collected through the Windows health monitoring device configuration policy, which uses the Windows 10/11 and Windows Server Connected User Experiences and Telemetry component (DiagTrack) to collect the data from Intune-managed devices. To enable use of this data in the reports, you must configure devices to send Windows Updates data.

Enable data collection

To Configure this setting for your devices, Create a profile with the following information:

• Platform: Select Windows 10 and later.

• Profile: Select Windows health monitoring.

• Name: Enter a descriptive name for the profile, like Intune data collection policy.

• Description: Enter a description for the profile. This setting is optional, but recommended.

• In Configuration Settings:

  • Health Monitoring: Select Enable to collect event information from supported Windows 10/11 devices.
  • Scope: Select Windows Updates.

• Use the Scope tags and Applicability rules to filter the profile to specific IT groups or devices in a group that meet a specific criteria. Only Windows 10 version 1903 and later and Windows 11 are supported for these reports.

  

When you complete the creation of the Windows health monitoring profile, the profile deploys to the assigned groups, and configuration of data collection is complete.

It can take up to 24 hours after setting up Windows health monitoring with Windows updates before the policy is applied.

Tip

If you use Endpoint Analytics, you can modify the existing configuration profile. The same policy is used to collect data for Endpoint Analytics.

About reporting data latency

The data for these reports is generated at different times, which depend on the type of data:

• Service-based data from Windows Update – This data typically arrives in less than an hour after an event happens in the service. Events include Alerts for a device that can't register with Windows Update (which is viewable in the Feature update failures report), to status updates about when Windows Update began offering an update to clients. This data is available without configuring data collection.

• Client-based data from Intune devices that are configured to send data to Intune – This data is processed in batches and refreshes every eight hours, but is only available after you configure data collection. The data contains information like when a client doesn't have enough disk space to install an update. This data is also used in the Windows 10 feature updates organizational report to show the various installation steps a device moves through when installing feature updates.

Use the Windows 10 feature updates (Organizational) report

The Windows 10 feature updates report provides an overview of compliance for devices you target with a Windows feature updates policy.

Important

Before this report can show data, you must configure data collection for the Windows feature updates reports.

This report provides you update installation status that's based on the update state from device and device-specific update details. The data in this report is timely, calls out the device name and state, and other update-related details. This report also supports filtering, searching, paging, and sorting.

To use the report:

1. Sign in to the Microsoft Intune admin center.

2. To view a summary report across all Windows 10 and later feature updates policies:

   • In the admin center, go to Reports > Windows updates. The default view displays the Summary tab:

     

3. To open the Windows 10 feature updates report and view device details for a specific feature updates profile:

   • In the admin center, go to Reports > Windows updates > select the Reports tab > select Windows Feature Update Report.

   • Select on Select a feature update profile, select a profile, and then Generate report.

   • Select Update status and Ownership to refine the report.

     

   The following list identifies the columns that are available in the view:

   • Devices – The name of the device.
   • UPN – Intune user identifier (email).
   • Intune Device ID – Intune device identifier.
   • AAD Device ID – Azure Active Directory identifier for device.
   • Last Event Time – The last time there was new data, or something happened for the device and update.
   • Update State – The state of the update for the device. Initial state data is from the service-side, which is the status of the update in the system before it begins to install on the device. When client-side data is available, client-side data is shown, replacing the server-side data.
   • Update Substate – A low-level detailed version of the Update State.
   • Update Aggregated Status – A high-level summary of the Update State, like In progress or Error.
   • Alert Type – When applicable, Alert Type displays the most recent alert message.
   • Alert Details – This column isn't in use.
   • Last Scan Time – The last time this device ran a scan for Windows Update.

   The following information applies to Update State and Update Substate:

   • Service-side data:

     • Pending:
       • Validation – The update can't be offered to the device because of a validation issue with the device and Windows Update.
       • Scheduled – The update isn't ready to be offered to the device but is ready to be offered.
     • On hold:
       • Admin paused – The update is on hold because the Deployment being paused by an explicit Administrator action.
       • ServicePaused – The update is on hold because of an automatic action by Windows Update.
     • Canceled:
       • Admin Cancelled – The update offer was canceled by explicit Administrator action.
       • Service Cancelled – The update was canceled by Windows Update for one of the following reasons:
         • The end of service for the selected content was reached and it’s no longer offered by Windows Update. For example, the device might have been added to a deployment after the content’s availability expired, or the content reached its end of service date before it could install on the device.
         • The deployment content has been superseded for the device. This can happen when the device is targeted by another deployment that deploys newer content. For example, one deployment targets the Windows 10 device to install version 2004 and a second deployment targets that same device with version 21H1. In this event, 2004 is superseded by the 21H1 deployment and Windows Update cancels the 2004 deployment to the device.
       • Removed from Deployment – The update offer was canceled because it was removed from the Deployment by explicit Administrator action.
     • Offering:
       • OfferReady – The update is currently being offered to the device by Windows Update.

   • Client-side data:

     • On Hold:
       • Deferred – Windows Update for Business (WUfB) policies are causing the device to defer the update being offered.
     • Offering:
       • Offer Received – The device scanned against Windows Update (WU) and identifies that the update is applicable but hasn't begun to download it.
     • Installing:
       • Download Start – The download process has begun.
       • Download Complete – The download process has completed.
       • Install Start – The pre-restart install process has started.
       • Install Complete – The pre-restart install process has finished. If the update doesn't require a restart, the update process ends here.
       • Restart Required – A restart is required to finish update.
       • Restart Initiated – The device has gone into restart.
       • Restart Complete – The device has come back from restart.
     • Installed:
       • Update Installed – The update successfully installed.
     • Uninstalling:
       • Uninstall – The device is actively uninstalling the update.
       • Rollback – A rollback has been initiated to a previous update because of a serious issue during installation.
       • Update Uninstalled – The update successfully uninstalled.
       • Rollback complete – A rollback has completed.
     • Cancelled:
       • User Cancelled – A user canceled the update.
       • Device Cancelled – The device canceled the update for a user. This action is usually because the update no longer applies.

   • Other:

     • Needs attention: The device has some issue and needs attention.

Use the Feature update failures (Operational) report

The Feature update failures operational report provides details for devices that you target with a Windows 10 and later feature updates policy, and that have attempted to install an update. Devices in this report might have an Alert that prevents the device from completing installation of the update.

Important

Before this report can show data, you must configure data collection for the Windows feature updates reports.

This report provides insights to update installation status, including the number of devices with errors. It also supports drilling in for more details to help you troubleshoot issues with the installation. This report supports filtering, searching, paging, and sorting.

To use the report:

1. Sign in to the Microsoft Intune admin center.

2. Select Devices > Monitor, and then below Software updates select Feature update failures.

   • The initial view displays a per-profile summary of how many devices have alerts for each of your profiles with the version of Windows that the profile targets:

     

   • Selecting a profile opens a dedicated view that contains all active Alerts for that profile.

   • While viewing the active alerts for the profile:

     • Select an Alert Message to open a pane that displays more details for that alert:

       

     • Select the device name to open the Device page:

       

The following list identifies Alert Messages, and suggested remediation actions:

Alert Message	Description	Recommendation
CancelledByUser	User canceled the update.	Retry the installation.
DamagedMedia	The update file or the hard drive is damaged.	Run Chkdsk /F on the device with administrator privileges, then retry the update.
DeploymentConflict	Device is in more than one deployment of the same update type. Only the first deployment assigned is effective.	Remove the device from any deployments that shouldn't apply.
DeviceRegistrationInvalidAzureADDeviceId	The device isn't able to register or authenticate properly with Windows Update because of an invalid Azure AD Device ID.	Check that the device is joined to the Azure Active Directory tenant making the request.
DeviceRegistrationInvalidGlobalDeviceId	The device isn't able to register or authenticate properly with Windows Update because of an invalid Global Device ID.	The Microsoft Account Sign-In Assistant (MSA) Service might be disabled, preventing Global Device ID assignment. Check that the MSA Service is running or able to run on the device.
DeviceRegistrationIssue	The device isn't able to register or authenticate properly with Windows Update.	Check that the device registration information is correct and the device can connect.
DeviceRegistrationNoTrustType	The device isn't able to register or authenticate properly with Windows Update because it can't establish Trust.	Check that the device is joined in Azure Active Directory using your account. If the issue persists, the device might need to be unenrolled from Intune first.
DiskFull	The installation couldn't complete because the Windows partition is full.	Free up disk space on the Windows partition. Retry the installation.
DownloadCancelled	Windows Update couldn't download the update because the update server stopped the connection.	Make sure your network is working and retry the download. If it still fails, check your WSUS server or contact support.
DownloadConnectionIssue	Windows Update couldn't connect to the update server and the update couldn't download.	Make sure your network is working and retry the download. If it still fails, contact support.
DownloadCredentialsIssue	Windows Update couldn't download the file because the Background Intelligent Transfer Service (BITS) couldn't connect to the internet. A proxy server or firewall on your network might require credentials.	Retry the download. If it fails again, review your network configuration to make sure that this computer can access the internet. If you need help, contact support.
DownloadIssue	There was an issue downloading the update.	Retry the installation.
DownloadIssueServiceDisabled	There was a problem with the Background Intelligent Transfer Service (BITS). The BITS service or a service it depends on might be disabled.	In the Services administration tool, make sure that the Background Intelligent Transfer Service is enabled. If the service isn't running, try starting it manually. If it won't start, check the event log for errors.
DownloadTimeout	A timeout occurred while Windows tried to contact the update service or the server containing the update's payload.	Retry the download. If it doesn't succeed, make sure that the update service and payload servers are running normally and that there are no network connectivity issues.
EndOfService	Device is on a version of Windows that has passed its end of service date.	Update device to a version that is currently supported.
EndOfServiceApproaching	Device is on a version of Windows that is approaching its end of service date.	Update the device to a version that has a longer remaining servicing timeline.
FailureResponseThreshold	The failure response threshold setting was met for a deployment to which the device belongs.	Consider pausing the deployment and assessing for issues.
FailureResponseThresholdPause	A deployment to which the device belongs was paused because of its failure response threshold being met.	Review devices that encountered issues.
FileNotFound	The downloaded update files can't be found. The Disk Cleanup utility or a non-Microsoft software cleaning tool might have removed the files during cleanup.	Download the update again, and then retry the installation.
Incompatible	The system doesn't meet the minimum requirements to install the update.	Review the ScanResult.xml file for Block Type=Hard.
IncompatibleArchitecture	This update is for a different CPU architecture.	Make sure the target operating system architecture matches the host operating system architecture.
IncompatibleServicingChannel	Device is in a servicing channel that is incompatible with a deployment to which the device belongs.	Configure the device's servicing channel to a retail (Generally Available) update channel.
InstallAccessDenied	Installer doesn't have permission to access or replace a file. The installer might have tried to replace a file that an antivirus, antimalware, or a backup program is currently scanning.	Retry the installation.
InstallCancelled	The installation was canceled.	Retry the installation.
InstallFileLocked	Installer couldn't access a file that is already in use. The installer might have tried to replace a file that an antivirus, antimalware, or backup program is currently scanning.	Check the files under the %SystemDrive%$Windows.~bt directory. Retry the installation.
InstallIssue	There was an issue installing the update.	Run dism /online /cleanup-image /restorehealth on the device with administrator privileges, then retry the update. If the commands fail, a reinstall of Windows might be required.
InstallIssueRedirection	A known folder that doesn't support redirection to another drive might have been redirected to another drive.	Report this issue to Microsoft if this error is encountered more than a once.
InstallMissingInfo	Windows Update doesn't have information it needs about the update to finish the installation.	Another update might have replaced the one you're trying to install. Check the update, and then try reinstalling it.
InstallOutOfMemory	The installation couldn't complete because Windows ran out of memory.	Restart Windows, then try the installation again. If it still fails, allocate more memory to the virtual machine, or increase the size of the virtual memory pagefiles.
InstallSetupError	Windows Setup encountered an error while installing.	Check that the BIOS and drivers are up to date. Retry the download.
InstallSystemError	A system occurred while installing.	Check that the BIOS and drivers are up to date. Retry the download.
PolicyConflict	There are client policies (MDM, GP) that conflict with Windows Update settings.	Check that the client policies configured on the device don't conflict with deployment settings.
PolicyConflictDeferral	The Deferral Policy configured on the device is preventing the update from installing.	Check that the client policies configured on the device don't conflict with deployment settings.
PolicyConflictPause	Updates are paused on the device, preventing the update from installing.	Check that the client policies configured on the device don't conflict with deployment settings.
PostRestartIssue	Windows Update couldn't determine the results of installing the update. The error is usually false and the update probably succeeded.	If the update you're trying to install isn't available, no action is required. If the update is still available, retry the installation.
RollbackInitiated	A rollback was started on this device, indicating a catastrophic issue occurred during the Windows Setup install process.	Run the Setup Diagnostics Tool on the Device. Don't retry the installation until the impact is understood.
SafeguardHold	Update can't install because of a known Safeguard Hold.	View the Deployment Error Code column of the report to see the ID of the safeguard hold. Open the Windows release health dashboard at https://aka.ms/WindowsReleaseHealth to view information about the active holds, including known issues with the update.
UnexpectedShutdown	The installation was stopped because a Windows shutdown or restart was in progress.	Ensure the device remains on during Windows installation.
VersionMismatch	Device is on a version of Windows that wasn't intended by Windows Update.	Confirm whether the device is on the intended version.
WindowsRepairRequired	The current version of Windows needs to be repaired before it can be updated.	Run the Startup Repair Tool on this device.
WUBusy	Windows Update can't do this task because it's busy.	Restart Windows. Retry the installation.
WUComponentMissing	Windows Update might be missing a component or the update file might be damaged.	Run dism /online /cleanup-image /restorehealth on the device with administrator privileges, and then retry the update. If the commands fail, a reinstall of Windows might be required.
WUDamaged	Windows Update or the update file might be damaged.	Run dism /online /cleanup-image /restorehealth on the device with administrator privileges, and then retry the update. If the commands fail, a reinstall of Windows might be required.
WUDecryptionIssue	Windows Update couldn't decrypt the encrypted update file because it couldn't find the proper key.	Retry the installation.
WUDiskError	Windows Update encountered an error while reading or writing to the system drive.	Run the Windows Update Troubleshooter on the device. Retry the installation.
WUIssue	Windows Update couldn't understand the metadata provided by the update service. This error usually indicates a problem with the update.	Contact support.

Reports for Windows Driver updates policy

Intune offers integrated reports to view detailed status for Windows driver updates for devices assigned to Windows Driver update policies. To use these reports, you must first configure the prerequisites and policies that support data collection from devices. These reports are applicable to Windows 10 and Windows 11.

The data in the Intune reports for Windows Driver update policies is used only for these reports and doesn't appear in other Intune reports. The following reports are available:

• Windows Driver updates summary
• Windows Driver updates report
• Windows Driver update failures

Prerequisites for driver updates reports

Devices and data collection

To support reporting on all status and events for driver updates, you must configure the following data collection settings:

• Enable Windows diagnostic data collection from devices at a level of Required or higher.
• At the Tenant level, set Enable features that require Windows diagnostic data in processor configuration to On. This setting can be configured in the Microsoft Intune admin center at Tenant administration > Connectors and tokens > Windows data.

User permissions to use reports

To view these reports, users must be assigned an Intune role with the Managed devices > View reports permission. This permission is included in the following built-in roles:

• Endpoint Security Manager
• Read Only Operator
• Help Desk Operator

Windows Driver updates summary

On the Summary tab of the Windows Updates node of Reports, you can view summary details about device success or failure for installing updates from device update policies. To find this report, navigate to Reports > Windows Updates > Summary tab and scroll down until you find the Windows Driver updates.

The following screen capture displays a summary of four policies, each assigned to a single device.

This report allows you to view the status of driver updates for each policy (Profile column). It displays the number of devices that are up-to-date (Success), failed (Error), paused (Paused), etc. for the driver updates in that policy. However, each device is only represented once in a single status column, based on the worst status across all of the updates that apply to that device.

Intune ranks the following statuses in order of priority, from best (Success) to worst (NeedsReview):

• Success – All applicable driver updates have installed successfully.
• In progress – At least one update remains in progress, and none have been paused, failed, or worse.
• Paused – At least one update has been paused, but none have failed to install, been cancelled, or are pending review.
• Error – At least one update failed to install, but none are cancelled or pending review.
• Cancelled – At least one update has been declined, but none are pending review.
• NeedsReview – One or more updates are new to the policy and pending review to approve or decline.

For example: A policy might have three applicable driver updates for an assigned device. If one of the three fails to install on that device while the other two updates install successfully, the device is identified by adding one to the Error column. Once all three updates install successfully, the device is represented by adding one to the Success column and reducing the count of the Error column by one.

This report doesn’t support drilling in for more details about devices, driver updates, or policy details.

Windows Driver updates report

The Windows Driver Updates report allows you to select a single driver update and view details about the policies in which it's applicable for a device. This report provides information about the driver from all your driver update policies, offering a different perspective than other reports, which only provide details specific to a single policy.

To find this report, in the admin center go to Reports > Windows updates > Reports tab, and then select the Windows Driver Update Report tile.

In the following screen capture, the report shows details for the driver update Microsoft – APPLIANCES – 1.0.0.1.

To change the focus of this report to a different driver:

1. On the Windows 10 and later Driver updates view, select Select a driver update to open the Driver updates pane on the right.

2. The Driver updates pane displays a list of updates that are approved and applicable for at least one device from across all your driver update policies.

3. On the Driver updates pane, select a driver, and then OK to return to the Windows 10 and later Driver updates report view that now shows information for the driver you selected, and select Generate again to update the report.

In the following screen capture, only four drivers remain applicable to devices with driver updates policy, and those four updates are different versions of the same driver update.

Column details:

While most of the column details should be clear, the following warrant some explanation:

• Update State – This column presents the most recent status of the selected driver update, as reported by each device to which it applies. Further details can be found in the Update Substrate column.

  • Cancelled – The update was paused in the policy that applies to this device.
  • Offering – The update is approved, but the device hasn't yet installed it.
  • Installed – The update installed successfully.
  • Needs attention – There's an installation issue for the update on this device.

• Policy – This column identifies the name of the policy in which the update was approved.

• Last Scan Time – This column provides insight into when a device last checked for updates. This can help explain why approved updates haven't installed. For instance, if the last scan time is several weeks old, it may indicate that the device is either offline or unable to connect to scan for updates.

Data retention:

As devices across all your updates policies install the latest versions of a driver update, older driver update versions that are no longer needed by any device drops off the driver updates list. However, this isn't necessarily an immediate event. Reporting data for driver updates remains available until the end of a data retention period is reached. This period is six months since the last time an event for the update is received.

• If the update is approved and all applicable devices have installed the update, then six months after the last device updates is status, the update is removed from reporting details.
• Similarly, if an update is paused and shows no activity for the retention period, that update is also dropped from reporting details after six months. After an updates data ages out, if a paused update that remains applicable to a device is reapproved, subsequent status for that update begins to appear in reports. Previous data that aged out of reports won’t be restored or available.

Windows Driver update failures

Windows driver updates include a report on driver update failures. To find this report, in the admin center go to Devices > Monitor > Windows Driver update failures. This report is part of the Software updates group and might require you to scroll down the admin center to locate it.

When you select the report, you can view a list of your update policies and see a count of devices in each policy that have at least one driver update error. In the previous screen capture, only one driver has such an error.

By selecting that policy and entry, you can then view more information about the error, including:

• Device Name
• Driver Name
• Driver Class
• Alert Message
• Deployment Error Code
• UPN
• Intune Device ID

This view is a useful place to identify and start investigation of driver update installation failures.

Use Windows Update for Business reports

You can monitor Windows update rollouts by using Windows Update for Business reports. Windows Update for Business reports is offered through the Azure portal and is included as part of Windows 10/11 licenses listed in the prerequisites. Azure Log Analytics ingestion and retention charges aren't incurred on your Azure subscription for Windows Update for Business reports data.

To use this solution, you'll:

• Use an Intune device configuration profile to deploy the settings to your Windows 10/11 devices.

• Optionally, deploy a configuration script as a Win32 app to those same devices to validate their configuration for Windows Update for Business reports.

• Use Windows Update for Business reports to Monitor Windows updates.

For guidance on this solution, see Configuring Microsoft Intune devices for Windows Update For Business reports in the Windows Update For Business reports documentation.

Next steps

Manage software updates in Intune