question

Expecho avatar image
1 Vote"
Expecho asked RaydelPiero-9873 edited

Moving an Azure Sql Server to another subscription in another tenant

We are planning to move a sql server containing a elastic pool with 8 databases to another subsciption in another tenant. So far we have come up with these steps:

  1. Create a new subscription (TMP) in the source tenant

  2. Move the server to this new subscription (TMP)

  3. Transfer ownership of the new subscription to the destination tenant

  4. Move the server to the final destination subscription

  5. Remove the now obsolete subscription (TMP) from the destination tenant


My questions are:

  • Is this a good approach and are there any thing we need to be aware of? I suppose we need to correct the Azure Active Directory admin after the movement has completed but that is all I can think of.

  • One of the databases does have geo replication enabled, is that something we need to address or not?

  • What are the risks involved, will there be any downtime? What happens if there is a failure in one of the steps?


azure-sql-database
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I tried that today and it worked just fine. The steps were:

  1. Create a new subscription Pay-as-you-go (temporal) in the source tenant (owner role of the new suscription granted)

  2. Move the server and other resources to this new subscription PAYG (temporal)

  3. Change the directory of the new subscription PAYG (temporal) to the destination tenant. Select the suscription and there will be the option to Change the directory

  4. In the destination tenant change your role to own the moved suscription

  5. Move the server to the final destination subscription

  6. Remove the now obsolete subscription (TMP) from the destination tenant


0 Votes 0 ·
KalyanChanumolu-MSFT avatar image
1 Vote"
KalyanChanumolu-MSFT answered KalyanChanumolu-MSFT commented

@Expecho Thank you for reaching out.

For moving elastic pools, you can use Azure Resource Mover. It can help you in validating the dependencies and guide you through the process.

123062-image.png

We have a tutorial published here to walk you through the process. Though the tutorial talks about resource movement between regions, the process is similar for moving resources across subscriptions as well.

You may experience a minor downtime during the commit phase when the database switches to the new host.
It is recommended that you try this with a non-production database first to estimate the time required for the move and plan your production move accordingly.


If an answer is helpful, please "Accept answer" or "Up-Vote" which might help other community members reading this thread.
And if you have further questions or issues, please let us know.


image.png (91.6 KiB)
· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@KalyanChanumolu-MSFT thanks for your answer and the guidance! So that covers the whole movement to the other subscription. How about the move to the new tenant, do you forsee any issues there giving our plan?

0 Votes 0 ·

@Expecho Any particular reason you are moving the database twice?
First to a TMP subscription and then to the destination?

Please check the guidance here

0 Votes 0 ·
Expecho avatar image Expecho KalyanChanumolu-MSFT ·

Hi, that is because there are a lot of other resources in that subscription that should not be moved to the new tenant.

0 Votes 0 ·
Show more comments
SaeInChoi-8023 avatar image
0 Votes"
SaeInChoi-8023 answered

It means Azure SQL MI data migration between tenant is supported by Azure Resource Mover?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PrashanthKasamsetty-1365 avatar image
0 Votes"
PrashanthKasamsetty-1365 answered

Resource mover will move the resources to same tenant but not between 2 different tenants. Can someone update if there is any approach that exists to move the dbs between 2 tenants?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.