Skip to content

Latest commit

 

History

History
72 lines (44 loc) · 4.56 KB

File metadata and controls

72 lines (44 loc) · 4.56 KB
title Move Azure VMware Solution subscription to another subscription
description This article describes how to move Azure VMware Solution subscription to another subscription. You might move your resources for various reasons, such as billing.
ms.topic how-to
ms.service azure-vmware
ms.date 03/13/2026
ms.custom
subject-moving-resources
engagement-fy23
sfi-image-nochange

Move Azure VMware Solution subscription to another subscription

This article describes how to move an Azure VMware Solution subscription to another subscription. You might move your subscription for various reasons, like billing.

Prerequisites

You should have at least contributor rights on both source and target subscriptions.

Important

Virtual network and virtual network gateway can't be moved from one subscription to another. Additionally, moving your subscriptions has no effect on the management and workloads, like the vCenter Server, NSX-T Data Center, vSAN, and workload virtual machines.

Prepare and move

  1. In the Azure portal, select the private cloud you want to move.

    :::image type="content" source="media/move-subscriptions/source-subscription-id.png" alt-text="Screenshot that shows the overview details of the selected private cloud."lightbox="media/move-subscriptions/source-subscription-id.png":::

  2. From a command prompt, ping the components and workloads to verify that they're pinging from the same subscription.

    :::image type="content" source="media/move-subscriptions/verify-components-workloads.png" alt-text="Screenshot shows the ping command and the results of the ping.":::

  3. Select the Subscription (change) link.

    :::image type="content" source="media/move-subscriptions/private-cloud-overview-subscription-id.png" alt-text="Screenshot shows the private cloud details."lightbox="media/move-subscriptions/private-cloud-overview-subscription-id.png":::

  4. Provide the subscription details for Target and select Next.

    :::image type="content" source="media/move-subscriptions/move-resources-subscription-target.png" alt-text="Screenshot of the target resource."lightbox="media/move-subscriptions/move-resources-subscription-target.png":::

  5. Confirm the validation of the resources you selected to move. During the validation, you see Pending validation under Validation status.

    :::image type="content" source="media/move-subscriptions/pending-move-resources-subscription-target.png" alt-text="Screenshot shows the resource being moved."lightbox="media/move-subscriptions/pending-move-resources-subscription-target.png":::

  6. Once the validation is successful, select Next to start the migration of your private cloud.

    :::image type="content" source="media/move-subscriptions/move-resources-succeeded.png" alt-text=" Screenshot shows the validation status of Succeeded."lightbox="media/move-subscriptions/move-resources-succeeded.png":::

  7. Select the check box indicating you understand that the tools and scripts associated don't work until you update them to use the new resource IDs. Then select Move.

    :::image type="content" source="media/move-subscriptions/review-move-resources-subscription-target.png" alt-text="Screenshot showing the summary of the selected resource being moved."lightbox="media/move-subscriptions/review-move-resources-subscription-target.png":::

Verify the move

A notification appears once the resource move is complete.

:::image type="content" source="media/move-subscriptions/notification-move-resources-subscription-target.png" alt-text="Screenshot of the notification after the resources move is complete."lightbox="media/move-subscriptions/notification-move-resources-subscription-target.png":::

The new subscription appears in the private cloud Overview.

:::image type="content" source="media/move-subscriptions/moved-subscription-target.png" alt-text="Screenshot showing a new subscription."lightbox="media/move-subscriptions/moved-subscription-target.png":::

Next steps

Learn more about: