Skip to content

Commit a9e6da2

Browse files
committed
Fixup links
1 parent 6bf0843 commit a9e6da2

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/service-fabric-mesh/service-fabric-mesh-move-across-regions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,16 +12,16 @@ ms.custom: subject-moving-resources
1212

1313
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.
1414

15-
[Service Fabric Mesh does not support](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/region-move-support#microsoftservicefabricmesh) 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 (ARM) template to the new target region and then redirecting ingress traffic and dependencies to the newly created Service Fabric Mesh application.
15+
[Service Fabric Mesh does not support](../azure-resource-manager/management/region-move-support.md#microsoftservicefabricmesh) 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 (ARM) template to the new target region and then redirecting ingress traffic and dependencies to the newly created Service Fabric Mesh application.
1616

1717
## Prerequisites
1818

19-
* Ingress controller (such as [Application Gateway](https://docs.microsoft.com/en-us/azure/application-gateway/)) to serve as an intermediary for routing traffic between clients and your Service Fabric Mesh application
19+
* Ingress controller (such as [Application Gateway](../application-gateway.md)) to serve as an intermediary for routing traffic between clients and your Service Fabric Mesh application
2020
* Service Fabric Mesh (Preview) availability in the target Azure region (`westus`, `eastus`, or `westeurope`)
2121

2222
## Prepare
2323

24-
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](https://docs.microsoft.com/azure/azure-resource-manager/templates/export-template-portal#export-template-after-deployment) using the Azure portal. You can also use [Azure CLI](../management/manage-resource-groups-cli.md#export-resource-groups-to-templates), [Azure PowerShell](../management/manage-resource-groups-powershell.md#export-resource-groups-to-templates), or [REST API](/rest/api/resources/resourcegroups/exporttemplate).
24+
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](../azure-resource-manager/templates/export-template-portal.md#export-template-after-deployment) using the Azure portal. You can also use [Azure CLI](../azure-resource-manager/management/manage-resource-groups-cli.md#export-resource-groups-to-templates), [Azure PowerShell](../azure-resource-manager/management/manage-resource-groups-powershell.md#export-resource-groups-to-templates), or [REST API](https://docs.microsoft.com/rest/api/resources/resourcegroups/exporttemplate).
2525

2626
2. If applicable, [export other resources in the same resource group](https://docs.microsoft.com/azure/azure-resource-manager/templates/export-template-portal#export-template-from-a-resource-group) for redeployment in the target region.
2727

@@ -33,7 +33,7 @@ This article describes how to move your Service Fabric Mesh application and its
3333

3434
2. With your exported template, follow the steps in [Deploy resources from custom template](https://docs.microsoft.com/azure/azure-resource-manager/templates/deploy-portal#deploy-resources-from-custom-template) using the Azure portal. You can also use [Azure CLI](https://docs.microsoft.com/azure/azure-resource-manager/templates/deploy-cli), [Azure PowerShell](https://docs.microsoft.com/azure/azure-resource-manager/templates/deploy-powershell), or [REST API](https://docs.microsoft.com/azure/azure-resource-manager/templates/deploy-rest).
3535

36-
3. For guidance on moving related resources such as [Azure Storage accounts](../storage/common/storage-account-move), refer to guidance for individual services listed under the topic [Moving Azure resources across regions](../azure-resource-manager/management/move-region.md).
36+
3. For guidance on moving related resources such as [Azure Storage accounts](../storage/common/storage-account-move.md), refer to guidance for individual services listed under the topic [Moving Azure resources across regions](../azure-resource-manager/management/move-region.md).
3737

3838
## Verify
3939

0 commit comments

Comments
 (0)