Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,314 questions
Azure Basic Public IP will be retired
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 27%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA3%3C/text%3E%3C/svg%3E)
AdamTyler-3590
275
Reputation points
I've noticed this warning message in the Azure user interface while attempting to provision a new Basic Public IP address.
This is alarming. Today we use Basic Public IP addresses and the "Associate public IP address" mechanism to support connectivity to our entire Azure datacenter footprint. The IP association pipes our Basic public IP into the private vnet IP of the WAN interface of an Azure based FortiGate firewall.
When attempting to use a Standard Public IP for this purpose I am getting the following error. So it appears that Microsoft is deprecating Basic public IP addresses and has disabled Standard addresses for our purposes. Effectively removing our ability to use our tenant as of September 2025.
Is this error indicating that ALL Public addresses need to be Standard or Basic? Like you can't mix and match? If so, what is the process for upgrading a Basic IP without losing your static and access to our FortiGate appliance? I did find an upgrade button in the Basic public IP interface and got this message.
Last but not least, when creating a Standard Public IP, you get this new option. For our purposes this WAN IP will be associated with our perimeter firewall handling outbound WAN NAT for internal Azure VMs as well as site-to-site VPNs to other offices and client VPN. which option is recommended in this case?