Azure Migrate - unable to set IP address on protected machines

Question

Azure Migrate - unable to set IP address on protected machines

AnTu31 26

Hi

In Azure Migrate, the portal experience for modifying the settings of protected VMs seems to have changed and I am now unable to set the IP address from being just DHCP assigned.
There used to be an Edit button at the top but that has now disappeared it seems.
How can I now change the IP address please?

User's image

AnTu31 26 Reputation points

2025-04-28T12:25:39.2566667+00:00

I was able to do this in the RSV behind the AzMig project.
Not sure why I can't do it in the project itself.

Accepted answer

0 additional answers

Your answer

AnTu31 26 Reputation points

2025-04-28T12:25:39.2566667+00:00

I was able to do this in the RSV behind the AzMig project.
Not sure why I can't do it in the project itself.

Answer 1

Hi @AnTu31

It seems like the Azure Migrate portal interface has undergone some updates, which might have altered the way settings are modified for protected VMs

1.Static IP Assignment: Azure Migrate typically assigns dynamic IP addresses (via DHCP) during replication. However, you can configure static IPs manually:

Navigate to the Network Interface Card (NIC) settings of the VM in the Azure portal.

Change the IP allocation method from Dynamic to Static and specify the desired IP address.

2.Post-Migration Configuration: If the option to modify IP settings during the migration process is no longer available, you might need to adjust these settings after the migration is complete. Ensure that the target virtual network (VNet) in Azure has the same address space as your on-premises network to avoid conflicts.

3.Resource-Specific View (RSV): Since you mentioned being able to make changes in the RSV, it might be worth revisiting the RSV for the specific NIC associated with the VM. Sometimes, settings are accessible at the resource level rather than through the project interface.

Please let me know if you face any challenge here, I can help you to resolve this issue further

User's image

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

AnTu31 26 Reputation points

2025-04-28T14:09:16.77+00:00

Thanks for your response,
The 3rd method - assign the IP via RSV - is the workaround I used.

You'd always want to predefine the IP address prior to migration so the VM boots up first time with the correct IP, matching FW rules etc. Seems strange for MS to remove that functionality from the AzMig project, and make it harder by having to use the RSV instead.
I'm hoping its just a glitch with the latest portal experience.
Ashok Gandhi Kotnana 6,680 Reputation points Microsoft External Staff Moderator

2025-04-28T14:18:06.4033333+00:00

Hi @AnTu31

I agree with your point, also the document shows that we can do it the view looks bug/glitch

https://learn.microsoft.com/en-us/azure/azure-local/migrate/migrate-maintain-ip-addresses?view=azloc-2504&tabs=windows#set-up-ip-migration

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Share via

Azure Migrate - unable to set IP address on protected machines

0 additional answers

Your answer