hi SoniaCuff. thank you for this. I am trying to do this, but instead of using powershell, just portal azure... I create the IP, add it to the NIC, and then update the OS and lose connectivity every time.
I read https://github.com/MicrosoftDocs/SupportArticles-docs/blob/main/support/azure/virtual-machines/windows/no-internet-access-multi-ip.md which said the primary IP is the only one exposed to the internet... and if the additional IP is numerically smaller it "identifies" as primary in the OS but not in the Azure environment - which wasn't the case in my scenario (10.232.2.5 primary, added 10.232.2.6 as additional)
I know this works - I am rebuilding a VM from a production VM, which does this to host 2 FTP sites on port 21 using the different internal IP as unique IP:21 for mapping the sites, mapping to 2 different URLs which map to the different external IPs.
Can you possibly think why this would not work using azure portal, instead of powershell, to create the second IP config object (internal IP)?
For completeness, I am using Dynamic allocation for the internal primary (10.232.2.5) and static for the additional internal IP (10.232.2.6)