Moving Azure Resources Across Regions

• Customers may need to move deployed Azure resources across regions for reasons such as data residency requirements and latency reduction.
• Various tools help customers with these moves, but Azure Resource Mover, in preview, aims to unify and simplify the task.
• A small subset of Azure resource types is initially supported by Azure Resource Mover, and many aspects of a regional move will still require manual steps or custom scripting.

Moving deployed Azure resources across regions can be a difficult task because of dependencies and differences between the source and target environments. However, there are several reasons customers may need to perform such moves. The Azure Resource Mover tool, in preview as of Sept. 2020, can reduce some of the complexity.

Why Move Resources Across Regions?

Azure deployments consist of provisioned resources such as VMs, databases, and Web Apps. The resources are deployed logically within a hierarchy of accounts, subscriptions, and resource groups and physically to Azure geographic regions around the world. A resource’s logical and physical (region) locations are determined when it is provisioned.