After September 30, 2025, new virtual networks will default to requiring explicit outbound connectivity methods instead of having a fallback to default outbound access connectivity. All virtual machines that require public endpoint access will need to use explicit outbound connectivity methods such as Azure NAT Gateway, Azure Load Balancer outbound rules, or a directly attached Azure public IP address. "
Due to this announcement, our code has been updated to support NAT gateways for outbound internet access. A default_outbound_access_enabled attribute has been added to the subnets variable, which is set to false by default. This requires that outbound internet access be provided by a NAT gateway or other method.
If the customer has an ALZ that provides outbound access, User Defined Routes (UDRs) should be used to route outbound traffic to the appropriate destination within the ALZ, otherwise, a NAT gateway should be used.
Create Public IPs Example
A NAT gateway requires one or more public IP addresses. Below is an example of how to create the public IPs that will be used by the NAT gateway(s). The public IPs must be created in the same resource group as the NAT gateway it will be attached to.
See below for an example of a NAT gateway configuration. The same NAT gateway cannot be used on more than one virtual network, so one must be created for each.