Jun 10 2017 08:04 PM
Jun 12 2017 09:35 PMSolution
Sep 08 2017 12:28 PM
Can you share steps how to do so? I am trying to share a subscription but nothing is happening.
Thanks in advance.
Sep 08 2017 12:52 PM
You can try the procedures of the following links:
Oct 24 2017 08:02 PM
If the both subscriptions are in same tenant you can migrate VMs between subscriptions.
Use following doc
If you want to move resources between two tenents then you have to use alternative method. We can use Azure Storage explore to copy VHDs from one SA to other SA in different tenant. Then using PowerShell or Azure CLI script we can create a VM from that VHD.
Aug 22 2018 07:18 PM
Hello, I have not tested this procedure with Linux VMs, but I recommend that you do a test and if you can not find it, I believe you can find the most appropriate procedure in the same place where the procedure I recommended for Windows VMs is.
Good luck and sucess!
Sep 24 2023 05:25 AM - edited Sep 24 2023 05:37 AM
Yes, it is possible to move a virtual machine (VM) from one Azure account to another, but it involves a process called "Azure Cross-Subscription Move" or "Azure VM Migration." This process allows you to transfer resources, including virtual machines, from one Azure subscription to another, which can be helpful in scenarios such as organizational restructuring, billing changes, or mergers and acquisitions.
Here's an overview of how you can perform a cross-subscription move for a virtual machine:
Azure Subscription Access: You need access to both the source (current) Azure subscription and the target (destination) Azure subscription.
Resource Group: The VM you want to move should be located within a resource group. You cannot move individual resources between resource groups; you need to move the entire resource group.
Resource Dependencies: Ensure that all resources associated with the VM, such as virtual networks, storage accounts, and network security groups, are within the same resource group or can be moved together.
Steps to Move a Virtual Machine:
Prepare the Source and Target Subscriptions:
Create a Snapshot or Backup (Recommended):
Initiate the Move:
Review and Confirm:
Validation and Testing:
Update DNS and Connectivity:
Please note the following considerations:
Resource Dependencies: Ensure that all resources associated with the VM can be moved together. If any dependencies cannot be moved, you may need to recreate them in the target subscription.
IP Addresses: VMs with public IP addresses may require reconfiguration of DNS records or reassignment of public IPs in the target subscription.
Data Transfer Costs: Be aware of potential data transfer costs associated with moving resources between subscriptions, especially if data needs to be transferred between regions.
Resource Locks: Ensure that there are no resource locks in place that could prevent the move operation.
Resource Limits: Be aware of resource limits and quotas in the target subscription to accommodate the new resources.
Before proceeding with a cross-subscription move, it's recommended to thoroughly plan and understand the implications of the move, especially in production environments, to minimize disruption and ensure a smooth transition.