Generated on: October 09, 2026 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 7 items
Published: October 08, 2026 22:51:01 UTC Link: Generally Available: Managed StandardV2 NAT Gateway for AKS
Update ID: 574430 Data source: Azure Updates API
Categories: Launched, Compute, Containers, Networking, Azure Kubernetes Service (AKS), Azure NAT Gateway, Features
Summary:
- What was updated
Azure Kubernetes Service (AKS) now provisions and manages a StandardV2 NAT Gateway for clusters using an AKS-managed virtual network. StandardV2 is now the default managed NAT Gateway SKU for new clusters in supported regions when using the managedNATGateway outbound type.
- Key changes or new features
- Target audience affected
- Important notes if any
Details:
Azure Update Technical Report
Title: Generally Available: Managed StandardV2 NAT Gateway for AKS
Link: Azure Update
Background and Purpose of the Update
Azure Kubernetes Service (AKS) clusters often require outbound connectivity to external resources, such as APIs, repositories, or other cloud services. Traditionally, outbound traffic management in AKS has been handled via NAT Gateways, which provide source network address translation (SNAT) for pods within the cluster. The update introduces the StandardV2 NAT Gateway as the default managed NAT Gateway SKU for AKS clusters using AKS-managed virtual networks, specifically when the managedNATGateway outbound type is selected. The purpose is to enhance outbound traffic management, simplify NAT Gateway provisioning, and improve scalability and reliability for AKS workloads.
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
AKS now provisions and manages a StandardV2 NAT Gateway by default for new clusters using AKS-managed virtual networks and the managedNATGateway outbound type, streamlining outbound traffic management and enhancing scalability in supported regions.
Published: October 08, 2026 19:56:31 UTC Link: Generally Available: Azure Database for PostgreSQL flexible server in East US 3
Update ID: 573691 Data source: Azure Updates API
Categories: Launched, Databases, Hybrid + multicloud, Azure Database for PostgreSQL, Feature
Summary:
What was updated
Azure Database for PostgreSQL Flexible Server is now generally available in the East US 3 Azure region.
Key changes or new features
This update enables deployment of PostgreSQL Flexible Server instances in the East US 3 region. Customers can now leverage all features of the Flexible Server deployment option, including high availability, zone-redundant capabilities, and flexible scaling, within this new region.
Target audience affected
Developers and IT professionals who manage or deploy PostgreSQL databases on Azure, especially those with workloads or compliance requirements in the East US 3 region.
Important notes if any
This expansion provides additional regional redundancy and disaster recovery options. It also supports customers seeking to optimize latency or meet data residency requirements in the Eastern US. Existing deployments in other regions are unaffected, but new deployments can now be provisioned in East US 3. For more details, refer to the official documentation.
Details:
Comprehensive Technical Explanation: Azure Database for PostgreSQL Flexible Server Now Generally Available in East US 3
Background and Purpose of the Update:
This update announces the general availability of Azure Database for PostgreSQL Flexible Server in the East US 3 Azure region. The purpose is to expand regional coverage, enabling customers to deploy PostgreSQL flexible servers closer to their user base or workloads within East US 3. This supports improved performance, data residency compliance, and disaster recovery strategies by providing more geographic options for deployment.
Specific Features and Detailed Changes:
With this update, all features of Azure Database for PostgreSQL Flexible Server are now accessible in the East US 3 region. This includes built-in high availability, zone-redundant deployments, automated backups, scaling of compute and storage resources, and advanced security features such as virtual network integration and private endpoints. No new features are introduced; rather, the full set of existing flexible server capabilities is now regionally available.
Technical Mechanisms and Implementation Methods:
The implementation involves provisioning the managed PostgreSQL flexible server service in the East US 3 region’s Azure datacenters. Customers can select East US 3 as the target region during server creation via the Azure Portal, CLI, ARM templates, or REST APIs. The underlying infrastructure leverages Azure’s regional resource management and network architecture to ensure low-latency access and regional redundancy.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
Azure Database for PostgreSQL Flexible Server in East US 3 integrates seamlessly with other Azure services available in the region, such as Azure Virtual Network, Azure Key Vault, Azure Monitor, and Azure Backup. This enables secure, monitored, and automated database deployments as part of broader cloud solutions.
Summary Sentence:
Azure Database for PostgreSQL Flexible Server is now generally available in the East US 3 region, enabling customers to deploy managed PostgreSQL databases with full feature support, improved regional coverage, and integration with Azure services for enhanced performance, compliance, and scalability.
Published: October 08, 2026 18:23:25 UTC Link: Retirement: Microsoft Dev Box will be retired on September 18, 2028
Update ID: 567933 Data source: Azure Updates API
Categories: Developer tools, DevOps, Virtual desktop infrastructure, Microsoft Dev Box, Retirements
Summary:
What was updated
Microsoft announced the retirement of Microsoft Dev Box. The service will be fully retired on September 18, 2028, and is currently in maintenance mode.
Key changes or new features
No new features will be added; Microsoft Dev Box is now in maintenance mode. The service will begin its shutdown process on September 14, 2026, leading up to its complete retirement in 2028. After retirement, Microsoft Dev Box will no longer be available.
Target audience affected
Developers and IT professionals who use Microsoft Dev Box for cloud-based development environments are directly impacted. Organizations leveraging Dev Box for developer onboarding, environment provisioning, or secure development workflows should take note.
Important notes if any
Users should begin planning migration strategies to alternative solutions well before the retirement date. After September 18, 2028, all resources and access related to Microsoft Dev Box will be discontinued. No new features or enhancements will be delivered during the maintenance period. Early planning is recommended to avoid disruption to development workflows.
For more details, see the official update: https://azure.microsoft.com/updates?id=567933
Details:
Azure Update Report: Retirement of Microsoft Dev Box on September 18, 2028
Background and Purpose of the Update:
Microsoft has announced the planned retirement of Microsoft Dev Box, with a final retirement date set for September 18, 2028. This update serves as an advance notification to customers and IT professionals, allowing for sufficient time to plan migration strategies and transition workloads away from Microsoft Dev Box. The purpose of this update is to ensure transparency and provide a clear timeline for the service’s deprecation.
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:
Microsoft Dev Box will be retired on September 18, 2028, with the closing-down process starting September 14, 2026; the service is now in maintenance mode, and IT professionals must plan to migrate workloads and dependencies to alternative solutions before the retirement date to ensure uninterrupted operations.
Published: October 08, 2026 18:20:34 UTC Link: Retirement: Azure Deployment Environments will be retired on February 22, 2027
Update ID: 567934 Data source: Azure Updates API
Categories: Developer tools, DevOps, Azure Deployment Environments, Retirements
Summary:
What was updated
Azure announced the retirement of Azure Deployment Environments, effective February 22, 2027.
Key changes or new features
Azure Deployment Environments will no longer be available after February 22, 2027. The service will begin its shutdown process starting September 14, 2026. No new features or enhancements will be added; this is a retirement notice.
Target audience affected
Developers, DevOps engineers, and IT professionals who use Azure Deployment Environments for managing and provisioning cloud-based development, testing, or staging environments.
Important notes if any
Users must plan to migrate workloads and resources to alternative solutions before the retirement date to avoid service disruption. After February 22, 2027, all resources and environments managed by Azure Deployment Environments will be inaccessible. Microsoft recommends evaluating other Azure services or third-party solutions for environment management. Early planning and migration are advised to ensure business continuity. For more details and guidance, refer to the official Azure Update link.
Details:
Azure Update Report: Retirement of Azure Deployment Environments (February 22, 2027)
Background and Purpose of the Update
Azure Deployment Environments is scheduled for retirement on February 22, 2027. This update is part of Microsoft’s lifecycle management for Azure services, ensuring customers are informed well in advance to plan for service migration or decommissioning. The purpose is to provide clarity on service availability and to minimize disruption by giving a clear timeline for the retirement process.
Specific Features and Detailed Changes
Azure Deployment Environments, which facilitates the creation and management of cloud environments for development, testing, and production, will no longer be available after the retirement date. The closing-down process will commence on September 14, 2026, marking the start of a transition period where the service will gradually wind down. After February 22, 2027, all features, APIs, and management capabilities associated with Azure Deployment Environments will be discontinued, and the service will be inaccessible.
Technical Mechanisms and Implementation Methods
The retirement process will involve disabling new resource creation, restricting access to management interfaces, and eventually shutting down all existing environments provisioned through Azure Deployment Environments. Customers will need to migrate their workloads, templates, and environment configurations to alternative Azure services or solutions before the retirement date. Microsoft typically provides migration guidance and tools to facilitate this process, but specific mechanisms for this service’s retirement will be communicated closer to the transition period.
Use Cases and Application Scenarios
Azure Deployment Environments is commonly used in scenarios where teams require repeatable, consistent, and secure cloud environments for application development, testing, or staging. It supports DevOps workflows, CI/CD pipelines, and collaborative projects by enabling self-service environment provisioning. With its retirement, organizations will need to reassess their environment provisioning strategies and consider alternatives such as Azure Resource Manager (ARM) templates, Azure DevTest Labs, or other environment orchestration tools within Azure.
Important Considerations and Limitations
Integration with Related Azure Services
Azure Deployment Environments often integrates with services such as Azure DevOps, GitHub Actions, Azure Resource Manager, and Azure DevTest Labs to enable automated environment provisioning and management. With its retirement, customers will need to leverage these related services for environment orchestration, resource management, and CI/CD integration. Transitioning to ARM templates or DevTest Labs may require adjustments to existing workflows and automation scripts.
Summary Sentence
Azure Deployment Environments will be retired on February 22, 2027, with a closing-down process beginning September 14, 2026; customers should plan to migrate their workloads and environment provisioning workflows to alternative Azure services to avoid disruption.
Published: October 08, 2026 17:29:30 UTC Link: Generally Available: Exceptions in WAF for Azure Application Gateway and Azure Front Door
Update ID: 574343 Data source: Azure Updates API
Categories: Launched, Networking, Security, Application Gateway, Azure Front Door, Web Application Firewall, Features
Summary:
What was updated
The Exceptions feature for Web Application Firewall (WAF) on Azure Application Gateway and Azure Front Door is now generally available.
Key changes or new features
With this update, users can now configure custom exceptions for WAF rules. This allows you to exclude specific request attributes (such as headers, cookies, or query strings) from WAF evaluation, reducing false positives and enabling more granular control over security policies. Exceptions can be applied to both managed and custom rules, and are available through the Azure Portal, ARM templates, PowerShell, and CLI.
Target audience affected
This update is relevant for developers and IT professionals managing web applications protected by Azure Application Gateway WAF or Azure Front Door WAF. Security administrators and DevOps teams who need to fine-tune WAF policies will benefit most.
Important notes if any
Implementing exceptions helps reduce application disruptions caused by false positives, improving the overall user experience. Careful configuration is recommended to maintain security while minimizing unnecessary rule triggers. For more details and configuration guidance, refer to the official documentation: https://aka.ms/waf-exceptions.
Details:
Azure Update Report: Generally Available – Exceptions in WAF for Azure Application Gateway and Azure Front Door
Background and Purpose of the Update:
Azure Web Application Firewall (WAF) is designed to protect web applications hosted on Azure Application Gateway and Azure Front Door from common threats and attacks, such as SQL injection, cross-site scripting, and other OWASP Top 10 vulnerabilities. However, certain legitimate application behaviors or requests may inadvertently trigger WAF rules, resulting in false positives and blocking valid traffic. The introduction of exceptions addresses this challenge by allowing administrators to fine-tune WAF rule enforcement, thereby improving application compatibility and reducing unnecessary disruptions.
Specific Features and Detailed Changes:
With this update, exceptions for WAF rules are now generally available for both Azure Application Gateway and Azure Front Door. This feature enables users to define granular exceptions to WAF rules, allowing specific requests or patterns to bypass certain WAF rules without disabling the rule entirely. Administrators can specify exceptions based on request attributes such as URI, headers, query strings, or other relevant criteria. This enhancement provides greater flexibility and control over WAF rule enforcement, ensuring that only malicious traffic is blocked while legitimate requests are allowed.
Technical Mechanisms and Implementation Methods:
Exceptions are configured within the WAF policy associated with either Azure Application Gateway or Azure Front Door. Administrators can create exception rules using the Azure Portal, Azure CLI, or ARM templates. The exceptions are evaluated during WAF rule processing, and if a request matches the defined exception criteria, the corresponding WAF rule is skipped for that request. This mechanism ensures that exceptions are applied in real-time, minimizing latency and maintaining the overall security posture of the application.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
Exceptions are integrated directly into WAF policies for Azure Application Gateway and Azure Front Door. These services can be managed via Azure Portal, Azure CLI, and ARM templates, allowing for seamless integration with existing Azure resource management workflows. Exceptions complement other security features such as custom rules, managed rule sets, and logging, providing a comprehensive approach to web application protection within the Azure ecosystem.
Summary Sentence:
Azure Web Application Firewall now supports generally available exceptions for Azure Application Gateway and Azure Front Door, enabling fine-tuned rule enforcement to reduce false positives and enhance application compatibility while maintaining robust security.
Published: October 08, 2026 17:24:34 UTC Link: Public Preview: Microsoft Agent 365 integration with Azure API Management
Update ID: 574204 Data source: Azure Updates API
Categories: In preview, Integration, Internet of Things, Mobile, Web, API Management, Feature
Summary:
What was updated
Microsoft Agent 365 integration with Azure API Management is now available in public preview.
Target audience affected
Developers and IT professionals managing APIs, especially those using Microsoft Agent 365 and Azure API Management in enterprise environments. This is particularly relevant for teams responsible for API governance, security, and compliance.
Details:
Azure Update Report: Public Preview – Microsoft Agent 365 Integration with Azure API Management
Background and Purpose of the Update
The public preview of Microsoft Agent 365 integration with Azure API Management addresses the need for centralized governance and runtime enforcement for MCP (Microsoft Cloud Platform) servers and tools. This integration is designed to streamline the management of APIs and services by connecting Microsoft Agent 365’s governance capabilities directly with Azure API Management, enabling organizations to enforce policies and maintain compliance across their API infrastructure.
Specific Features and Detailed Changes
With this integration, organizations gain the ability to discover and connect their MCP servers and tools to Azure API Management. The update introduces mechanisms for centralized governance, allowing IT administrators to apply consistent policies and controls across APIs managed by Azure API Management. Runtime enforcement is enhanced, ensuring that policies set within Microsoft Agent 365 are actively enforced during API operations. The integration provides a unified interface for managing API lifecycle, security, and compliance, leveraging both Microsoft Agent 365 and Azure API Management functionalities.
Technical Mechanisms and Implementation Methods
The integration operates by linking Microsoft Agent 365’s governance framework with Azure API Management’s runtime policy enforcement engine. MCP servers and tools can be registered and discovered within Azure API Management, enabling administrators to apply governance policies from Microsoft Agent 365 directly to APIs. Runtime enforcement is achieved through Azure API Management’s policy engine, which executes the governance rules during API calls. The technical implementation likely involves secure authentication and authorization between Microsoft Agent 365 and Azure API Management, as well as API connectors or extensions that facilitate communication and policy synchronization.
Use Cases and Application Scenarios
Typical use cases include organizations seeking to enforce consistent security, compliance, and operational policies across their API ecosystem. For example, enterprises managing multiple MCP servers and tools can leverage this integration to ensure that all APIs adhere to corporate governance standards, with runtime enforcement preventing unauthorized access or policy violations. Application scenarios include regulated industries (such as finance or healthcare) where compliance and auditability are critical, as well as large enterprises with distributed API infrastructure requiring centralized control.
Important Considerations and Limitations
As this integration is in public preview, it may not offer full production-level support or feature completeness. IT professionals should validate compatibility with their existing MCP servers and tools and assess the maturity of the integration before deploying in mission-critical environments. There may be limitations in policy granularity, scalability, or interoperability with other Azure services. Organizations should monitor the preview’s release notes and documentation for updates, bug fixes, and feature enhancements.
Integration with Related Azure Services
The integration is tightly coupled with Azure API Management, leveraging its policy enforcement and API lifecycle management capabilities. It also connects with Microsoft Agent 365’s governance framework, providing a bridge between centralized policy management and runtime enforcement. This update may complement other Azure services such as Azure Active Directory for authentication, Azure Monitor for observability, and Azure Security Center for compliance and security monitoring.
Summary Sentence
The public preview of Microsoft Agent 365 integration with Azure API Management enables organizations to connect centralized governance and runtime enforcement for MCP servers and tools, providing enhanced policy management and compliance across their API infrastructure.
Published: October 08, 2026 14:17:44 UTC Link: Announcing: Multiparty private offers in Microsoft Marketplace expands to Hong Kong
Update ID: 571831 Data source: Azure Updates API
Categories: Announcement
Summary:
What was updated
Multiparty private offers in Microsoft Marketplace are now available in Hong Kong.
Key changes or new features
This update enables Microsoft partners to create and manage multiparty private offers for customers in Hong Kong via the Microsoft Marketplace. Multiparty private offers allow multiple partners (such as ISVs and resellers) to collaborate on customized, private deals for third-party cloud and AI solutions. This expansion helps partners reach new markets and customers by leveraging existing relationships and streamlining the procurement process.
Target audience affected
ISVs (Independent Software Vendors), resellers, system integrators, and other Microsoft partners operating in or targeting the Hong Kong market. IT professionals and procurement teams managing cloud and AI solution purchases are also impacted.
Important notes if any
Developers and IT professionals can now access a broader range of third-party solutions through private, customized offers in Hong Kong. Partners should review Marketplace requirements and ensure compliance for multiparty deals. This update supports faster deal cycles and greater flexibility in solution procurement and deployment for enterprise customers in the region.
Data source: Using API data
Link: https://azure.microsoft.com/updates?id=571831
Details:
Azure Update Report: Multiparty Private Offers in Microsoft Marketplace Expands to Hong Kong
Background and Purpose of the Update:
The expansion of Multiparty Private Offers (MPO) in Microsoft Marketplace to Hong Kong is designed to enhance the procurement process for third-party cloud and AI solutions. This update allows Microsoft partners—including software vendors and resellers—to collaborate more effectively and reach new customer segments in the Hong Kong region. The primary goal is to enable software companies to leverage established partner relationships to accelerate market entry and adoption of their 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 expansion of Multiparty Private Offers in Microsoft Marketplace to Hong Kong enables Microsoft partners to collaboratively deliver tailored third-party cloud and AI solutions to local customers, streamlining procurement and supporting market growth through established partner relationships.
This report was automatically generated - 2026-10-09 03:05:25 UTC