For those with projects and changes planned or underway on Azure default outbound access being disabled, there has been a reprieve with a new extension to the end of March 2026 allowing a little more time for remediation planning.
Update: The retirement date for default outbound access has been extended to March 31, 2026
The retirement date for default outbound access has been extended to March 31, 2026. This change aligns with the broader Azure Virtual Network (VNet) update and replaces the previously communicated September 30, 2025 date.
Starting March 31, 2026, newly created VNets will default to using private subnets. This means:
- Explicit outbound connectivity (e.g., via NAT Gateway, UDR, or other methods) must be configured to access public endpoints on the Internet or Microsoft services.
- Default outbound access will be disabled by default, but not removed. Customers who do not configure an outbound method will lose internet connectivity from their Batch nodes.
- Review your current Batch pool configurations, especially those using simplified node communication without public IPs.
- Plan to implement an explicit outbound method before the March 2026 deadline.
Azure ID: 515484
Default Internet outbound access for Simplified node communication Batch pools without public IP addresses will be retired on 30 September 2025
How and when default outbound access is provided
Feature Update: Default behaviour for newly created virtual networks will be private
