Generated on: March 18, 2026 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 3 items
Published: March 17, 2026 17:45:45 UTC Link: Generally Available: Default Rule Set 2.2 and updates to ruleset support policy
Update ID: 558016 Data source: Azure Updates API
Categories: Launched, Networking, Security, Application Gateway, Azure Front Door, Web Application Firewall, Features
Summary:
What was updated
Azure Web Application Firewall (WAF) has announced the general availability of Default Rule Set (DRS) 2.2 on Azure Application Gateway and Azure Front Door. Additionally, the managed ruleset support policy has been updated.
For more details, see the official update: https://azure.microsoft.com/updates?id=558016
Details:
Comprehensive Technical Explanation: Azure Web Application Firewall (WAF) Default Rule Set 2.2 General Availability and Ruleset Support Policy Update
Background and Purpose of the Update:
The Azure Web Application Firewall (WAF) is a critical security component for protecting web applications from common threats and vulnerabilities. The release of Default Rule Set (DRS) 2.2 marks its general availability on both Azure Application Gateway and Azure Front Door. Alongside this, Microsoft is updating the managed ruleset support policy. The primary purpose of this update is to provide a clearer and more predictable framework for ruleset support, ensuring that organizations can plan their security posture with greater confidence and transparency.
Specific Features and Detailed Changes:
Technical Mechanisms and Implementation Methods:
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
Summary:
The general availability of Default Rule Set 2.2 and the updated managed ruleset support policy for Azure Web Application Firewall provide enhanced security, clearer lifecycle management, and improved operational predictability for organizations using Azure Application Gateway and Azure Front Door.
Published: March 17, 2026 17:45:45 UTC Link: Generally Available: Foundry Agent Service
Update ID: 557141 Data source: Azure Updates API
Categories: Launched, AI + machine learning, Microsoft Foundry, Features
Summary:
What was updated
The Foundry Agent Service is now generally available (GA) on Azure. This release introduces a redesigned API format and enhanced runtime experience for building and managing agents.
Target audience affected
Developers and IT professionals building, deploying, or managing agent-based solutions on Azure, especially those moving from proof-of-concept to production.
For more details, refer to the official Azure Update.
Details:
Azure Update Technical Report: Generally Available – Foundry Agent Service
Background and Purpose of the Update:
The Foundry Agent Service has reached General Availability (GA), marking its transition from preview to a fully supported Azure service. This update introduces a next-generation platform specifically designed to help teams efficiently build, deploy, and manage agents. The primary goal is to enable seamless movement from prototyping to production, ensuring reliability and scalability for agent-based solutions.
Specific Features and Detailed Changes:
Technical Mechanisms and Implementation Methods:
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
Summary Sentence:
The Foundry Agent Service is now generally available, offering a redesigned API and enhanced runtime to help teams confidently build, operate, and scale agent-based solutions from prototype to production within the Azure ecosystem.
Published: March 17, 2026 17:30:11 UTC Link: Retirement: Azure VMware Solution AV36P and AV52 node retirement on June 30, 2029
Update ID: 557094 Data source: Azure Updates API
Categories: Compute, Azure VMware Solution, Retirements
Summary:
What was updated
Microsoft announced the retirement of Azure VMware Solution (AVS) AV36P and AV52 node types, effective June 30, 2029.
Key changes or new features
The AV36P and AV52 node types will no longer be available for provisioning after June 30, 2029. Existing Reserved Instances (RIs) for these node types will remain valid until their expiration, and current terms are not impacted by this announcement.
Target audience affected
This update affects IT professionals and developers managing Azure VMware Solution environments, particularly those utilizing AV36P or AV52 nodes, and those responsible for capacity planning, infrastructure lifecycle management, and RI purchasing.
Important notes if any
Customers should review the expiration dates of their current AV36P and AV52 RIs and plan migrations or transitions to supported node types before the retirement date. No immediate action is required, but early planning is recommended to avoid service disruption. Microsoft will provide further guidance as the retirement date approaches.
For more details, visit the official Azure Update.
Details:
Azure Update Technical Report
Title: Retirement: Azure VMware Solution AV36P and AV52 node retirement on June 30, 2029
Link: Azure Update
Background and Purpose of the Update:
Microsoft has announced the retirement of the AV36P and AV52 node types within the Azure VMware Solution (AVS) platform, effective June 30, 2029. This update is part of Microsoft’s ongoing lifecycle management for Azure infrastructure components, ensuring that customers are informed well in advance about the deprecation of specific node SKUs. The purpose is to provide customers with ample time to plan for migration or transition strategies, minimizing disruption to workloads running on these node types.
Specific Features and Detailed Changes:
The AV36P and AV52 nodes are specific compute SKUs offered in Azure VMware Solution, designed to provide dedicated VMware infrastructure on Azure. The retirement announcement means that after June 30, 2029, these node types will no longer be available for provisioning or renewal. Existing Reserved Instances (RI) for AV36P and AV52 nodes will continue to operate as per their current terms and are not affected by this announcement until their expiration. Customers are advised to review their RI expiration dates and plan accordingly for future capacity needs.
Technical Mechanisms and Implementation Methods:
The retirement process will be managed through Azure’s standard lifecycle management procedures. After the retirement date, the Azure portal and APIs will no longer permit the creation or extension of AV36P and AV52 nodes. Existing nodes will continue to function until the end of their RI term, after which customers will need to migrate workloads to supported node types. Microsoft will provide tools and guidance for migration to newer node SKUs within the Azure VMware Solution platform, ensuring compatibility and continuity of service.
Use Cases and Application Scenarios:
AV36P and AV52 nodes are typically used by enterprises running VMware workloads in Azure, leveraging dedicated infrastructure for high-performance, scalable, and secure virtualization. Common scenarios include datacenter extension, disaster recovery, and cloud migration of VMware-based applications. The retirement impacts customers who have standardized on these node types for their AVS deployments and will require them to evaluate alternative node SKUs for future workloads.
Important Considerations and Limitations:
Integration with Related Azure Services:
Azure VMware Solution integrates with a broad range of Azure services, including Azure networking, storage, and security solutions. The retirement of AV36P and AV52 nodes may require customers to update their integration points, such as reconfiguring network connectivity or adjusting storage mappings, when migrating to new node types. Microsoft will continue to support AVS integration with other Azure services, ensuring that customers can maintain seamless operations during and after migration.
Summary Sentence:
Microsoft will retire the AV36P and AV52 node types in Azure VMware Solution on June 30, 2029, and recommends customers review their Reserved Instance expiration dates and plan for migration to supported node SKUs to ensure uninterrupted service.
This report was automatically generated - 2026-03-18 03:02:33 UTC