Forum Discussion

Ryan Clark's avatar
Ryan Clark
Copper Contributor
Nov 14, 2017

Error when moving resources

I am trying to move some resources (couple of VMs, virtual network, storage accounts) from one subscription to another. I am seeing this error. It is raised with support, but so far they have not been able to tell me what resources are causing the problem. The message does not identify them. As far as I know, none of our resources have been upgraded from Classic and there are no affinity groups in the Classic portal. It looks like at least one other person has seen this error (In the comments https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-move-resources)

Does anyone know how I might be able to identify the problem resources?

 

MoveCannotProceedBecauseOfResourcesInServiceManagementStackThe move request contains resources that were migrated from the Service Management stack. When the resources existed in the Service Management stack, they were associated with an affinity group that is still in use. Such moves are not supported

5 Replies

  • Could you be more specific as to what and how you are trying to move resources?

    • Ryan Clark's avatar
      Ryan Clark
      Copper Contributor

      Initially I was trying through the portal. The successful move was with PowerShell. All resources were ARM, classic resources cannot be moved from subscription to subscription 

      • Kent Gaardmand's avatar
        Kent Gaardmand
        Iron Contributor
        They can, but require going through support and its all resources to a sub with no ASM resources allready present. Well glad it worked for you, i was wondering if perhaps the resource group once housed ASM resources and had lingering data.

        kind regads
    • Ryan Clark's avatar
      Ryan Clark
      Copper Contributor

      Ticket was already in progress, but Azure support could not identify the problem. Someone else on another thread I was following (see comments in the link I referenced earlier) said there was a bug that has now been fixed. I have moved my resources.

Resources