How to Set Azure Virtual Networks as Private Before March 31, 2026

Select Language:

If you’re creating new virtual networks (VNets) after March 31, 2026, you’ll need to be aware of a new change. This update only affects VNets that are created after that date. Existing VNets and the virtual machines (VMs) running within them will continue to operate just as they do now — no disruptions.

Here’s what the change means for new VNets: They will no longer automatically have internet access. If you want your VMs in these new networks to connect to the internet, you’ll need to set up outbound connectivity explicitly. You can do this using a few options:

Azure NAT Gateway: Helps your virtual machines access the internet without exposing them to inbound traffic.
Azure Load Balancer with outbound rules: Allows you to configure outbound internet access for your VMs.

To summarize:

Any new VNets won’t have internet access by default.
To give VMs in these networks internet access, configure either a NAT Gateway or set up outbound rules with a Load Balancer.

This change aims to improve security by making outbound internet access an explicit setup rather than automatic. If you’re planning to create new VNets, make sure to set up one of these options to keep your VMs connected to the internet.

Did this guidance help you? If so, please let us know by giving a thumbs up or accepting the answer. Sharing your feedback can also help others facing the same situation.