Summary
Details
Updated August 26, 2025: We have updated the content. Thank you for your patience.
We are introducing improvements to how the Windows Autopatch Client Broker is managed and installed. The broker performs device readiness checks to identify whether a device is fully prepared to be managed by Windows Autopatch. Further, when a support request is created, it enables automated log collection to help diagnose and resolve issues more quickly. For information on data storage, see Privacy.
You will soon have the flexibility to deploy the client broker on-demand, either to all Autopatch devices or scoped to specific Entra ID groups. As part of this update, Win32 app deployment will become the default installation method, replacing the previous PowerShell-based approach. This change helps overcome limitations associated with PowerShell scripts and ensures a more reliable installation experience. Admins who prefer to use PowerShell can still manually install the broker using scripts if needed.
[When will this happen:]
The changes will be gradually rolled out starting September 22, 2025.
[How will this affect your organization:]
There will be no changes to your current set of devices with the client broker installed—they will remain assigned to the PowerShell script. However, with the upcoming launch, you’ll have the option to migrate to a Win32 app-based installation for improved reliability. Additionally, you’ll be able to use portal controls to selectively install the client broker on devices based on Entra ID groups.
[What you need to do to prepare:]
You should prepare for these changes in the Microsoft Intune admin center and inform your team. If you have any questions or concerns, or need assistance, file a service request by visiting the Microsoft Intune admin center. Additional Information and details will also be included on any docs.microsoft.com post feature release.
Change History
We are introducing improvements to how the Windows Autopatch Client Broker is managed and installed. The broker performs device readiness checks to identify whether a device is fully prepared to be managed by Windows Autopatch. Further, when a support request is created, it enables automated log collection to help diagnose and resolve issues more quickly. For information on data storage, see Privacy.
You will soon have the flexibility to deploy the client broker on-demand, either to all Autopatch devices or scoped to specific Entra ID groups. As part of this update, Win32 app deployment will become the default installation method, replacing the previous PowerShell-based approach. This change helps overcome limitations associated with PowerShell scripts and ensures a more reliable installation experience. Admins who prefer to use PowerShell can still manually install the broker using scripts if needed.
[When will this happen:]
The changes will be gradually rolled out starting September 22, 2025.
[How will this affect your organization:]
There will be no changes to your current set of devices with the client broker installed—they will remain assigned to the PowerShell script. However, with the upcoming launch, you’ll have the option to migrate to a Win32 app-based installation for improved reliability. Additionally, you’ll be able to use portal controls to selectively install the client broker on devices based on Entra ID groups.
[What you need to do to prepare:]
You should prepare for these changes in the Microsoft Intune admin center and inform your team. If you have any questions or concerns, or need assistance, file a service request by visiting the Microsoft Intune admin center. Additional Information and details will also be included on any docs.microsoft.com post feature release.
Updated August 26, 2025: We have updated the content. Thank you for your patience.
We are introducing improvements to how the Windows Autopatch Client Broker is managed and installed. The broker performs device readiness checks to identify whether a device is fully prepared to be managed by Windows Autopatch. Further, when a support request is created, it enables automated log collection to help diagnose and resolve issues more quickly. For information on data storage, see Privacy.
You will soon have the flexibility to deploy the client broker on-demand, either to all Autopatch devices or scoped to specific Entra ID groups. As part of this update, Win32 app deployment will become the default installation method, replacing the previous PowerShell-based approach. This change helps overcome limitations associated with PowerShell scripts and ensures a more reliable installation experience. Admins who prefer to use PowerShell can still manually install the broker using scripts if needed.
[When will this happen:]
The changes will be gradually rolled out starting September 22, 2025.
[How will this affect your organization:]
There will be no changes to your current set of devices with the client broker installed—they will remain assigned to the PowerShell script. However, with the upcoming launch, you’ll have the option to migrate to a Win32 app-based installation for improved reliability. Additionally, you’ll be able to use portal controls to selectively install the client broker on devices based on Entra ID groups.
[What you need to do to prepare:]
You should prepare for these changes in the Microsoft Intune admin center and inform your team. If you have any questions or concerns, or need assistance, file a service request by visiting the Microsoft Intune admin center. Additional Information and details will also be included on any docs.microsoft.com post feature release.
Never Miss a Microsoft 365 Update
Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.