Azure VPN Gateway Non-AZ SKUs Retired Sep 30, 2026
Azure is retiring VpnGw1-5 Non-Availability Zones SKUs for VPN Gateways on September 30, 2026, due to their lack of redundancy and lower availability. As of January 1, 2025, new gateway creation on these Non-AZ SKUs will be disabled, and existing gateways will be automatically migrated to equivalent AZ SKUs between April 2025 and October 2026. Pricing for AZ SKUs is being reduced to facilitate this transition.
- →Retirement of VpnGw1-5 Non-AZ SKUs
- →New Gateway Creation Disabled
- →Automatic Migration to AZ SKUs
- →Reduced Pricing for AZ SKUs
Deprecations (3) ›
- Retirement of VpnGw1-5 Non-AZ SKUs
Azure VPN Gateway VpnGw1-5 Non-AZ SKUs are scheduled for retirement on September 30, 2026. The service cites lack of redundancy, lower availability, and potential higher costs associated with failover solutions as reasons for the transition.
- New Gateway Creation Disabled
Effective January 1, 2025, users will no longer be able to create new VPN gateways using the VpnGw1-5 Non-AZ SKUs.
- Automatic Migration to AZ SKUs
All existing gateways on VpnGw1-5 Non-AZ SKUs will be automatically migrated to their corresponding VpnGw1-5 AZ SKUs between April 2025 and October 2026.
Enhancements (1) ›
- Reduced Pricing for AZ SKUs
To support the transition, Azure is implementing reduced pricing for AZ SKUs, effective January 1, 2025.
https://azure.microsoft.com/en-us/updates/?id=vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026
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 ·