Azure Update Manager replaces Automated Patching
Azure is retiring the Automated Patching feature on September 15th, 2027, and replacing it with Azure Update Manager. This change aims to provide a more streamlined update management process. Azure Update Manager offers centralized update management, customizable scheduling, and detailed patch compliance reporting for virtual machines, on-premises servers, and hybrid environments.
- →Automated Patching feature retirement
- →Introduction of Azure Update Manager
- →Customizable update scheduling
- →Patch compliance reporting
Deprecations (1) ›
- Automated Patching feature retirement
The Automated Patching feature will be retired effective September 15th, 2027, and replaced by Azure Update Manager.
Features (3) ›
- Introduction of Azure Update Manager
Azure Update Manager is introduced as a replacement for Automated Patching, offering centralized management for updates across virtual machines, on-premises servers, and hybrid environments.
- Customizable update scheduling
Azure Update Manager allows users to create custom update schedules based on organizational needs, including weekly, monthly, or specific date-based updates.
- Patch compliance reporting
The new Azure Update Manager generates detailed reports on patch compliance, helping administrators stay informed about update status across their infrastructure.
https://azure.microsoft.com/en-us/updates/?id=automated-patching-deprecation-and-replacement-with-azure-update-manager
Related releases
- Designing Scalable and Secure Agent-First Platforms with Azure Container Apps Sandboxes Microsoft Azure Blog ·
- Azure on Ensuring Resilience in the AI Era: Beyond Static Diagrams Microsoft Azure Blog ·
- Microsoft Foundry Expands AI Agent Capabilities with New Models, Voice, and Resilient Workflows Microsoft Azure Blog ·
- Azure AI Foundry model Kimi-K2.7-Code 2026-06-12 reaches end of life in 7 days endoflife.date ·
- Azure HorizonDB adds PostgreSQL 18 support in public preview Azure Updates ·
- Azure AI Foundry model gpt-4o 2024-05-13 end-of-life date moved to 2026-12-09 endoflife.date ·