Skip to content

Commit 05d2618

Browse files
committed
split of internal load balancer doc to powershell
1 parent aff82f9 commit 05d2618

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/load-balancer/move-across-regions-internal-load-balancer-powershell.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.author: allensu
1010

1111
# Move Azure internal Load Balancer to another region using PowerShell
1212

13-
There are various scenarios in which you'd want to move your existing internal load balancer from one region to another. For example, you may want to create an internal load balancer with the same configuration for testing. You may also want to move a internal load balancer to another region as part of disaster recovery planning.
13+
There are various scenarios in which you'd want to move your existing internal load balancer from one region to another. For example, you may want to create an internal load balancer with the same configuration for testing. You may also want to move an internal load balancer to another region as part of disaster recovery planning.
1414

1515
Azure internal load balancers can't be moved from one region to another. You can however, use an Azure Resource Manager template to export the existing configuration and virtual network of an internal load balancer. You can then stage the resource in another region by exporting the load balancer and virtual network to a template, modifying the parameters to match the destination region, and then deploy the templates to the new region. For more information on Resource Manager and templates, see [Export resource groups to templates](https://docs.microsoft.com/azure/azure-resource-manager/manage-resource-groups-powershell#export-resource-groups-to-templates)
1616

@@ -21,7 +21,7 @@ Azure internal load balancers can't be moved from one region to another. You can
2121

2222
- Azure internal load balancers can't be moved between regions. You'll have to associate the new load balancer to resources in the target region.
2323

24-
- To export a internal load balancer configuration and deploy a template to create a internal load balancer in another region, you'll need the Network Contributor role or higher.
24+
- To export an internal load balancer configuration and deploy a template to create an internal load balancer in another region, you'll need the Network Contributor role or higher.
2525

2626
- Identify the source networking layout and all the resources that you're currently using. This layout includes but isn't limited to load balancers, network security groups, virtual machines, and virtual networks.
2727

@@ -31,7 +31,7 @@ Azure internal load balancers can't be moved from one region to another. You can
3131

3232

3333
## Prepare and move
34-
The following steps show how to prepare the internal load balancer for the move using an Resource Manager template, and move the internal load balancer configuration to the target region using Azure PowerShell. As part of this process, the virtual network configuration of the internal load balancer must be included and must be done first before moving the internal load balancer.
34+
The following steps show how to prepare the internal load balancer for the move using a Resource Manager template, and move the internal load balancer configuration to the target region using Azure PowerShell. As part of this process, the virtual network configuration of the internal load balancer must be included and must be done first before moving the internal load balancer.
3535

3636

3737
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]

0 commit comments

Comments
 (0)