How to move Azure resources that don’t support migration between subscriptions while minimizing downtime?

Question

I’m working with Azure resources that cannot be migrated directly between subscriptions in the same tenant. For these resources:

1. Can I recreate them manually in the target subscription?
2. If manual creation is the only option, how can I identify and map all dependencies at various levels (e.g., CI/CD pipelines, application-level configurations, resource interconnections)?
3. What best practices can I follow to minimize downtime and ensure a seamless transition for a production-grade, enterprise-level application?
4. Are there any tools or scripts available to help automate parts of this process or assist with planning the migration effectively?
5. Any Plan to achieve it

Please help me to understand; I’d really appreciate your support!

Answer 1

Hi @Muhammad Zubair,

Welcome to Microsoft Q&A Forum, thank you for posting your query here!

Azure Resource Mover is a service in Azure designed to help you move resources between Azure regions with minimal downtime from one subscription to another subscrption. It supports moving a wide variety of Azure resources, including virtual machines, storage accounts, virtual networks, and more. The tool helps you plan, validate, and initiate the movement of these resources across regions within the same Azure subscription, or between subscriptions, while preserving their configurations and dependencies.

Here’s a general overview of its features:

• Migration Planning: Azure Resource Mover can assess your resources to ensure they are eligible for movement to the target region.
• Move Validation: It checks for any dependencies or issues that might prevent the successful migration.
• Resource Movement: Once validated, you can initiate the migration, and the tool will automate the movement of the resources while preserving their configurations.
• Minimal Downtime: While resources are moved, downtime is minimized as the tool ensures that the resources remain operational as much as possible.
• Cross-Region and Cross-Subscription: You can move resources within the same subscription or to a different subscription in a different region.

It’s useful for scenarios like disaster recovery, optimizing regional costs, or improving performance by relocating resources closer to users.

Refer: https://learn.microsoft.com/en-us/azure/resource-mover/overview

let us know if you have any further queries. I’m happy to assist you further.  

Please provide your valuable comments

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.