Share via

Moving SQL Database to another subscription failed and is not longer available in either subscription

jason mirosh 0 Reputation points
2026-03-20T05:46:26.5566667+00:00

There was an error moving resources. All move in provider succeeded. However, the batch move job failed. The correlation id is 'aa065546-2a95-434b-a2ce-5f5f0591f169'. (Code: ResourceMoveFailed) ResourceProviderLinkedNotificationJob for resourceid 'Microsoft.Network/virtualNetworks/VBA_VNET-westus3-0' to endpoint 'https://uksouth.rsrp.storage.azure.com' did not finish successfully within given period. (Code: NotificationAfterMoveFailed, Target: Microsoft.Storage/) ResourceProviderLinkedNotificationJob for resourceid 'Microsoft.Network/virtualNetworks/VBA_VNET-canadacentral-0' to endpoint 'https://uksouth.rsrp.storage.azure.com' did not finish successfully within given period. (Code: NotificationAfterMoveFailed, Target: Microsoft.Storage/)

Azure SQL Database

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Manoj Kumar Boyini 12,090 Reputation points Microsoft External Staff Moderator
    2026-03-20T06:25:32.79+00:00

    Hi jason mirosh

    The issue occurred due to an inconsistent ARM resource state after the failed subscription move operation, which caused the SQL Database resource to become unavailable in both the source and target subscriptions.

    An ARM refresh / synchronization has been performed from our end to resolve the resource visibility issue.

    Please check the Azure Portal now and confirm whether the SQL Database is visible and manageable.

    0 comments

Your answer

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