Transition to a new method of internet access for your VMs in Azure

Hello @ Sheik Mohamed Yasar,

Thanks for reaching out to Microsoft Q&A.

This change won’t break your existing VMs’ Internet connectivity.

By design, Azure doesn’t retroactively remove the default outbound IP from already-deployed VNets or VMs. That means:

• Your 3 running VMs and any new VMs you spin up in that same VNet will continue to get default outbound IPs unless you explicitly make their subnet “private” (defaultOutboundAccess=false) or attach an explicit outbound solution (NAT Gateway, public IP, Load Balancer outbound rule, etc.).

• Nothing happens automatically to existing VMs you only lose that implicit outbound path if and when you manually switch the subnet to private (and then stop/deallocate the VMs so the change can take effect).

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Hi,

Your existing VNet with 3 VMs will not be affected by the change. If the VMs are using Default Outbound Access now it will still work after March 31st.

In the various official announcements, articles, etc., they have consistently said existing VNets/VMs will not be changed, and thus still able to use Default Outbound Access.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP