Azure-docs: I cannot move the Managed Disk VM across subscription dispite of registering the Microsoft.Compute Resource

[Anmolgan81]

I have tried below command to register:
Register-AzureRmProviderFeature -FeatureName ManagedResourcesMove -ProviderNamespace Microsoft.Compute

I have also checked the status of it and its registere, but I am getting the same error as the managed disks are not supported to move, I have Registered this in all 2 subscription.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 76c1c185-685f-27e0-e634-844b510b1834
• Version Independent ID: 09375778-5354-ab44-c5c6-94c2aebe34bc
• Content: Move Azure resources to new subscription or resource group
• Content Source: articles/azure-resource-manager/resource-group-move-resources.md
• Service: azure-resource-manager
• GitHub Login: @tfitzmac
• Microsoft Alias: tomfitz

[rem8]

Same. Not working yet it appears...

[femsulu]

@Anmolgan81 @rem8 , thanks for bringing this to our attention. As you rightly stated this should now be supported based on the published documentation. checking internally to see if there is a known issue blocking migration of managed VMs. Please stay tuned.

@tfitzmac - are you aware of this?

[tonisc]

Hi!
@femsulu, the same error:
The feature is registered:
"ManagedResourcesMove Microsoft.Compute Registered"
but I can't move a VM. I have tried with a lot of vms, rgs, subscriptions and regions. Always obtains the same error:
"This subscription is not registered to use Microsoft.Compute/ManagedResourcesMove feature."

[tfitzmac]

@singhkays - do you know if the step to register for ManagedResourcesMove feature is working as expected? Several people on this issue thread have reported problems.

[tonisc]

@tfitzmac - in my case, this step works fine and appairs "Registered"
"ManagedResourcesMove Microsoft.Compute Registered"

[Anmolgan81]

@tonisc @tfitzmac In my case I have registered the Resource provider that is "ManagedResourcesMove Microsoft.Compute" I have registered this in both of the subscription, but I still cannot move the managed disks across subscriptions.

[rem8]

@singhkays @tfitzmac Guys, feel free to get in touch with me, you can check my sub if needed, even on Skype call.

[ejschaefer]

@rem8 @tonisc @Anmolgan81 - did you run this after registering the feature?

Register-AzureRmResourceProvider -ProviderNamespace Microsoft.Compute

[tfitzmac]

I just want to reiterate the point that @ejschaefer made. The message from the Azure CLI command provides details that are not returned in the PowerShell command. First, register the feature. Second, wait for status to be set to registered. Third, register the provider. I am adding these steps to the article.

[tonisc]

@tfitzmac @ejschaefer
I made this "Register-AzureRmResourceProvider -ProviderNamespace Microsoft.Compute"
and I wait some minutes until the command "Get-AzureRmProviderFeature -ListAvailable" returns "ManagedResourcesMove Microsoft.Compute Registered"
After, I have trien with powershell and from portal to move a VM to another resource group in the same subscription. And it fails.
What I made wrong? I follow this article.

[Anmolgan81]

@tonisc I have registered the resource, it takes about 20mins to register, when I get the status as registered only then I tried to move the managed disks and it does not support move.

[rem8]

OK guys - now it is working… well, at least. Thanks @ejschaefer for pointing that two registrations are needed: 1 - feature one, which can take about 30 minutes to finish and 2 - resource provider itself which takes a 1 minute to finish.

Now the another case appeared and I think that this has to be added into docs -

The move resources request contains resources like /subscriptions/------------/resourceGroups/-------------/providers/Microsoft.Compute/disks/---------datadisk01 that are being backed up as part of a Azure Backup job. Please check details for these resource ids.

Remember to remove any backup job before moving the Resources. I'll get back to you if everything will go fine! :)

[foskam]

Same here...
registered with
Register-AzureRmProviderFeature -FeatureName ManagedResourcesMove -ProviderNamespace Microsoft.Compute
waited until it was registered. Than I ran
Register-AzureRmResourceProvider -ProviderNamespace Microsoft.Compute
And finally tried the move... same error as before:
This subscription is not registered to use Microsoft.Compute/ManagedResourcesMove feature.
Operation 'move' is not supported on Resource 'xxx' with managed disks.
What now?

[rem8]

Moving resources failed
There was an error moving resources. Unknown error occurred.

DAMN, I was so close :D

EDIT = it was by portal which went weird because lack of connectivity.

After stopping backup, removing all recovery points movement was done correctly. Woohoo!

[tfitzmac]

@tonisc @Anmolgan81 @foskam @rem8 - are you moving to a new resource group or subscription? The registration operations are subscription specific. I haven't tested this myself yet, but I am wondering if you need to run the commands in both subscriptions if you are moving to a new subscription.

[Anmolgan81]

@tfitzmac I have registered the resources in both the subscription but still I cannot move the Managed disk VM's across subscriptions.

[rem8]

@tfitzmac - I'm moving it only between resource groups as for now. It seems to work after I removed all backups from them (which is a bit poor that we cannot then comply with backup policies). I cannot check movement between subs yet :)

@Anmolgan81 - i'm wondering how long have you waited for the movement operations from the time both registry Operations in both subscriptions have shown Registered ? Because I'm thinking that it needs to somehow apply internally longer then it shows Registered through PowerShell... I'd give it even few hours to suit it up.

[Anmolgan81]

@rem8 I just registered the resource and as soon as I got status as Registered, I test the move, are you saying it takes hours to complete?
If yes then can I know how many hours?

[rem8]

@Anmolgan81 Don't have an idea but I registered the second option and it took me about 10 minutes. Are you able to move between RG's in same sub?

[tonisc]

Hi!
today works fine, I needed to register the provider Microsoft.compute even though it's already registered. (This is a new step in this doc).
Thanks a lot for your help!
Toni

[femsulu]

thanks for the update @tonisc .
@rem8 , @Anmolgan81 can you both confirm your managed vm migration is no longer blocked?

[femsulu]

@tfitzmac do we need to update or create a new how-to doc to ensure no one else misses the extra step to re-register the MS.Compute provider?

[tfitzmac]

@femsulu - that step was added based on comments in this issue, so some of the above comments came before the step was documented. However, I am going reformat with numbered steps to make sure it is clear that each step is needed.

[femsulu]

Closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.

[dyesuron]

Still not working to move managed disks to another subscription. Followed the guide step by step but Azure portal is still showing the same message.

[erwinwildenburg]

For anyone having this problem, I initially had the same problem.

I initially activated using the instructions on the destination subscription.
This resulted in the same error messages most have.

After that I applied the instructions on the source subscription.
This resulted in messages about Azure Backup, but this error message disappeared. I haven't disabled (and removed all restore points) yet. I will do that at a move convenient time.

Anyway, the original error message disappeared, and I assume it will succeed after that.
I'm not sure if this feature has to be enabled on only the source subscription or the source and destination subscription.

[gacurtin]

Has anyone had success with moving a managed image? I have registered with the namespaces as shown above. Still getting this error:

{"code":"ResourceMoveProviderValidationFailed","message":"Resource move validation failed. Please see details. Diagnostic information: timestamp '20181026T152013Z', subscription id 'c510ccb2-1976-47f0-a901-7a2528b1cb23', tracking id '94d90948-71d0-4f7b-b4f1-7c05f442e231', request correlation id '2c3d1217-d287-42e6-a4ed-70ff4f98c30c'.","details":[{"target":"Microsoft.Compute/images","message":"{"error":{"code":"BadRequest","message":"This subscription is not registered to use Microsoft.Compute/ManagedResourcesMove feature. Browse the link https://aka.ms/movemdsignup for resource move information."}}"}]}

[singhkays]

@gacurtin Have you registered the Compute RP as well? Also have you registered both source & destination sub?

[gacurtin]

I have. Just verified as well

Get Outlook for Androidhttps://aka.ms/ghei36

---

From: Kay Singh [e-mail]
Sent: Friday, October 26, 2018 12:34:54 PM
To: MicrosoftDocs/azure-docs
Cc: Garrett Curtin; Mention
Subject: Re: [MicrosoftDocs/azure-docs] I cannot move the Managed Disk VM across subscription dispite of registering the Microsoft.Compute Resource (#15588)

@gacurtinhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgacurtin&data=02%7C01%7CGarrett.Curtin%40microsoft.com%7C3d5397cdb62d4286c8fe08d63b69579d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636761720964418468&sdata=Rh8d%2BMhgTlBm4e9knSfj5Dg35PdO2G%2FVAtq3CfH2da8%3D&reserved=0 Have you registered the Compute RP as well? Also have you registered both source & destination sub?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F15588%23issuecomment-433485861&data=02%7C01%7CGarrett.Curtin%40microsoft.com%7C3d5397cdb62d4286c8fe08d63b69579d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636761720964428473&sdata=EaJB6BZQ%2BVgcypF6isQrUaGWtcGeGZMW%2BJfMqFj69Z8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAnuIFe44PSLC-4BziWPEa44KmsZkBc_7ks5uo0e-gaJpZM4W4rNH&data=02%7C01%7CGarrett.Curtin%40microsoft.com%7C3d5397cdb62d4286c8fe08d63b69579d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636761720964428473&sdata=cwWP%2FNk70%2F%2BBT5GglExbmaSYNx0Yt58Qsn1rkrm4C%2FE%3D&reserved=0.

[singhkays]

@gacurtin Weird, those are the steps that you need to do and it's worked for many other folks. Btw, we're removing the sign up requirement in a few weeks as well. In the meantime, to confirm you've done these steps in order ?

1. registered for the feature
2. then registered for the Microsoft.Compute RP again
3. Wait 30 mins or so to confirm the feature status is showing registered
4. Tried to move

[gacurtin]

@singhkays, I re-registered and now it works. I must have missed a step when I originally registered the namespace. I also registered microsoft.batch. Not sure if this helped. Thank you for your help.

[singhkays]

@gacurtin Awesome! glad to hear it worked

[nicomlas]

The 0-step is : be sure the active sub is the target one before executing tuto commands.

After registering feature, you SHOULD see the target sub id in the feature :

az feature show --namespace Microsoft.Compute --name ManagedResourcesMove
{ "id": "/subscriptions/<target sub id>/providers/Microsoft.Features/providers/Microsoft.Compute/features/ManagedResourcesMove", "name": "Microsoft.Compute/ManagedResourcesMove", "properties": { "state": "Registered" }, "type": "Microsoft.Features/providers/features" }

And... One day lost :(