check before: 2025-09-22
Product:
Entra, Intune, Microsoft 365 admin center, 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**
XXXXXXX ... free basic plan only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
The recent updates to the Windows Autopatch Client Broker are like upgrading from a manual car to an automatic one. The core function remains the same—getting you from point A to point B—but the experience becomes smoother and more reliable. Previously, installing the client broker relied on PowerShell scripts, which are like having to manually shift gears. This method works, but it can be a bit clunky and prone to hiccups.
Now, with the switch to Win32 app deployment, it's akin to having an automatic transmission. The process is more streamlined and less likely to encounter issues, making it easier for IT admins to manage installations. This change will begin rolling out on September 22, 2025, but don't worry—if your current setup works for you, it won't be affected. It's like having the option to keep your manual car if you prefer, while still having the choice to switch to automatic for a smoother ride.
Additionally, there's more flexibility with how you can deploy the client broker. Think of it like having a delivery service that can drop off packages to everyone in the neighborhood or just to specific houses. You can now deploy the client broker to all devices or target specific groups within your organization, thanks to the integration with Entra ID groups. This targeted approach can help ensure that only the necessary devices receive updates, saving time and resources.
To prepare for these changes, it's a good idea to familiarize yourself with the Microsoft Intune admin center, where you can manage these deployments. If you have any questions or run into issues, support is available through the Intune admin center. This update is designed to make the process more efficient and reliable, much like upgrading to a more modern and user-friendly system.
** 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 3 weeks ago
