Managing and deploying updates via Configuration Manager
Microsoft officially deprecated WSUS on September 20, 2024, but it is not completely retired or discontinued yet. In Microsoft terms, deprecation means active development has stopped and no new features, capabilities, or major enhancements will ever be added to the product. The core functionality remains active, and Microsoft will continue to provide security updates, bug fixes, and technical support for existing setups.
Because the server role is fully included in Windows Server 2025, WSUS will remain functional and officially supported until at least 2035, matching the lifecycle of that operating system. Microsoft also explicitly noted in the Windows IT Pro Blog announcement that this change does not impact current integration or support within Configuration Manager. While there is no immediate pressure to shut down your current WSUS backend, Microsoft's long-term strategy heavily pushes environments toward cloud-native alternatives like Windows Update for Business, Microsoft Intune, and Azure Update Manager.
Btw. AFAIK, you cannot integrate Windows Autopatch directly into an unlinked SCCM/ECM environment because Windows Autopatch is a cloud-native service built on top of Microsoft Intune and Windows Update for Business. To use Windows Autopatch while maintaining your ECM infrastructure, you must establish Co-management between your ECM site and a Microsoft Intune tenant. Once co-management is configured, you would slide the Windows Update policies workload over to Intune. This specific configuration tells the local configuration manager client agent to stop scanning your on-premises WSUS server for OS patches and to start checking the cloud-based Windows Update service instead
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin