Azure Move Error

Jain Navin Kumar 46 Reputation points
2022-06-27T05:34:59.177+00:00

Hello

When we attempted Move of Azure Resources from one subscription to another we encountred this error message but when verefied we were able to see all resources under the New Subscription.
What is this error and why has this been reported.

There was an error moving resources. All move in provider succeeded. However, the batch move job failed. The correlation id is '7947f890-ccd2-46e4-8952-ca91c1a29300'. (Code: ResourceMoveFailed) ResourceProviderLinkedNotificationJob for resourceid 'Microsoft.Network/virtualNetworks/Temp-vnet' to endpoint 'https://westcentralus.rsrp.storage.azure.com' did not finish successfully within given period. (Code: NotificationAfterMoveFailed, Target: Microsoft.Storage/) ResourceProviderLinkedNotificationJob for resourceid 'Microsoft.Network/virtualNetworks/Temp-vnet' to endpoint 'https://eastus2euap.rsrp.storage.azure.com' did not finish successfully within given period. (Code: NotificationAfterMoveFailed, Target: Microsoft.Storage/) ResourceProviderLinkedNotificationJob for resourceid 'Microsoft.Network/virtualNetworks/Temp-vnet' to endpoint 'https://centraluseuap.rsrp.storage.azure.com' did not finish successfully within given period. (Code: NotificationAfterMoveFailed, Target: Microsoft.Storage/) ResourceProviderLinkedNotificationJob for resourceid 'Microsoft.Network/virtualNetworks/Temp-vnet' to endpoint 'https://eastus2.stage.rsrp.storage.azure.com' did not finish successfully within given period. (Code: NotificationAfterMoveFailed, Target: Microsoft.Storage/)
Related events

Azure Resource Mover
Azure Resource Mover
An Azure service used for moving multiple resources between Azure regions.
287 questions
{count} vote

2 answers

Sort by: Most helpful
  1. Monalla-MSFT 13,071 Reputation points Moderator
    2022-07-01T14:00:00.683+00:00

    Hello @Jain Navin Kumar - Welcome to Microsoft Q&A and thanks for reaching out.

    Depending on the type of resources you moved, you could indeed have side effects.

    You might have missed some components that are hidden - you can unhide by clicking this box in the portal or by querying Azure Graph.

    216975-image.png

    Also, Microsoft deploys additional components in their backbone that you do not have control on (like network related policies for example). The migration can fail in the back while depicting a false success on your end. You should refer to move operations - supported services first, and most probably raise a case to check that everything went fine if all services you moved are supposed to be supported.

    Hope this helps. and please feel free to reach out if you have any further questions.

    ------------------------------------------------------------------

    If the above response was helpful, please feel free to "Accept as Answer" and "Upvote" the same so it can be beneficial to the community.

    0 comments No comments

  2. Andrii 0 Reputation points
    2023-03-06T17:59:31.8766667+00:00

    Got similar error:

    There was an error moving resources. All move in provider succeeded. However, the batch move job failed. The correlation id is '6183a0e1-646d-4d2b-b0a7-80d14259ccca'. (Code: ResourceMoveFailed) ResourceProviderLinkedNotificationJob for resourceid 'Microsoft.Storage/storageAccounts/stmove343' to endpoint 'https://eastus2.cert.api.azureml.ms/registrymanagement/v1.0/' did not finish successfully within given period. (Code: NotificationAfterMoveFailed, Target: Microsoft.MachineLearningServices/registries)

    Steps to reproduce:

    1. Create a resource group in East US2
    2. Create Azure Storage in East US2
    3. Create a blob container
    4. Upload an empty text file

    Note: there are no hidden files in the resource group before we move

    1. Move to a different subscription in the same region (East US 2)

    Expected:
    Operation is successful since Microsoft.Storage.storageaccounts supports subscription move.

    Actual:

    The error message posted above. However, files seems to be moved.

    I've tried it with US East and couple of other combinations - it fails with the same error.

    Second question I have, is there a guide on how to move Storage between two different subscriptions within the same tenant? What are the implications/downtime? I found only one to move to a different region - https://learn.microsoft.com/en-us/azure/storage/common/storage-account-move?tabs=azure-portal


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.