Move a Service Fabric Mesh application to another Azure region


The preview of Azure Service Fabric Mesh has been retired. New deployments will no longer be permitted through the Service Fabric Mesh API. Support for existing deployments will continue through April 28, 2021.

For details, see Azure Service Fabric Mesh Preview Retirement.

This article describes how to move your Service Fabric Mesh application and its resources to a different Azure region. You might move your resources to another region for a number of reasons. For example, in response to outages, to gain features or services available in specific regions only, to meet internal policy and governance requirements, or in response to capacity planning requirements.

Service Fabric Mesh does not support the ability to directly move resources across Azure regions. However, you can move resources indirectly by deploying a copy of your current Azure Resource Manager template to the new target region and then redirecting ingress traffic and dependencies to the newly created Service Fabric Mesh application.


  • Ingress controller (such as Application Gateway) to serve as an intermediary for routing traffic between clients and your Service Fabric Mesh application
  • Service Fabric Mesh (Preview) availability in the target Azure region (westus, eastus, or westeurope)


  1. Take a "snapshot" of the current state of your Service Fabric Mesh application by exporting the Azure Resource Manager template and parameters from the most recent deployment. To do this, follow the steps in Export template after deployment using the Azure portal. You can also use Azure CLI, Azure PowerShell, or REST API.

  2. If applicable, export other resources in the same resource group for redeployment in the target region.

  3. Review (and edit, if needed) the exported template to ensure the existing property values are the ones you want to use in the target region. The new location (Azure region) is a parameter that you will supply during redeployment.


  1. Create a new resource group (or use an existing one) in the target region.

  2. With your exported template, follow the steps in Deploy resources from custom template using the Azure portal. You can also use Azure CLI, Azure PowerShell, or REST API.

  3. For guidance on moving related resources such as Azure Storage accounts, refer to guidance for individual services listed under the topic Moving Azure resources across regions.


  1. When the deployment is complete, test the application endpoint(s) to verify the functionality of your application.

  2. You can also verify the status of your application by checking the application status (az mesh app show) and reviewing the application logs and (az mesh code-package-log) commands using the Azure Service Fabric Mesh CLI.


Once you've confirmed equivalent functionality of your Service Fabric Mesh application in the target region, configure your ingress controller (for example, Application Gateway) to redirect traffic to the new application.

Clean up source resources

To complete the move of the Service Fabric Mesh application, delete the source application and/or parent resource group.

Next steps