check before: 2025-02-15
Product:
Intune, Microsoft 365 admin center, Windows Autopatch
Platform:
Online, Windows Desktop, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message
Links:

Details:
Summary:
Windows Autopatch Client Setup Script updates will start mid-February 2025 and continue through mid-March 2025. The script will uninstall the old 'Microsoft Cloud Managed Desktop Extension' and upgrade the 'Windows Autopatch Client Broker' for better performance. Ensure device.autopatch.microsoft.com is on your allow list.
Details:
Updated March 4, 2025: We have updated the rollout timeline below. Thank you for your patience.
We are updating the 'Modern Workplace - Autopatch Client Setup' script used by Windows Autopatch. Currently, this script installs the 'Microsoft Cloud Managed Desktop Extension' and 'Windows Autopatch Client Broker' applications, which share the same script for post-device registration readiness checks. The updated script will uninstall the old 'Microsoft Cloud Managed Desktop Extension' application and upgrade the existing application for improved performance.
[When will this happen:]
We will start the updates in mid-February 2025 (previously early February), and they will continue through mid-March 2025 (previously late February).
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-01-17
updated:
2025-03-05
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**
Uninstallation of Old Extension
The uninstallation of the 'Microsoft Cloud Managed Desktop Extension' may lead to temporary disruptions in service if not properly managed, affecting user access to cloud-managed desktop features.
- roles: IT Administrator, End User
- references: https://learn.microsoft.com/windows/deployment/windows-autopatch/prepare/windows-autopatch-configure-network?tabs=business-premium-and-a3-licenses-required-microsoft-endpoints
Upgrade of Client Broker
Upgrading the 'Windows Autopatch Client Broker' without preparation may result in compatibility issues with existing applications, leading to potential downtime or degraded performance for users.
- roles: IT Administrator, End User
- references: https://learn.microsoft.com/windows/deployment/windows-autopatch/prepare/windows-autopatch-configure-network?tabs=business-premium-and-a3-licenses-required-microsoft-endpoints
Network Configuration Changes
Failure to add 'device.autopatch.microsoft.com' to the allow list may prevent the new client from functioning correctly, causing interruptions in service and impacting user productivity.
- roles: Network Administrator, End User
- references: https://intune.microsoft.com/#home
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
Improved Device Management Efficiency
By upgrading to the 'Windows Autopatch Client Broker', IT can benefit from enhanced performance and scalability, which can lead to reduced time spent on device management and troubleshooting.
- next-steps: Evaluate current device management processes to identify time-consuming tasks that can be streamlined with the new setup. Train IT staff on the updated functionalities of the 'Windows Autopatch Client Broker'.
- roles: IT Administrators, System Administrators
- references: https://learn.microsoft.com/windows/deployment/windows-autopatch/prepare/windows-autopatch-configure-network?tabs=business-premium-and-a3-licenses-required-microsoft-endpoints
Streamlined Network Configuration
Adding 'device.autopatch.microsoft.com' to the allow list can help simplify network configurations and improve connectivity for devices using Windows Autopatch, which can lead to fewer network-related issues.
- next-steps: Review and update firewall and network policies to include the new endpoint. Communicate the changes to network administration teams to ensure compliance and proper implementation.
- roles: Network Administrators, IT Security Teams
- references: https://learn.microsoft.com/windows/deployment/windows-autopatch/prepare/windows-autopatch-configure-network?tabs=business-premium-and-a3-licenses-required-microsoft-endpoints
Enhanced User Experience with Faster Updates
The transition to the new 'Windows Autopatch Client Broker' is designed to provide better performance, which can lead to faster update rollouts and improved user satisfaction as devices stay up-to-date with less downtime.
- next-steps: Gather user feedback on current update experiences and communicate the expected improvements. Monitor user satisfaction post-implementation to assess the impact of the changes.
- roles: End Users, IT Support Teams
- references: https://learn.microsoft.com/windows/deployment/windows-autopatch/prepare/windows-autopatch-configure-network?tabs=business-premium-and-a3-licenses-required-microsoft-endpoints
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-03-05 | MC Last Updated | 02/11/2025 21:33:31 | 2025-03-04T21:22:50Z |
2025-03-05 | MC Messages | Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience.
We are updating the 'Modern Workplace - Autopatch Client Setup' script used by Windows Autopatch. Currently, this script installs the 'Microsoft Cloud Managed Desktop Extension' and 'Windows Autopatch Client Broker' applications, which share the same script for post-device registration readiness checks. The updated script will uninstall the old 'Microsoft Cloud Managed Desktop Extension' application and upgrade the existing application for improved performance. [When will this happen:] We will start the updates in mid-February 2025 (previously early February), and they will continue through late February 2025. | Updated March 4, 2025: We have updated the rollout timeline below. Thank you for your patience.
We are updating the 'Modern Workplace - Autopatch Client Setup' script used by Windows Autopatch. Currently, this script installs the 'Microsoft Cloud Managed Desktop Extension' and 'Windows Autopatch Client Broker' applications, which share the same script for post-device registration readiness checks. The updated script will uninstall the old 'Microsoft Cloud Managed Desktop Extension' application and upgrade the existing application for improved performance. [When will this happen:] We will start the updates in mid-February 2025 (previously early February), and they will continue through mid-March 2025 (previously late February). |
2025-03-05 | MC End Time | 04/16/2025 09:00:00 | 2025-05-05T09:00:00Z |
2025-03-05 | MC Summary | The Windows Autopatch Client Setup script will be updated in February 2025 to uninstall the old Microsoft Cloud Managed Desktop Extension and improve application performance. Organizations should add device.autopatch.microsoft.com to their allow list and can seek assistance via the Microsoft Intune admin center. | Windows Autopatch Client Setup Script updates will start mid-February 2025 and continue through mid-March 2025. The script will uninstall the old 'Microsoft Cloud Managed Desktop Extension' and upgrade the 'Windows Autopatch Client Broker' for better performance. Ensure device.autopatch.microsoft.com is on your allow list. |
2025-02-12 | MC Messages | We are updating the 'Modern Workplace - Autopatch Client Setup' script used by Windows Autopatch. Currently, this script installs the 'Microsoft Cloud Managed Desktop Extension' and 'Windows Autopatch Client Broker' applications, which share the same script for post-device registration readiness checks. The updated script will uninstall the old 'Microsoft Cloud Managed Desktop Extension' application and upgrade the existing application for improved performance.
[When will this happen:] We will start the updates in early February 2025, and they will continue through late February 2025. | Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience.
We are updating the 'Modern Workplace - Autopatch Client Setup' script used by Windows Autopatch. Currently, this script installs the 'Microsoft Cloud Managed Desktop Extension' and 'Windows Autopatch Client Broker' applications, which share the same script for post-device registration readiness checks. The updated script will uninstall the old 'Microsoft Cloud Managed Desktop Extension' application and upgrade the existing application for improved performance. [When will this happen:] We will start the updates in mid-February 2025 (previously early February), and they will continue through late February 2025. |
2025-02-12 | MC Title | Improvements to Windows Autopatch Client Setup Script | (Updated) Improvements to Windows Autopatch Client Setup Script |
2025-02-12 | MC Last Updated | 01/16/2025 21:01:12 | 2025-02-11T21:33:31Z |
2025-02-12 | MC MessageTagNames | Feature update, Admin impact | Updated message, Feature update, Admin impact |
Last updated 2 weeks ago