How to setup Internet access after All Basic IPs be retired on September 30, 2025

Take this:

 

Starting September 30, 2025, Microsoft Azure will retire Basic SKU Public IP addresses, which means you'll need to transition to Standard SKU Public IPs or other outbound connectivity methods to maintain internet access for your virtual machines (VMs) and services.

 

BTW, seems Microsoft postponed the retirement recently!

Here’s how to prepare and set up internet access after retirement:

Migration Options
1. Upgrade to Standard SKU Public IPs
•    Why: Basic IPs will no longer work; Standard IPs offer better security and availability.
•    How: 
o    Detach the Basic IP from your VM.
o    Set the allocation method to Static.
o    Upgrade the IP to Standard SKU.
o    Re-associate the IP with the VM.
o    Use Microsoft’s upgrade script for automation.
2. Use NAT Gateway
•    Why: NAT Gateway provides scalable outbound internet access without assigning public IPs to each VM.
•    How: 
o    Create a NAT Gateway in each subnet or centralize it in a hub (hub-and-spoke topology).
o    Route traffic from spoke subnets to the hub.
o    Ensure sufficient IP addresses to avoid port exhaustion.
3. Standard Load Balancer
•    Why: Required if you're using Basic Load Balancer.
•    How: 
o    Upgrade Basic Load Balancer to Standard SKU using Microsoft’s migration script.
o    Reconfigure outbound rules accordingly.
4. ExpressRoute Gateway & App Gateway
•    If you're using these services, upgrade to their Standard SKUs as well.
•    Follow Azure’s migration guidance for each component.