Operating System of VM options when adding alternative IPv4 address

[Alocyte]

The changes to the IPv4 configuration trigger a warning message when updated. It is not clear how to respond to avoid loss of connectivity.

The primary IP (static internal) address assigned to my NIC configuration was 10.232.2.5. I added an alternate IP (static internal) address to the VM configuration in Azure Portal - 10.232.2.6. I followed the articles guidelines to update the Operating System (Windows Server) to add this second IP.

Answering Yes or No I have lost connectivity to the VM.

Then I read the article "No Internet access from Azure Windows VM that has multiple IP addresses" - https://learn.microsoft.com/en-US/troubleshoot/azure/virtual-machines/windows/no-internet-access-multi-ip. It states: "This issue occurs because Windows selects the lowest numerical IP address as the primary IP address regardless of the address settings in the Azure portal." A powershell script is supplied to correct the issue, but the script fails to execute in the Azure Portal "Run command" - Powershell... it just hangs. Results in the activity log: Message The resource operation completed with terminal provisioning state 'Failed'.

So, the primary IP was the lowest numerical IP value - should not have lost connectivity.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: efc2e55c-a007-e1da-a0b6-00b4397e0f13
• Version Independent ID: edadbe52-9c3e-77c9-afaa-1ae9b6454f73
• Content: No Internet access from Azure Windows VM that has multiple IP addresses - Azure
• Content Source: support/azure/virtual-machines/windows/no-internet-access-multi-ip.md
• Service: virtual-machines
• GitHub Login: @genlin
• Microsoft Alias: genli

[TPavanBalaji]

@Alocyte Thanks for your feedback! We will investigate and update as appropriate.

[SaibabaBalapur-MSFT]

@Alocyte I'm going to assign this to the document author so they can take a look at it accordingly.

@genlin Please review it.

[Alocyte]

https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000Cx2aCAC The process here describes how to remove the NIC of the origninal source of the VM backup - which needs to be removed PRIOR to reconfiguring the Primary IP and Secondary IP - else the operating system malfunctions and you have to reset the NIC. It took me forever to discover, as the operating system doesn't even show these items in the device manager by default. I had success the first attempt after removing the "Ghost NICs" - once removed there is no warning pop-up and it works when following the process described in the original post.

[genlin]

@Alocyt, Thanks for sharing the information. Glad to know the issue is resolved after removing the unavailable NICs. #please-close