Issue With adding Secondary IPs to Azure VM

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Issue With adding Secondary IPs to Azure VM

L2 Linker

Recently, we've been having an issue with assigning secondary IPs to our Azure PA VMs where if we add a new IP, it doesn't seem to apply until we add a second IP. After the 2nd IP is added, the first starts working but the 2nd doesn't work. The Palo interfaces are set to DHCP and IPs are assigned to the Azure NIC.


Same issue on 3 firewalls in different regions running PAN-OS 9.1.7/8.


Just wondering if anyone else has seen this issue? Also, unsure if it's an Azure or PAN issue.


L4 Transporter

Hello @Ash2k 

Change the IP assignment in Azure to static (for all fw IPs).

Configure the primary IP on the firewall with the correct network mask (e.g. /24). Configure all further IPs on the same NIC with /32

  • 1 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!