check before: 2025-09-22
Product:
Entra, Intune, Microsoft 365 admin center, Windows, Windows Autopatch
Platform:
Online, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message, User impact
Links:
Details:
Summary:
Windows Autopatch Client Broker improvements include on-demand deployment to all or specific Entra ID groups, switching the default installation to Win32 app from PowerShell for better reliability, with rollout starting September 22, 2025. Current installations remain unchanged; admins should prepare via Microsoft Intune.
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.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-08-22
updated:
2025-08-27
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
Deployment Reliability Issues
If the change is implemented without preparation, there may be deployment failures due to the transition from PowerShell to Win32 app installation, leading to devices not being managed properly.
- roles: IT Admin, Support Staff
- references: https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/overview/windows-autopatch-privacy
User Experience Disruption
Users may experience disruptions if the client broker fails to install correctly, resulting in unavailability of features and support for device management.
- roles: End User, IT Support
- references: https://learn.microsoft.com/windows/deployment/windows-autopatch/overview/windows-autopatch-privacy
Increased Support Requests
Without proper preparation, the number of support requests may increase due to issues arising from the new installation method, overwhelming the support team.
- roles: Support Staff, IT Admin
- references: https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/overview/windows-autopatch-privacy
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
On-Demand Deployment Flexibility
The introduction of on-demand deployment to specific Entra ID groups allows IT admins to target specific devices or user groups for installation. This can lead to more efficient resource allocation and a tailored user experience based on departmental needs.
- next-steps: Develop a strategy for identifying critical user groups that require immediate deployment. Train IT staff on using the new deployment features in Intune.
- roles: IT Administrators, System Engineers, Department Heads
- references: https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/overview/windows-autopatch-privacy
Improved Reliability with Win32 App Installation
Switching the default installation method to Win32 apps enhances the reliability of the installation process, reducing the potential for errors that can occur with PowerShell scripts. This can minimize downtime and support tickets related to installation failures.
- next-steps: Evaluate the current deployment processes and plan for transitioning existing installations to the Win32 app model. Monitor the performance post-migration to assess improvements.
- roles: IT Administrators, Support Teams, Operations Managers
- references: https://learn.microsoft.com/windows/deployment/windows-autopatch/overview/windows-autopatch-privacy
Automated Log Collection for Support Requests
The automated log collection feature enables quicker diagnosis and resolution of issues, potentially reducing the time IT spends on troubleshooting. This leads to a better user experience as problems can be resolved faster.
- next-steps: Implement training for support staff on how to leverage automated logs for troubleshooting. Update documentation to reflect new processes and best practices for issue resolution.
- roles: Help Desk Staff, IT Support Managers, System Administrators
- references: https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/overview/windows-autopatch-privacy
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2025-08-27 | MC 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.
https://go.microsoft.com/fwlink/?linkid=2109431 https://teams.microsoft.com/l/message/19:2605e3fb-72df-4db1-880d-c3e21557f38e_c3c976db-1556-41e7-8261-164ed547fd0f@unq.gbl.spaces/1755635431855?context=%7B%22contextType%22%3A%22chat%22%7D | 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.
https://go.microsoft.com/fwlink/?linkid=2109431 https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/overview/windows-autopatch-privacy https://learn.microsoft.com/windows/deployment/windows-autopatch/overview/windows-autopatch-privacy |
| 2025-08-27 | MC Summary | Windows Autopatch Client Broker will be improved with on-demand deployment via Win32 app (replacing PowerShell), scoped by Entra ID groups. Rollout starts September 22, 2025. Existing installations remain unchanged. Admins should prepare in Intune and can still use PowerShell if preferred. | Windows Autopatch Client Broker improvements include on-demand deployment to all or specific Entra ID groups, switching the default installation to Win32 app from PowerShell for better reliability, with rollout starting September 22, 2025. Current installations remain unchanged; admins should prepare via Microsoft Intune. |
| 2025-08-27 | MC Last Updated | 08/22/2025 02:03:59 | 2025-08-26T17:51:17Z |
| 2025-08-27 | MC Messages | 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. | 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. |
| 2025-08-27 | MC Title | Improvements to the Windows Autopatch Client Broker | (Updated) Improvements to the Windows Autopatch Client Broker |
| 2025-08-27 | MC MessageTagNames | Feature update, User impact, Admin impact | Updated message, Feature update, User impact, Admin impact |
Last updated 2 months ago ago
