Who rated this post

Per Microsoft:

https://azure.microsoft.com/en-gb/updates/default-outbound-access-for-vms-in-azure-will-be-retired-t...

On 30 September 2025, default outbound access connectivity for virtual machines in Azure will be retired. After this date, all new VMs that require internet 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.

Direct-attached public IP seems to be a doable option. 

EDIT:

My expectation is that a marketplace-deployed template will no longer provision a public IP address and attach it to a VM.  I figure you'll have to do that manually, or in your playbook as a separate step.

<Conjecture/Theory>:  I would imagine, eventually, Azure would start charging money for having a public IPv4 address.  This may also be a way to steer to IPv6. Combine this with the announcement of IPv6 for Gateway Load-Balancer, the pieces are now in place.

https://azure.microsoft.com/en-us/updates/general-availability-gateway-load-balancer-ipv6-support/

Everyone has 2 years, so start working on those Ansible playbooks! 🙂