not able to move VM created from custom image getting error LinkedAuthorizationFailed: The current tenant is not authorized to access linked subscription

PTechie 0 Reputation points
2025-07-03T05:22:26.6933333+00:00

I'm trying to move a VM (vm-image) from one tenant (CSP subscription) to another tenant by first adding a PAYG subscription, changing its directory, and then using Azure Resource Move. But I'm getting the following error

{"message":"Resource move policy validation failed. Please see details. Diagnostic information:  subscription id '15xxxxx', request correlation id 'bxxxx'. (Code: ResourceMovePolicyValidationFailed) The client has permission to perform action 'Microsoft.Compute/images/read' on scope '/subscriptions/21xxxxx/resourcegroups/Prod-RG/providers/Microsoft.Compute/virtualMachines/vm-Image', however the current tenant 'bxxxxx' is not authorized to access linked subscription 'dxxxxxxxxxxx'. (Code: LinkedAuthorizationFailed, Target: Microsoft.Compute/Microsoft.Compute/virtualMachines/vm-image)","code":"ResourceMovePolicyValidationFailed","name":"BatchResponseItemError","stack":"BatchResponseItemError: Resource move policy validation failed. Please see details. Diagnostic information:  subscription id '15xxxxxx', request correlation id 'bxxx'.\n    at t (https://portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:41:815)\n    at new t (https://portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:61:11960)\n    at https://portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:61:4965\n    at Array.forEach (<anonymous>)\n    at https://portal.azure.com/Content/Dynamic/MYbNINXhLuLV.js:61:3220","status":409}
Azure Resource Mover
Azure Resource Mover
An Azure service used for moving multiple resources between Azure regions.
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Deepanshu katara 17,330 Reputation points MVP Moderator
    2025-07-03T06:11:59.4966667+00:00

    Hello ,

    I think You're trying to move or access a resource (like a VM image) across subscriptions or tenants, but:

    • The source subscription (21xxxxx) is under Tenant A (bxxxxx),
    • The target subscription (15xxxxx) is under Tenant B,
    • Your current user has permissions on the resource, but not across both tenants,
    • Azure blocks the operation due to Linked Authorization Failure.

    How to Fix It

    1. Confirm Tenant and Subscription Ownership
    • Go to the Azure Portal and check:
      • Which Azure Active Directory (tenant) each subscription belongs to.
        • You can do this under Subscriptions > [Your Subscription] > Properties.
    1. Ensure Both Subscriptions Are in the Same Tenant

    Azure does not allow resource moves across tenants. You have two options:

    Option A: Move the Subscription to the Same Tenant

    If you control both subscriptions:

    • Go to Azure Portal > Subscriptions > Transfer billing ownership.
    • Or contact Microsoft Support to move the subscription to the same tenant.

    Option B: Recreate the Resource in the Target Tenant

    If you can’t move the subscription:

    • Export the VM image (or resource),
    • Recreate it in the target tenant/subscription manually.
    1. Grant Proper Permissions

    If the subscriptions are in the same tenant:

    • Ensure your user has Contributor or Owner role on both subscriptions.
    • Also check Azure Resource Move policies under:
      • Azure Policy > Assignments — look for any policies blocking resource moves.

    Pls check and let us know if any further ques

    Kindly accept

    Thanks

    Deepanshu


  2. Naveena Patlolla 4,960 Reputation points Microsoft External Staff Moderator
    2025-07-10T01:01:22.6+00:00

    Hi PTechie

    The error occurs because your VM in Tenant B's PAYG subscription (15xxxxx) still has dependencies on resources in Tenant A's original CSP subscription (dxxxx), specifically the custom managed image used to create the VM.

    In the same subscription it will work Resource move successfully, but you are preforming in different tenants so please find the solutions below.

    Solution 1: Export all VM disks to VHD format in PAYG subscription (15xxxxx)

    Use AzCopy to transfer VHDs to storage in target CSP subscription (21xxxxx)

    Create new managed disks from the VHDs

    Build new VM using these disks

    Solution 2: Use Azure migrate to Migrate server from 1 Subscription to another subscription which are in different tenants.

    https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines?view=migrate-classic

    let us know if you have any further queries. I’m happy to assist you further.

    Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.