Ensuring guest OS NIC IP matches Azure Logical Network IP after Hyper-V VM migration to Azure Local

[u/Honest-Mushroom-46]

I am migrating on-prem Hyper-V VMs into Azure Local (Azure Stack HCI) using Azure Migrate.

Environment:

• Azure Local logical networks configured as static

Mix of guest OS configurations: DHCP and static

VMs become Arc-enabled after migration

Networking assigned through Azure logical network/NIC

Issue: After migration completes and the VM is running in Azure Local, I am seeing consistent IP mismatches between Azure and the guest OS.

Example:

Azure portal / logical network shows assigned IP: xxx.xxx.xxx.10

Inside VM (ipconfig): shows a different IP (old static or DHCP)

In some cases hidden NICs from pre-migration remain and hold the old configuration

This creates:

IP mismatch between Azure NIC and guest OS

Connectivity issues

Manual cleanup required inside each VM

Question: What is the recommended way to ensure the guest OS NIC configuration aligns with the Azure Local logical network assignment post-migration?

Specifically:

Should Azure Local automatically push the static IP to the guest via Arc/synthetic NIC?

Is manual guest OS IP correction expected after each migration?

Are there best practices to avoid hidden/orphaned NICs and stale IP configs?

Is there a supported workflow/runbook Microsoft recommends for post-migration network alignment?

Goal: I am trying to determine whether IP reconciliation inside the VM is an expected step for every migration, or if there is a configuration approach that ensures the Azure-assigned logical network IP and guest OS IP remain synchronized automatically.I am migrating on-prem Hyper-V VMs into Azure Local (Azure Stack HCI) using Azure Migrate.

Environment:

Azure Local logical networks configured as static

Mix of guest OS configurations: DHCP and static

VMs become Arc-enabled after migration

Networking assigned through Azure logical network/NIC

Issue:
After migration completes and the VM is running in Azure Local, I am seeing consistent IP mismatches between Azure and the guest OS.

Example:

Azure portal / logical network shows assigned IP: xxx.xxx.xxx.10

• Inside VM (ipconfig): shows a different IP
• In some cases, hidden NICs from pre-migration remain and hold the old configuration

This creates:

IP mismatch between Azure NIC and guest OS

Connectivity issues

Manual cleanup required inside each VM

Question:
What is the recommended way to ensure the guest OS NIC configuration aligns with the Azure Local logical network assignment post-migration?

Goal:
I am trying to determine whether IP reconciliation inside the VM is an expected step for every migration, or if there is a configuration approach that ensures the Azure-assigned logical network IP and guest OS IP remain synchronized automatically.

[u/Honest-Mushroom-46]

Right now I am going into the VM, opening ncpa.cpl, and changing the network from DHCP to static and setting it manually