Introduction
Managing Azure Storage Accounts often involves scenarios where you need to move them between regions, resource groups, subscriptions, or tenants. While Azure provides robust tools for resource management, moving a Storage Account is not always straightforward and depends on the specific scenario. In this article, we’ll break down the key scenarios, solutions, and common issues to help you move your Storage Account effectively.
Key Scenarios for Moving Azure Storage Accounts
There are four common requests for moving a Storage Account:
- To a different region
- To a different resource group
- To a different subscription
- To a different tenant
These scenarios can be divided into two categories based on the feasibility of the move:
Scenario 1: Moving Is Not Directly Supported
In some cases, moving a Storage Account is not directly possible, and you’ll need to create a new Storage Account and transfer the data manually.
- Requests in this category:
- Moving to a different region
- Moving to a different tenant
Solution:
- Create a new Storage Account in the desired location or tenant.
- Transfer the data from the source Storage Account to the destination Storage Account.
- Access to the source Storage Account remains available during the transfer, so downtime should not be an issue.
Reference:
Scenario 2: Moving Is Supported Using Azure Resource Manager
For some requests, Azure Resource Manager (ARM) supports moving resources automatically with minimal manual intervention.
- Requests in this category:
- Moving to a different resource group
- Moving to a different subscription
Solution:
- Use Azure Portal, PowerShell, or CLI to move the Storage Account.
- During the move, a lock is placed on both the source and destination resource groups for Write and Delete operations. However, applications can still interact with the data.
Steps to Move Using Azure Portal:
- Navigate to the Overview tab of your Storage Account.
- Select the Move option.
- Choose the appropriate move type (e.g., “Move to another resource group”).

- Select the target resource group or subscription.
- Allow the automatic validation process to complete.
- Approve and execute the move.

- Refresh the browser tab to confirm the move is successful.
Reference:
- Move resources to a new subscription or resource group – Azure Resource Manager | Microsoft Learn
- Move operation support by resource type – Azure Resource Manager | Microsoft Learn
Common Issues and Solutions
Issue 1: Private Endpoint Preventing Move
Problem:
The move fails with the following error:
{
"message": "Resource move validation failed. Diagnostic information: ... Move resources with storage accounts containing private endpoint is not supported."
}
Solution:
Disable the private endpoint associated with the Storage Account before initiating the move.
Reference:
Issue 2: Notification Job Failure After Move
Problem:
The move completes, but you receive an error indicating that the notification job failed:
{
"message": "ResourceProviderLinkedNotificationJob did not finish successfully within the given period."
}
Solution:
This issue occurs when the notification job times out after the move is completed. From the customer’s perspective, the data is successfully migrated, and no further action is required. However, you can validate the data migration to ensure everything is in place.
Best Practices for Moving Azure Storage Accounts
- Plan Ahead:
- Understand the limitations and requirements of your specific scenario.
- Check for dependencies like private endpoints or linked resources.
- Minimize Downtime:
- Leverage parallel data transfers or ARM tools to reduce impact on applications.
- Validate After the Move:
- Confirm that all data and configurations are properly migrated.
- Refresh the Azure Portal to ensure the move is reflected accurately.
Conclusion
Moving Azure Storage Accounts can be a straightforward process or require manual intervention, depending on the scenario. By understanding the supported operations and potential issues, you can ensure a smooth migration. For more information, refer to Microsoft’s official documentation or consult Azure support for complex cases.