Migration of VM from my account to a clients account but require static IP to remain

Hello Andy, you can absolutely keep your VM’s static IP – as long as you move the Public IP resource along with the VM and its NIC into the target subscription under the same Azure AD tenant. Here’s how to do it:

1. Confirm your target subscription is in the same Azure AD tenant • Moving resources (VM + NIC + Public IP) only works within the same directory. • If it’s a different tenant, you can’t directly move the Public IP resource – you’d need to redeploy, which means a new IP.
2. Use Azure Resource Manager’s “Move” feature • In the Azure portal, go to the resource group containing your VM. • Click … (More) > Move > Move to another subscription. • Select the VM, its NIC, and the Public IP resource, then pick the target subscription and resource group. • Review and start the move. The static IP address stays exactly the same. Alternatively, via PowerShell:

   
      # Example: move VM, NIC and Public IP to a new subscription/resource group
   
      $resources = @(
   
        '/subscriptions/<sourceSub>/resourceGroups/<rg>/providers/Microsoft.Compute/virtualMachines/<vmName>',
   
        '/subscriptions/<sourceSub>/resourceGroups/<rg>/providers/Microsoft.Network/networkInterfaces/<nicName>',
   
        '/subscriptions/<sourceSub>/resourceGroups/<rg>/providers/Microsoft.Network/publicIpAddresses/<pipName>'
   
      )
   
      Move-AzResource -DestinationSubscriptionId '<destSub>' `
   
                     -DestinationResourceGroupName '<destRg>' `
   
                     -ResourceId $resources
   
   

3. Post‐move validation • After the operation completes, verify in the portal that your VM’s public IP hasn’t changed. • Test connectivity from a client device to ensure everything still routes to your server.

If you discover you must move across separate Azure AD tenants (so the move API won’t work), consider these options instead of touching 500+ devices:

• Assign a DNS name (or CNAME) to your static IP and have devices connect via FQDN. Then you can repoint that DNS to any new IP.
• Use Azure Traffic Manager or Front Door in front of your VM—devices hit the front‐end domain, and you can switch backends without reconfiguring them.

Follow-up questions to make sure we’ve got all the details:

1. Is the static IP you’re using an ARM Public IP resource (not a classic/reserved IP)?
2. Is the client’s subscription under the same Azure AD directory as yours?
3. Are you using any custom NSGs or route tables that we should include in the move?

Reference list

• Move resources to a new resource group or subscription (ARM)
• Migrate a classic reserved IP address to a public IP address
• Plan migration of IaaS resources from classic to Azure Resource Manager
• Platform‐supported migration of IaaS resources from classic to ARM
• Create a VM with a static public IP address (ARM)