You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Make sure the Azure external load balancer is in the Azure region from which you want to move.
38
39
@@ -46,12 +47,12 @@ Use this procedure to move an internal load balancer to another region using the
46
47
47
48
- 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).
48
49
49
-
## Prepare and move
50
+
####Prepare and move
50
51
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.
### 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
55
56
56
57
1. Sign in to the [Azure portal](https://portal.azure.com) and select **Resource groups**.
57
58
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
189
190
190
191
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.
191
192
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
193
194
194
195
1. Sign in to the [Azure portal](https://portal.azure.com) and select **Resource groups**.
195
196
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
435
436
436
437
19. Select **Purchase** to deploy the target public IP.
437
438
438
-
## Discard
439
+
### Discard
439
440
440
441
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.
441
442
442
-
## Clean up
443
+
### Clean up
443
444
444
445
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.
445
446
446
-
## Next steps
447
+
### Next steps
447
448
448
449
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:
449
450
@@ -453,7 +454,7 @@ In this tutorial, you moved an Azure external load balancer from one region to a
- Make sure that the Azure external load balancer is in the Azure region from which you want to move.
459
460
@@ -468,13 +469,13 @@ In this tutorial, you moved an Azure external load balancer from one region to a
468
469
- 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)
469
470
470
471
471
-
## Prepare and move
472
+
### Prepare and move
472
473
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.
### Export the public IP template and deploy from Azure PowerShell
478
+
#### Export the public IP template and deploy from Azure PowerShell
478
479
479
480
1. Sign in to your Azure subscription with the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) command and follow the on-screen directions:
480
481
@@ -642,7 +643,7 @@ The following steps show how to prepare the external load balancer for the move
642
643
643
644
```
644
645
645
-
### Export the external load balancer template and deploy from Azure PowerShell
646
+
#### Export the external load balancer template and deploy from Azure PowerShell
646
647
647
648
1. Sign in to your Azure subscription with the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) command and follow the on-screen directions:
648
649
@@ -931,7 +932,7 @@ The following steps show how to prepare the external load balancer for the move
931
932
932
933
```
933
934
934
-
## Discard
935
+
### Discard
935
936
936
937
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):
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)
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:
966
967
@@ -970,7 +971,7 @@ In this tutorial, you moved an Azure network security group from one region to a
- Make sure that the Azure internal load balancer is in the Azure region from which you want to move.
976
977
@@ -985,13 +986,13 @@ In this tutorial, you moved an Azure network security group from one region to a
985
986
- 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)
986
987
987
988
988
-
## Prepare and move
989
+
### Prepare and move
989
990
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.
### Export the virtual network template and deploy from the Azure portal
995
+
#### Export the virtual network template and deploy from the Azure portal
995
996
996
997
1. Sign in to the [Azure portal](https://portal.azure.com) > **Resource Groups**.
997
998
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
1370
1371
1371
1372
19. Select the **Purchase** button to deploy the target virtual network.
1372
1373
1373
-
## Discard
1374
+
### Discard
1374
1375
1375
1376
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.
1376
1377
1377
-
## Clean up
1378
+
### Clean up
1378
1379
1379
1380
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.
1380
1381
1381
-
## Next steps
1382
+
### Next steps
1382
1383
1383
1384
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:
1384
1385
@@ -1389,7 +1390,7 @@ In this tutorial, you moved an Azure internal load balancer from one region to a
- Make sure that the Azure internal load balancer is in the Azure region from which you want to move.
1395
1396
@@ -1404,13 +1405,13 @@ In this tutorial, you moved an Azure internal load balancer from one region to a
1404
1405
- 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)
1405
1406
1406
1407
1407
-
## Prepare and move
1408
+
### Prepare and move
1408
1409
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.
### Export the virtual network template and deploy from Azure PowerShell
1414
+
#### Export the virtual network template and deploy from Azure PowerShell
1414
1415
1415
1416
1. Sign in to your Azure subscription with the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) command and follow the on-screen directions:
1416
1417
@@ -1591,7 +1592,7 @@ The following steps show how to prepare the internal load balancer for the move
### Export the internal load balancer template and deploy from Azure PowerShell
1595
+
#### Export the internal load balancer template and deploy from Azure PowerShell
1595
1596
1596
1597
1. Sign in to your Azure subscription with the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) command and follow the on-screen directions:
1597
1598
@@ -1853,8 +1854,7 @@ The following steps show how to prepare the internal load balancer for the move
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):
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)
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:
0 commit comments