# Azure product updates - 2026-10-09 **7 new update(s)** — first seen in this run. The last 7 day(s) are rescanned every time so late or backdated announcements are not missed. Grouped by Azure product category. Source: [Azure Updates](https://azure.microsoft.com/en-us/updates) ## Summary by category | Category | Updates | GA | Preview | Top products | | --- | ---: | ---: | ---: | --- | | [Developer tools](#developer-tools) | 2 | - | - | Microsoft Dev Box, Azure Deployment Environments | | [Compute](#compute) | 1 | 1 | - | Azure Kubernetes Service (AKS), Azure NAT Gateway | | [Databases](#databases) | 1 | 1 | - | Azure Database for PostgreSQL | | [Integration](#integration) | 1 | - | 1 | API Management | | [Networking](#networking) | 1 | 1 | - | Application Gateway, Azure Front Door, Web Application Firewall | | [Other](#other) | 1 | - | - | | ## Developer tools ### [Retirement: Microsoft Dev Box will be retired on September 18, 2028](https://azure.microsoft.com/en-us/updates?id=567933) **Status:** Retirement | **Published:** 2026-10-08 | **Products:** Microsoft Dev Box | **Tags:** Retirements Microsoft Dev Box will be retired on September 18, 2028, with a transition period starting in 2026, encouraging customers to migrate to Windows 365 for developer cloud environments. - Microsoft Dev Box enters closing-down phase starting September 14, 2026, and will be fully retired by September 18, 2028. - No new feature development will occur; existing deployments remain supported during the transition period. - Windows 365 is the recommended replacement for virtualized developer environments, reflecting Microsoft's strategic focus. - Customers should review current Dev Box usage, plan migration scenarios, validate requirements, and begin testing new workflows early to avoid disruption. ### [Retirement: Azure Deployment Environments will be retired on February 22, 2027](https://azure.microsoft.com/en-us/updates?id=567934) **Status:** Retirement | **Published:** 2026-10-08 | **Products:** Azure Deployment Environments | **Tags:** Retirements Azure Deployment Environments will be retired on February 22, 2027, requiring customers to plan and transition to alternative environment provisioning solutions to avoid service disruption. - Retirement date set for February 22, 2027, with closing-down starting September 14, 2026. - Customers must review and inventory current usage across subscriptions, projects, templates, and workflows. - Identify and validate alternative environment provisioning and developer self-service approaches. - Early migration planning and communication are critical to minimize operational and development impact. ## Compute ### [Generally Available: Managed StandardV2 NAT Gateway for AKS](https://azure.microsoft.com/en-us/updates?id=574430) **Status:** Launched | **Published:** 2026-10-08 | **Products:** Azure Kubernetes Service (AKS), Azure NAT Gateway | **Tags:** Features AKS now generally supports provisioning and managing a StandardV2 NAT Gateway for clusters using AKS-managed virtual networks, offering improved performance and zone redundancy. - StandardV2 NAT Gateway is the new default SKU for managed NAT Gateways in supported regions, replacing Standard SKU for new AKS clusters using managedNATGateway outbound type. - StandardV2 provides zone redundancy by default, higher bandwidth and throughput, and IPv6 support, enhancing cluster outbound connectivity reliability and performance. - Existing AKS clusters can migrate from Standard NAT Gateway or load balancer to StandardV2, but downgrades from StandardV2 to Standard are not supported. - StandardV2 NAT Gateway requires StandardV2 public IP addresses and prefixes, which are incompatible with existing Standard SKU public IP resources, necessitating planning for IP resource management. Documentation: [Create a Managed or User-Assigned NAT Gateway for your Azure Kubernetes Service (AKS) Cluster - Azure Kubernetes Service](https://learn.microsoft.com/en-us/azure/aks/nat-gateway) ## Databases ### [Generally Available: Azure Database for PostgreSQL flexible server in East US 3](https://azure.microsoft.com/en-us/updates?id=573691) **Status:** Launched | **Published:** 2026-10-08 | **Products:** Azure Database for PostgreSQL | **Tags:** Feature Azure Database for PostgreSQL flexible server is now generally available in the East US 3 region, expanding deployment options for customers. - Flexible server deployment is now supported in the East US 3 Azure region. - This availability provides customers with more geographic options for hosting PostgreSQL databases. - Supports full application compatibility with the community PostgreSQL engine for easy migration. - Customers can leverage Azure Database Migration Service or dump and restore methods for migration. Documentation: [What Is Azure Database for PostgreSQL flexible server? - Azure Database for PostgreSQL](https://learn.microsoft.com/en-us/azure/postgresql/overview) ## Integration ### [Public Preview: Microsoft Agent 365 integration with Azure API Management](https://azure.microsoft.com/en-us/updates?id=574204) **Status:** In preview | **Published:** 2026-10-08 | **Products:** API Management | **Tags:** Feature Microsoft Agent 365 integration with Azure API Management is now in public preview, enabling centralized governance and runtime enforcement for MCP servers and tools, enhancing security and operational control. - Organizations can discover and inventory Azure API Management gateways and MCP servers within Agent 365. - Access to MCP servers is controlled from Agent 365 with enforcement applied at runtime by Azure API Management. - The AI Gateway tier (in preview) allows tool-level access controls, activity monitoring, and threat protection using Microsoft Defender and Purview. - This integration centralizes governance for AI administrators while enabling platform teams to enforce policies within the customer’s Azure environment. ## Networking ### [Generally Available: Exceptions in WAF for Azure Application Gateway and Azure Front Door](https://azure.microsoft.com/en-us/updates?id=574343) **Status:** Launched | **Published:** 2026-10-08 | **Products:** Application Gateway, Azure Front Door, Web Application Firewall | **Tags:** Features, Security Azure Web Application Firewall (WAF) on Application Gateway and Front Door now generally supports exceptions that allow specific requests to bypass WAF inspection at granular levels, improving policy tuning and reducing false positives. - Exceptions can be configured by request URI, remote IP address, or request header name and value to bypass inspection at the rule, rule group, or managed ruleset level. - Available generally for Azure Application Gateway and Azure Front Door WAF policies via Azure portal and CLI/PowerShell commands. - Helps customers precisely tune WAF policies by excluding safe, expected requests from inspection while maintaining other protections. - Limits include up to 60 exceptions per WAF policy and per Application Gateway, with up to 600 IP addresses per exception. Documentation: [Azure Application Gateway WAF Exceptions List (Preview)](https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/application-gateway-exceptions) ## Other ### [Announcing: Multiparty private offers in Microsoft Marketplace expands to Hong Kong](https://azure.microsoft.com/en-us/updates?id=571831) **Status:** Effective | **Published:** 2026-10-08 | **Tags:** Announcement Multiparty private offers in Microsoft Marketplace have expanded to Hong Kong, enabling partners to procure third-party cloud and AI solutions for customers, enhancing market reach and customer trust. - Capability: Allows Microsoft partners to procure third-party cloud and AI solutions on behalf of customers through Marketplace. - Availability: Now expanded to include the Hong Kong market. - Customer impact: Customers benefit from trusted partners managing their cloud and AI initiatives. - Partner impact: Software companies can enter new markets by collaborating with partners who have established customer relationships. --- _Generated automatically on 2026-10-09 02:51 UTC._