Skip to content

Commit 1f559e0

Browse files
committed
fix tabs
1 parent 04f1a7b commit 1f559e0

File tree

1 file changed

+28
-28
lines changed

1 file changed

+28
-28
lines changed

articles/load-balancer/move-across-regions-azure-load-balancer.md

Lines changed: 28 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,10 @@ Use this procedure to move an external load balancer to another region using the
3030
Use this procedure to move an internal load balancer to another region using the Azure portal or Azure PowerShell.
3131

3232
---
33+
3334
# [Azure portal](#tab/azure-portal/external-load-balancer)
3435

35-
## Prerequisites
36+
#### Prerequisites
3637

3738
- Make sure the Azure external load balancer is in the Azure region from which you want to move.
3839

@@ -46,12 +47,12 @@ Use this procedure to move an internal load balancer to another region using the
4647

4748
- Make sure your subscription has enough resources to support the addition of the load balancers. See [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits).
4849

49-
## Prepare and move
50+
#### Prepare and move
5051
The following procedures show how to prepare the external load balancer for the move by using a Resource Manager template and move the external load balancer configuration to the target region by using the Azure portal. You must first export the public IP configuration of external load balancer.
5152

5253
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
5354

54-
### Export the public IP template and deploy the public IP from the portal
55+
#### Export the public IP template and deploy the public IP from the portal
5556

5657
1. Sign in to the [Azure portal](https://portal.azure.com) and select **Resource groups**.
5758
2. Locate the resource group that contains the source public IP and select it.
@@ -189,7 +190,7 @@ The following procedures show how to prepare the external load balancer for the
189190

190191
20. If you have another public IP that's being used for outbound NAT for the load balancer being moved, repeat the previous steps to export and deploy the second outbound public IP to the target region.
191192

192-
### Export the external load balancer template and deploy the load balancer from the Azure portal
193+
#### Export the external load balancer template and deploy the load balancer from the Azure portal
193194

194195
1. Sign in to the [Azure portal](https://portal.azure.com) and select **Resource groups**.
195196
2. Locate the resource group that contains the source external load balancer and select it.
@@ -435,15 +436,15 @@ The following procedures show how to prepare the external load balancer for the
435436

436437
19. Select **Purchase** to deploy the target public IP.
437438

438-
## Discard
439+
### Discard
439440

440441
If you want to discard the target public IP and external load balancer, delete the resource group that contains them. To do so, select the resource group from your dashboard in the portal and then select **Delete** at the top of the overview page.
441442

442-
## Clean up
443+
### Clean up
443444

444445
To commit the changes and complete the move of the public IP and external load balancer, delete the source public IP and external load balancer or resource group. To do so, select that resource group from your dashboard in the portal and then select **Delete** at the top of each page.
445446

446-
## Next steps
447+
### Next steps
447448

448449
In this tutorial, you moved an Azure external load balancer from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, see:
449450

@@ -453,7 +454,7 @@ In this tutorial, you moved an Azure external load balancer from one region to a
453454

454455
# [Azure PowerShell](#tab/azure-powershell/external-load-balancer)
455456

456-
## Prerequisites
457+
### Prerequisites
457458

458459
- Make sure that the Azure external load balancer is in the Azure region from which you want to move.
459460

@@ -468,13 +469,13 @@ In this tutorial, you moved an Azure external load balancer from one region to a
468469
- Make sure that your subscription has enough resources to support the addition of load balancers for this process. See [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits)
469470

470471

471-
## Prepare and move
472+
### Prepare and move
472473
The following steps show how to prepare the external load balancer for the move using a Resource Manager template, and move the external load balancer configuration to the target region using Azure PowerShell. As part of this process, the public IP configuration of the external load balancer must be included and must me done first before moving the external load balancer.
473474

474475

475476
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
476477

477-
### Export the public IP template and deploy from Azure PowerShell
478+
#### Export the public IP template and deploy from Azure PowerShell
478479

479480
1. Sign in to your Azure subscription with the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) command and follow the on-screen directions:
480481

@@ -642,7 +643,7 @@ The following steps show how to prepare the external load balancer for the move
642643

643644
```
644645

645-
### Export the external load balancer template and deploy from Azure PowerShell
646+
#### Export the external load balancer template and deploy from Azure PowerShell
646647

647648
1. Sign in to your Azure subscription with the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) command and follow the on-screen directions:
648649

@@ -931,7 +932,7 @@ The following steps show how to prepare the external load balancer for the move
931932

932933
```
933934

934-
## Discard
935+
### Discard
935936

936937
After the deployment, if you wish to start over or discard the public IP and load balancer in the target, delete the resource group that was created in the target and the moved public IP and load balancer will be deleted. To remove the resource group, use [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup):
937938

@@ -941,7 +942,7 @@ Remove-AzResourceGroup -Name <resource-group-name>
941942

942943
```
943944

944-
## Clean up
945+
### Clean up
945946

946947
To commit the changes and complete the move of the NSG, delete the source NSG or resource group, use [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup) or [Remove-AzPublicIpAddress](/powershell/module/az.network/remove-azpublicipaddress) and [Remove-AzLoadBalancer](/powershell/module/az.network/remove-azloadbalancer)
947948

@@ -960,7 +961,7 @@ Remove-AzPublicIpAddress -Name <public-ip> -ResourceGroupName <resource-group-na
960961

961962
```
962963

963-
## Next steps
964+
### Next steps
964965

965966
In this tutorial, you moved an Azure network security group from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
966967

@@ -970,7 +971,7 @@ In this tutorial, you moved an Azure network security group from one region to a
970971

971972
# [Azure portal](#tab/azure-portal/internal-load-balancer)
972973

973-
## Prerequisites
974+
### Prerequisites
974975

975976
- Make sure that the Azure internal load balancer is in the Azure region from which you want to move.
976977

@@ -985,13 +986,13 @@ In this tutorial, you moved an Azure network security group from one region to a
985986
- Make sure that your subscription has enough resources to support the addition of load balancers for this process. See [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits)
986987

987988

988-
## Prepare and move
989+
### Prepare and move
989990
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 the Azure portal. 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.
990991

991992

992993
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
993994

994-
### Export the virtual network template and deploy from the Azure portal
995+
#### Export the virtual network template and deploy from the Azure portal
995996

996997
1. Sign in to the [Azure portal](https://portal.azure.com) > **Resource Groups**.
997998
2. Locate the Resource Group that contains the source virtual network and select it.
@@ -1370,15 +1371,15 @@ The following steps show how to prepare the internal load balancer for the move
13701371

13711372
19. Select the **Purchase** button to deploy the target virtual network.
13721373

1373-
## Discard
1374+
### Discard
13741375

13751376
If you wish to discard the target virtual network and internal load balancer, delete the resource group that contains the target virtual network and internal load balancer. To do so, select the resource group from your dashboard in the portal and select **Delete** at the top of the overview page.
13761377

1377-
## Clean up
1378+
### Clean up
13781379

13791380
To commit the changes and complete the move of the virtual network and internal load balancer, delete the source virtual network and internal load balancer or resource group. To do so, select the virtual network and internal load balancer or resource group from your dashboard in the portal and select **Delete** at the top of each page.
13801381

1381-
## Next steps
1382+
### Next steps
13821383

13831384
In this tutorial, you moved an Azure internal load balancer from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
13841385

@@ -1389,7 +1390,7 @@ In this tutorial, you moved an Azure internal load balancer from one region to a
13891390

13901391
# [Azure PowerShell](#tab/azure-powershell/internal-load-balancer)
13911392

1392-
## Prerequisites
1393+
### Prerequisites
13931394

13941395
- Make sure that the Azure internal load balancer is in the Azure region from which you want to move.
13951396

@@ -1404,13 +1405,13 @@ In this tutorial, you moved an Azure internal load balancer from one region to a
14041405
- Make sure that your subscription has enough resources to support the addition of load balancers for this process. See [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits)
14051406

14061407

1407-
## Prepare and move
1408+
### Prepare and move
14081409
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.
14091410

14101411

14111412
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
14121413

1413-
### Export the virtual network template and deploy from Azure PowerShell
1414+
#### Export the virtual network template and deploy from Azure PowerShell
14141415

14151416
1. Sign in to your Azure subscription with the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) command and follow the on-screen directions:
14161417

@@ -1591,7 +1592,7 @@ The following steps show how to prepare the internal load balancer for the move
15911592
Get-AzVirtualNetwork -Name <target-virtual-network-name> -ResourceGroupName <target-resource-group-name>
15921593

15931594
```
1594-
### Export the internal load balancer template and deploy from Azure PowerShell
1595+
#### Export the internal load balancer template and deploy from Azure PowerShell
15951596

15961597
1. Sign in to your Azure subscription with the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) command and follow the on-screen directions:
15971598

@@ -1853,8 +1854,7 @@ The following steps show how to prepare the internal load balancer for the move
18531854
Get-AzLoadBalancer -Name <target-publicip-name> -ResourceGroupName <target-resource-group-name>
18541855

18551856
```
1856-
1857-
## Discard
1857+
### Discard
18581858

18591859
After the deployment, if you wish to start over or discard the virtual network and load balancer in the target, delete the resource group that was created in the target and the moved virtual network and load balancer will be deleted. To remove the resource group, use [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup):
18601860

@@ -1864,7 +1864,7 @@ Remove-AzResourceGroup -Name <resource-group-name>
18641864

18651865
```
18661866

1867-
## Clean up
1867+
### Clean up
18681868

18691869
To commit the changes and complete the move of the NSG, delete the source NSG or resource group, use [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup) or [Remove-AzVirtualNetwork](/powershell/module/az.network/remove-azvirtualnetwork) and [Remove-AzLoadBalancer](/powershell/module/az.network/remove-azloadbalancer)
18701870

@@ -1883,7 +1883,7 @@ Remove-AzVirtualNetwork -Name <virtual-network-name> -ResourceGroupName <resourc
18831883

18841884
```
18851885

1886-
## Next steps
1886+
### Next steps
18871887

18881888
In this tutorial, you moved an Azure internal load balancer from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
18891889

0 commit comments

Comments
 (0)