# Azure product updates - 2026-08-24 **4 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 | | --- | ---: | ---: | ---: | --- | | [Compute](#compute) | 2 | 1 | - | Azure Kubernetes Service (AKS), App Service | | [Databases](#databases) | 1 | - | - | Azure Database for PostgreSQL | | [Networking](#networking) | 1 | 1 | - | Application Gateway, Web Application Firewall | ## Compute ### [Generally Available: eBPF host routing in Advanced Container Networking Services for AKS](https://azure.microsoft.com/en-us/updates?id=569873) **Status:** Launched | **Published:** 2026-08-24 | **Products:** Azure Kubernetes Service (AKS) | **Tags:** Features, Microsoft Build, Services eBPF Host Routing in Advanced Container Networking Services for AKS is now generally available, enhancing Kubernetes networking performance by bypassing iptables and improving latency, throughput, and scalability for large-scale and latency-sensitive workloads. - Capability: Moves packet forwarding and routing into the Linux kernel using eBPF, bypassing iptables to reduce latency, CPU usage, and network hops. - Availability: Generally available for AKS clusters running Ubuntu 24.04 or Azure Linux 3.0 nodes; not supported on Windows nodes, Confidential VMs, Pod Sandboxing, or hybrid node scenarios. - Customer Impact: Enables better network performance and scalability for high-throughput, real-time, and AI/ML workloads with a controlled node rotation rollout to maintain connection continuity. - Limitations: Cannot be enabled selectively per node; incompatible with Static Egress Gateway and Istio Ambient with ACNS Performance mode; iptables rules in host namespace are blocked when enabled. Documentation: [eBPF Host Routing with Advanced Container Networking Services (ACNS) - Azure Kubernetes Service](https://learn.microsoft.com/en-us/azure/aks/container-network-performance-ebpf-host-routing) ### [Retirement: Support for Node 22 LTS ends on April 30, 2027](https://azure.microsoft.com/en-us/updates?id=567334) **Status:** Retirement | **Published:** 2026-08-24 | **Products:** App Service | **Tags:** Retirements Support for Node 22 LTS on Azure App Service will end on April 30, 2027, requiring customers to upgrade to Node 24 LTS to maintain security and support. - Node 22 LTS will no longer receive security updates or customer support after April 30, 2027. - Apps running on Node 22 LTS will continue to operate but may be vulnerable to security risks. - Customers must upgrade their App Service apps to Node 24 LTS before the retirement date to avoid potential vulnerabilities. - This change aligns with Azure App Service's language runtime support policy to ensure secure and supported environments. Documentation: [Language Runtime Support Policy - Azure App Service](https://learn.microsoft.com/en-us/azure/app-service/language-support-policy) ## Databases ### [Announcing: Extended Support for Azure Database for PostgreSQL Flexible Server](https://azure.microsoft.com/en-us/updates?id=569526) **Status:** Effective | **Published:** 2026-08-24 | **Products:** Azure Database for PostgreSQL | **Tags:** Announcement Azure Database for PostgreSQL Flexible Server now offers Extended Support to provide critical security updates and technical support for eligible PostgreSQL versions after community support ends, enabling customers to upgrade on their own timeline with confidence. - Provides critical security updates, bug fixes, and Azure technical support for PostgreSQL versions after community support ends, excluding new features or minor version upgrades. - Automatically enrolls eligible servers running unsupported PostgreSQL versions into Extended Support starting August 1, 2026, with a one-month grace period for versions 11, 12, and 13. - Extended Support billing applies only to running servers and stops once the server is upgraded to a supported PostgreSQL version; customers cannot opt out without upgrading. - Designed as a temporary bridge to maintain secure, compliant workloads while planning upgrades to newer PostgreSQL versions like 15 or 16 for improved performance and support. Documentation: [Extended Support in Azure Database for PostgreSQL Flexible Server - Azure Database for PostgreSQL](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/extended-support) ## Networking ### [Generally Available: Custom block response code and body for Application Gateway WAF](https://azure.microsoft.com/en-us/updates?id=569504) **Status:** Launched | **Published:** 2026-08-24 | **Products:** Application Gateway, Web Application Firewall | **Tags:** Security, Feature Azure Web Application Firewall (WAF) on Application Gateway is now generally available with the ability to customize block response status codes and bodies, providing customers greater control over blocked request handling. - Supports custom response status codes (e.g., 200, 429) and messages for blocked requests at the WAF policy level. - Available for Azure WAF integrated with Application Gateway, excluding Application Gateway for Containers WAF. - Limits include up to 20 WAF policies with custom responses per Application Gateway and a 32 KB max size for response bodies. - Custom block response bodies must be base64 encoded when configured via Azure Resource Manager API. Documentation: [Configure a Custom Response for Azure Application Gateway - Azure Web Application Firewall](https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/configure-custom-response-code) --- _Generated automatically on 2026-08-24 23:26 UTC._