Share via

Azure Migrate Test Failover: Can it be done in a different subscription than the Target

Mahavir Saroj 271 Reputation points
2026-05-16T10:17:50.4466667+00:00

Hi Team,

I would like to seek clarification on the recommended approach for Azure Migrate test failover, specifically regarding subscription usage and environment separation.

As per my understanding:

  • When replication is enabled in Azure Migrate, a target subscription is selected and associated with the replication configuration.
  • Both test failover and actual failover (migration) are performed within this same target subscription.
  • There is no option to select a different subscription solely for test failover once replication is configured.

However, in our scenario:

  • The application is planned to be migrated to a Production subscription.
  • The customer does not allow any testing (including test failover) in the Production subscription, even with isolation (separate VNet/subnet).
  • They require test validation activities be carried out exclusively in a sandbox subscription regardless of the environment.

Given this constraint, the approach we are considering is:

  1. Configure replication to a Sandbox subscription and perform test failover and validation there.
  2. Then configure replication again to the Production subscription for the final migration.

This effectively means replication needs to be configured twice for the same machine, once per target subscription.

I would appreciate any guidance or best practices from the community or Microsoft experts on how to handle this scenario efficiently.

Thank you.

Azure Migrate
Azure Migrate

A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.

0 comments

Answer accepted by question author

Marcin Policht 90,725 Reputation points MVP Volunteer Moderator
2026-05-16T11:06:43.7566667+00:00

Yep, AFAIK, your understanding is correct. Once replication is configured, the target subscription and region are locked for both test and final failovers. Considering that you cannot perform a test failover in one subscription and the final cutover in another, your proposed workaround (configuring replication twice) should work in order to maintain strict environment separation.

You do not necessarily have to push all the data twice over your network. You can avoid lengthy initial re-replication by leveraging your existing replication appliance or Recovery Services Vault configuration if orchestrated properly.

Make sure you run Clean up test migration after validating in the Sandbox subscription to delete the test VMs and temporary resources. Depending on your environment, you may also replicate the VMs directly to the sandbox, perform final migration, and then utilize the native Azure resource-move capabilities to move the production-ready VM to the Production subscription after it is running in Azure.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

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.