New Azure networks no longer reach the internet on their own
Since 31 March 2026 a new virtual network starts private. A fresh server that cannot download updates is the usual first symptom.
Virtual networks created after 31 March 2026 default to private subnets. Machines in them need an explicit outbound route, such as a NAT gateway, before they can reach the internet. Existing networks keep working as before.
For as long as most of us have used Azure, a new virtual machine could reach the internet the moment it started. You did not configure anything. Azure quietly assigned an outbound address behind the scenes and the machine could fetch its updates, call an API, or do anything else it liked.
That convenience was also a hole. A server that nobody decided should talk to the internet could talk to the internet, from an address you did not control and could not predict.
What changed
Microsoft retired that default on 31 March 2026, after moving the date from September 2025. Virtual networks created after it start with private subnets. A machine placed in one has no path out until someone gives it one on purpose. The supported choices are a NAT gateway attached to the subnet, a standard load balancer with outbound rules, or a public address on the machine itself.
The scope is narrower than the early headlines suggested. Existing virtual networks are not changed, and machines added to them, old or new, carry on as before unless you switch the subnet to private yourself.
How it shows up
Usually as a puzzle. Somebody builds a new environment for a project, from a template that has worked for years. The machines start. Then Windows will not activate, updates fail, the deployment script cannot download a package, and an hour goes on checking firewalls that are not the problem. Microsoft's documentation notes that activation and Windows updates are among the services that do not function in a private subnet without an explicit route out.
If that sounds familiar from the last few months, this is very likely why.
What to do
For new work, put the outbound method in the template, so every network is born with one. For most small environments a NAT gateway is the simplest choice. Note that one gateway serves one virtual network, so count them when you estimate cost.
For older networks there is no deadline, and we would still move them. An explicit route means you know which address your traffic leaves from, which matters the first time a supplier asks you for one to put on an allow list. It also means a machine cannot reach the outside world by accident.
Where X-Axis fits
Network reviews and template updates are routine parts of our Azure consulting. How we work.
Do this month
Tick them off as you go. Nothing is saved or sent.
Sources
Want a second pair of eyes on this?
How our consulting works