Cross-subscription move of a running VM partially succeeded. 4 out of 7 resources stuck in source subscription (NIC, IP, NSG, VNET)

Hello Nevotek, it looks like you got 3 of 7 resources over but NIC, IP, NSG and VNet keep erroring out with InternalServerError. That typically points at locks, missing dependencies in the move list or a stuck move operation. Here’s a checklist you can run through to get those last four pieces into the target subscription without interrupting the VM (or at least minimize downtime):

1. Check for stuck or overlapping move operations

• In the Azure portal Activity Log, filter on “Move resources” and see if any move is still in progress or failed and left stale locks.
• If you spot a stuck move, cancel it or wait up to four hours for Azure to automatically clear the locks.

2. Remove any resource or resource-group locks

• Go to SourceRG and TargetRG > Locks and delete Read-only/Delete locks on the VM and its NIC, IP, NSG and VNet.
• You can also run in Cloud Shell: az lock list --resource-group az lock delete --name --resource-group

3. Validate the move scenario

• Make sure all dependencies are explicitly included in the move (the NIC, IP, NSG, VNet).
• Run a validation via CLI or PowerShell: az resource invoke-action --action validateMoveResources --ids /subscriptions//resourceGroups/
• Address any warnings/errors from that command before retrying.

4. Check target-subscription quotas

• In the portal go to Subscriptions > > Usage + quotas, confirm you have enough vCore, IP, NSG, VNet limits.
• If you’re hitting a quota, request an increase.

5. Retry the move in one shot

• Using Azure PowerShell: Move-AzResource -DestinationSubscriptionId -DestinationResourceGroupName -ResourceId ,,,
• Or using Azure CLI: az resource move --destination-subscription --destination-group --ids

6. If you still see “InternalServerError”

• It may be a transient platform issue—open a quick support ticket with the operation-ID from the error.
• As a last-resort for zero-downtime, consider using Azure Site Recovery to replicate the live VM into the target subscription and fail over (this preserves the public IP with minimal interruption).

Follow-up questions if you hit more snags:

1. Are you moving these 4 resources via the portal, CLI or PowerShell?
2. Do any of them still show a Read-only/Delete lock under Locks?
3. What exact error text or operation-ID appears in the Activity Log when the move fails?

Reference links

• Move resources to a new resource group or subscription

https://docs.microsoft.com/azure/azure-resource-manager/management/move-resource-group-and-subscription

• Troubleshoot ResourcesBeingMoved for VMs

https://docs.microsoft.com/azure/azure-resource-manager/management/move-limitations/virtual-machines-move-limitations

• Azure subscription and service limits, quotas, and constraints

https://docs.microsoft.com/azure/azure-subscription-service-limits

Hope this helps! Let me know what you see after running these steps. Thanks