Published
Mar 13 2019 06:12 PM
13.7K
Views
First published on MSDN on Jul 05, 2016
This post is about what we DO NOT want you to do and how to do it right.
if you want to move Azure SQL server from one subscription to another do not delete it assuming you will be able to create the server in the other subscription.
this will not work for you ( read why here )
Instead, go to the server blade in the portal and click on Move
you will see all the subscriptions that you are administering
if you cannot see the destination subscription ID in the list, make sure you are added as administrator (co-administrator) on that subscription.
if your Microsoft account is set to as administrator and you still cannot see the subscription them much probably you have different account types (Work/School and personal)
in this case please open a support case to get assistance by our team.
Server Migration Blockers:
note that you will not be able to move the server if some dependency will be broken
for instance in case you have either:
in that case migration validation will stop you and you will have to remove the dependent object before move can be done.
This post is about what we DO NOT want you to do and how to do it right.
if you want to move Azure SQL server from one subscription to another do not delete it assuming you will be able to create the server in the other subscription.
this will not work for you ( read why here )
Instead, go to the server blade in the portal and click on Move
you will see all the subscriptions that you are administering
if you cannot see the destination subscription ID in the list, make sure you are added as administrator (co-administrator) on that subscription.
if your Microsoft account is set to as administrator and you still cannot see the subscription them much probably you have different account types (Work/School and personal)
in this case please open a support case to get assistance by our team.
Server Migration Blockers:
note that you will not be able to move the server if some dependency will be broken
for instance in case you have either:
- Alert rule set on database metrics
- Long Term Retention Backup
in that case migration validation will stop you and you will have to remove the dependent object before move can be done.