Merge pull request #112099 from irenehua/patch-18

Update upgrade-basicInternal-standard.md

Author: v-shils

articles/load-balancer/concepts-limitations.md

@@ -169,6 +169,8 @@ Load balancer supports both Basic and Standard SKUs. These SKUs differ in scenar
 
 The complete scenario configuration might differ slightly depending on SKU. Load balancer documentation calls out when an article applies only to a specific SKU. To compare and understand the differences, see the following table. For more information, see [Azure Standard Load Balancer overview](load-balancer-standard-overview.md).
 
+To upgrade Basic Load Balancer to Standard, see [Upgrade a Basic Load Balancer](upgrade-basic-standard.md).
+
 >[!NOTE]
 > Microsoft recommends Standard Load Balancer.
 Standalone VMs, availability sets, and virtual machine scale sets can be connected to only one SKU, never both. Load Balancer and the public IP address SKU must match when you use them with public IP addresses. Load Balancer and public IP SKUs aren't mutable.
@@ -205,6 +207,7 @@ For more information, see [Load balancer limits](https://docs.microsoft.com/azur
 
 ## Next steps
 
+- See [Upgrade a Basic Load Balancer](upgrade-basic-standard.md) to upgrade Basic Load Balancer to Standard Load Balancer.
 - See [Create a public Standard Load Balancer](quickstart-load-balancer-standard-public-portal.md) to get started with using a Load Balancer: create one, create VMs with a custom IIS extension installed, and load balance the web app between the VMs.
 - Learn more about [Azure Load Balancer](load-balancer-overview.md).
 - Learn about using [Standard Load Balancer and Availability Zones](load-balancer-standard-availability-zones.md).

articles/load-balancer/load-balancer-overview.md

@@ -79,6 +79,7 @@ Basic Load Balancer is offered at no charge.
 See [SLA for Load Balancer](https://aka.ms/lbsla). Basic Load Balancer has no SLA.
 
 ## Next steps
+See [Upgrade a Basic Load Balancer](upgrade-basic-standard.md) to upgrade Basic Load Balancer to Standard Load Balancer.
 
 See [Create a public Standard Load Balancer](quickstart-load-balancer-standard-public-portal.md) to get started with using a Load Balancer.
 

articles/load-balancer/upgrade-InternalBasic-To-PublicStandard.md

@@ -16,8 +16,7 @@ There are four stages in a upgrade:
 
 1. Migrate the configuration to Standard Public Load Balancer
 2. Add VMs to backend pools of Standard Public Load Balancer
-3. Create an outbound rule on the Load Balancer for outbound connection
-4. Set up NSG rules for Subnet/VMs that should be refrained from/to the Internet
+3. Set up NSG rules for Subnet/VMs that should be refrained from/to the Internet
 
 This article covers configuration migration. Adding VMs to backend pools may vary depending on your specific environment. However, some high-level, general recommendations [are provided](#add-vms-to-backend-pools-of-standard-load-balancer).
 
@@ -27,6 +26,7 @@ An Azure PowerShell script is available that does the following:
 
 * Creates a Standard SKU Public Load Balancer in the resource group and location that you specify.
 * Seamlessly copies the configurations of the Basic SKU Internal Load Balancer to the newly create Standard Public Load Balancer.
+* Creates an outbound rule which enables egress connectivity.
 
 ### Caveats\Limitations
 
@@ -37,7 +37,7 @@ An Azure PowerShell script is available that does the following:
 
 ## Download the script
 
-Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzurePublicLBUpgrade/1.0).
+Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzureLBUpgrade/2.0).
 ## Use the script
 
 There are two options for you depending on your local PowerShell environment setup and preferences:

articles/load-balancer/upgrade-basic-standard.md

@@ -16,7 +16,6 @@ There are three stages in a upgrade:
 
 1. Migrate the configuration
 2. Add VMs to backend pools of Standard Load Balancer
-3. Create an outbound rule on the load balancer for outbound connection
 
 This article covers configuration migration. Adding VMs to backend pools may vary depending on your specific environment. However, some high-level, general recommendations [are provided](#add-vms-to-backend-pools-of-standard-load-balancer).
 
@@ -26,17 +25,18 @@ An Azure PowerShell script is available that does the following:
 
 * Creates a Standard SKU Load Balancer in the resource group and location the you specify.
 * Seamlessly copies the configurations of the Basic SKU Load Balancer to the newly create Standard Load Balancer.
+* Creates a default outbound rule which enables outbound connectivity.
 
 ### Caveats\Limitations
 
-* Script only supports Public Load Balancer upgrade. For Internal Basic Load Balancer upgrade, create a Standard Internal Load Balancer if outbound connectivity is not desired, and create a Standard Internal Load Balancer and Standard Public Load Balancer if outbound connectivity is required.
+* Script only supports Public Load Balancer upgrade. For Internal Basic Load Balancer upgrade, refer to [this page](https://docs.microsoft.com/azure/load-balancer/upgrade-basicinternal-standard) for instructions.
 * The Standard Load Balancer has a new public address. It’s impossible to move the IP addresses associated with existing Basic Load Balancer seamlessly to Standard Load Balancer since they have different SKUs.
 * If the Standard load balancer is created in a different region, you won’t be able to associate the VMs existing in the old region to the newly created Standard Load Balancer. To work around this limitation, make sure to create a new VM in the new region.
 * If your Load Balancer does not have any frontend IP configuration or backend pool, you are likely to hit an error running the script. Please make sure they are not empty.
 
 ## Download the script
 
-Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzurePublicLBUpgrade/1.0).
+Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzurePublicLBUpgrade/2.0).
 ## Use the script
 
 There are two options for you depending on your local PowerShell environment setup and preferences:

articles/load-balancer/upgrade-basicInternal-standard.md

@@ -12,30 +12,26 @@ ms.author: irenehua
 # Upgrade Azure Internal Load Balancer- No Outbound Connection Required
 [Azure Standard Load Balancer](load-balancer-overview.md) offers a rich set of functionality and high availability through zone redundancy. To learn more about Load Balancer SKU, see [comparison table](https://docs.microsoft.com/azure/load-balancer/concepts-limitations#skus).
 
-There are two stages in an upgrade:
-
-1. Migrate the configuration
-2. Add VMs to backend pools of Standard Load Balancer
-
-This article covers configuration migration. Adding VMs to backend pools may vary depending on your specific environment. However, some high-level, general recommendations [are provided](#add-vms-to-backend-pools-of-standard-load-balancer).
+This article introduces a PowerShell script which creates a Standard Load Balancer with the same configuration as the Basic Load Balancer along with migrating traffic from Basic Load Balancer to Standard Load Balancer.
 
 ## Upgrade overview
 
 An Azure PowerShell script is available that does the following:
 
 * Creates a Standard Internal SKU Load Balancer in the location that you specify. Note that no [outbound connection](https://docs.microsoft.com/azure/load-balancer/load-balancer-outbound-connections) will not be provided by the Standard Internal Load Balancer.
-* Seamlessly copies the configurations of the Basic SKU Load Balancer to the newly create Standard Load Balancer.
+* Seamlessly copies the configurations of the Basic SKU Load Balancer to the newly created Standard Load Balancer.
+* Seamlessly move the private IPs from Basic Load Balancer to the newly created Standard Load Balancer.
+* Seamlessly move the VMs from backend pool of the Basic Load Balancer to the backend pool of the Standard Load Balancer
 
 ### Caveats\Limitations
 
 * Script only supports Internal Load Balancer upgrade where no outbound connection is required. If you required [outbound connection](https://docs.microsoft.com/azure/load-balancer/load-balancer-outbound-connections) for some of your VMs, please refer to this [page](upgrade-InternalBasic-To-PublicStandard.md) for instructions. 
-* The Standard Load Balancer has new public addresses. It’s impossible to move the IP addresses associated with existing Basic Load Balancer seamlessly to Standard Load Balancer since they have different SKUs.
 * If the Standard load balancer is created in a different region, you won’t be able to associate the VMs existing in the old region to the newly created Standard Load Balancer. To work around this limitation, make sure to create a new VM in the new region.
-* If your Load Balancer does not have any frontend IP configuration or backend pool, you are likely to hit an error running the script. Please make sure they are not empty.
+* If your Load Balancer does not have any frontend IP configuration or backend pool, you are likely to hit an error running the script. Make sure they are not empty.
 
 ## Download the script
 
-Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzureILBUpgrade/1.0).
+Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzureILBUpgrade/2.0).
 ## Use the script
 
 There are two options for you depending on your local PowerShell environment setup and preferences:
@@ -79,30 +75,6 @@ To run the script:
    AzureILBUpgrade.ps1 -rgName "test_InternalUpgrade_rg" -oldLBName "LBForInternal" -newlocation "centralus" -newLbName "LBForUpgrade"
    ```
 
-### Add VMs to backend pools of Standard Load Balancer
-
-First, double check that the script successfully created a new Standard Internal Load Balancer with the exact configuration migrated over from your Basic Internal Load Balancer. You can verify this from the Azure portal.
-
-Be sure to send a small amount of traffic through the Standard Load Balancer as a manual test.
-  
-Here are a few scenarios of how you add VMs to backend pools of the newly created Standard Internal Load Balancer may be configured, and our recommendations for each one:
-
-* **Moving existing VMs from backend pools of old Basic Internal Load Balancer to backend pools of newly created Standard Internal Load Balancer**.
-    1. To do the tasks in this quickstart, sign in to the [Azure portal](https://portal.azure.com).
- 
-    1. Select **All resources** on the left menu, and then select the **newly created Standard Load Balancer** from the resource list.
-   
-    1. Under **Settings**, select **Backend pools**.
-   
-    1. Select the backend pool which matches the backend pool of the Basic Load Balancer, select the following value: 
-      - **Virtual Machine**: Drop down and select the VMs from the matching backend pool of the Basic Load Balancer.
-    1. Select **Save**.
-    >[!NOTE]
-    >For VMs which have Public IPs, you will need to create Standard IP addresses first where same IP address is not guaranteed. Disassociate VMs from Basic IPs and associate them with the newly created Standard IP addresses. Then, you will be able to follow instructions to add VMs into backend pool of Standard Load Balancer. 
-
-* **Creating new VMs to add to the backend pools of the newly created Standard Internal Load Balancer**.
-    * More instructions on how to create VM and associate it with Standard Load Balancer can be found [here](https://docs.microsoft.com/azure/load-balancer/quickstart-load-balancer-standard-public-portal#create-virtual-machines).
-
 ## Common questions
 
 ### Are there any limitations with the Azure PowerShell script to migrate the configuration from v1 to v2?
@@ -111,7 +83,7 @@ Yes. See [Caveats/Limitations](#caveatslimitations).
 
 ### Does the Azure PowerShell script also switch over the traffic from my Basic Load Balancer to the newly created Standard Load Balancer?
 
-No. The Azure PowerShell script only migrates the configuration. Actual traffic migration is your responsibility and in your control.
+Yes it migrates traffic. If you would like to migrate traffic personally, use [this script](https://www.powershellgallery.com/packages/AzureILBUpgrade/1.0) which does not move VMs for you.
 
 ### I ran into some issues with using this script. How can I get help?