Managed cloud

Azure cross-tenant migration: the checklist we used for 25+ live apps

Moving servers, storage and domains to a subscription in a different Azure tenant, in the order that keeps customers from noticing.

By the Orbit Core engineering team · Published · 5 min read

We moved about 25 customer apps (websites, mobile-app backends and admin panels) from one Azure subscription to a new subscription in a different tenant. The old subscription ran on credits that were about to end, at which point Azure would have disabled it and taken every site offline. Nothing was lost, and 29,687 files (about 2 TB) were copied and verified. This is the order we worked in.

1. Inventory before you touch anything

  • Every VM, disk, database, storage account, public IP and DNS record.
  • Every hostname that resolves to the old environment. We had more than 50.
  • Every place an app stores a URL or a connection string: config files, environment variables and database rows.

The third item is the one teams skip. Our apps held about 9,600 file links signed for the old storage accounts. A straight copy would have left broken images and documents everywhere.

2. Build the destination first

  • Create the new subscription, resource groups and network in the target tenant.
  • Recreate storage accounts with identical settings: redundancy, access tier, container names and access levels. We recreated six.
  • Set up access, backups and monitoring before any data arrives.

3. Move servers by snapshot

  • Snapshot the server disks in the source subscription.
  • Copy the snapshots across tenants and create disks from them.
  • Rebuild the VM around those disks and confirm services start cleanly.

4. Copy storage, then verify it

  • Copy every container into its counterpart in the new accounts.
  • Compare file counts and sizes on both sides. A copy you have not verified is a hope.
  • Run a final incremental copy close to the switch to pick up new uploads.

5. Fix stored links and configuration

  • Re-sign stored file links for the new storage accounts and update them in place.
  • Repoint each app's configuration to the new storage and database endpoints.
  • Open each app on the new server through a hosts-file override and click through the pages that show files.

6. Switch DNS deliberately

  • Lower TTLs several days ahead so the change spreads in minutes.
  • Test every hostname before the switch and record the result.
  • Change the records, then test every hostname again against the same list.
  • Reissue or confirm SSL certificates for each domain.

7. Keep the old side until you are sure

Leave the source environment stopped but intact for as long as the subscription allows. Raise TTLs back once things are stable, and write down what moved where.

What we would tell another team

The copy is the easy part. The work is in the inventory and in the stored links. Budget most of your time there, and test by hostname rather than by server. The numbers and the outcome are in the full case study.

Frequently asked questions

Can you move an Azure subscription to another tenant?

Some subscription types can be transferred between directories, but credit-based and sponsored subscriptions often cannot. In that case you rebuild in a new subscription and copy the data across.

What breaks most often in a cross-tenant Azure migration?

Stored URLs. Applications often save signed links to the old storage account in their databases, and those stop working after a plain copy.

How do you avoid downtime when switching domains?

Lower DNS TTLs several days ahead, test every hostname against the new server before the switch, then change the records and test again.

Does Orbit Core resell Azure?

No. We run your own Azure, AWS or Google Cloud account. You pay the provider directly.

Sources

Planning a migration?

Talk it through with the engineers who ran this one.