App Service, App Service plan, DB (Paas) Location and subscription migration

Question

Azure Resources:

• App Service
• App Service Plan
• App Insights
• Availability test
• Database (PaaS)

Existing :
Subscription : A
Location - North Europe

Target :

• Subscription : B
• Location - West Europe

When you want to move Web app, DB and Web app Plan from North Europe to West europe.

Following are the options:

• ARM Template
• Backup and Restore
• Terraform
• Data migration
• Subscription migration. (Movement)

Among these options, please advice the suitable option for the Location subscription migration.

Thank you

Answer 1

Since the majority resources are related to Azure App Service (DB is dependent resource).
App Service resources are region-specific and can't be moved across regions.
You must create a copy of your existing App Service resources in the target region, then move your content over to the new app.
If your source app uses a custom domain, you can migrate it to the new app in the target region when you're finished.

I would suggest you to refer the document -Move guidance for App Service resources - This article describes the steps to move App Service resources.

There are specific requirements for moving App Service resources to a new subscription.

This article shows you how to move Azure resources to either another Azure subscription or another resource group under the same subscription.
So, regardless of the migration method (Azure portal, Azure PowerShell, Azure CLI, or the REST API), firstly you need to review the prerequisite/validation the move support.

Some services have specific limitations or requirements when moving resources.

To make copying your app easier, you can clone an individual App Service app into an App Service plan in another region, but it does have limitations, especially that it doesn't support Linux apps.

I would suggest you to validate - Resources - Validate Move Resources

The validate move operation lets you test your move scenario without actually moving the resources. Use this operation to check if the move will succeed. Validation is automatically called when you send a move request. Use this operation only when you need to predetermine the results.

You can validate and try to move the resources via Azure Portal (“Move to another subscription”).

Note:

• Kindly note that moving a resource only moves it to a new resource group or subscription. It doesn't change the location of the resource.
• A database and server must be in the same resource group. When you move a SQL server, all its databases are also moved. This behavior applies to Azure SQL Database and Azure Synapse Analytics databases.
• Currently, not all resources in Azure support move. For a list of resources that support move, see Move operation support for resources.

Apologize for the long post, If you have further questions or needs clarification kindly send an email with subject line “Attn:Ajay” to AzCommunity[at]Microsoft[dot]com referencing this thread and Azure subscription ID, I will follow-up with you.