@syed Mohsin Firstly, Apologies for the delay response!
When you use Azure Resource Mover to move a virtual machine (VM) from one virtual network (VNet) to another within the same resource group, you may encounter an issue where the source and destination resource groups cannot have the same name for the OS disk. This is because Azure Resource Mover creates a copy of the VM in the destination VNet, and it needs to assign a new name for the OS disk to avoid conflicts.
To resolve this issue, you can follow these steps:
Before you start the move operation, rename the OS disk in the source VM to a unique name that is different from the default name. You can do this using the Azure Portal, Azure CLI, or PowerShell.
Initiate the move operation using Azure Resource Mover.
During the move operation, when you are prompted to provide a new name for the OS disk in the destination VNet, use a name that is different from the name of the OS disk in the source VM. You can choose any unique name that meets Azure naming conventions.
Complete the move operation.
Once the move is completed, verify that the VM is running in the new VNet and that it has the correct OS disk attached.
By following these steps, you should be able to move your VM to a new VNet within the same resource group, even if the source and destination resource groups cannot have the same name for the OS disk.
If you have any additional questions or need further clarification, please let me know.
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.