unable to create Powershell object for cmdlets to move a VM using Azure Resource Mover

Hi @Emmanuel Njang (TATA CONSULTANCY SERVICES LTD),

Following up to see if the information provided by Andreas Baumgarten was helpful. If you have any further queries do let us know. we are happy to assist you further.

I got the fix:

$targetResourceSettingsObj = New-Object Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.Models.VirtualMachineResourceSettings

Hi @RakeshReddy Gurram I am now facing another issue:

When I create a move collection using this snippet below, it creates a service principal instead of a managed identity:

New-AzResourceMoverMoveCollection -Name "PS-centralus-westcentralus-demoRMS" -ResourceGroupName "RG-MoveCollection-demoRMS" -SourceRegion "centralus" -TargetRegion "westcentralus" -Location "centralus"   -EnableSystemAssignedIdentity

Also when I attempt to add a VM resource to the move collection using this command, it throws this error:

Add-AzResourceMoverMoveResource -ResourceGroupName "RG-MoveCollection-demoRMS" -MoveCollectionName "PS-centralus-westcentralus-demoRMS" -SourceId "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx xxxxxxxxxxxx/resourceGroups/

PSDemoRM/providers/Microsoft.Compute/virtualMachines/PSDemoVM" -Name "PSDemoVM" -ResourceSetting $targetResourceSettingsObj

Please assist on the solution.

Hi @Emmanuel Njang (TATA CONSULTANCY SERVICES LTD),

The error occurs because the system-assigned managed identity associated with the move collection is either missing or does not have the required RBAC permissions.

To resolve this issue:

• Recreate or re-enable the move collection with system-assigned managed identity enabled
• Ensure the identity has the required roles:
  • Contributor
    • User Access Administrator
    • Wait a few minutes for identity propagation
    • Retry adding the resource to the move collection

After performing these steps, the Add-AzResourceMoverMoveResource operation should succeed.