Merge pull request #212846 from cburuzie/patch-23

Update upgrade-basicInternal-standard.md

Author: prmerger-automator[bot]

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

@@ -27,7 +27,7 @@ This article introduces a PowerShell script that creates a Standard Load Balance
 * The Basic Load Balancer needs to be in the same resource group as the backend VMs and NICs.
 * 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. Make sure they are not empty.
-* The script cannot migrate Virtual Machine Scale Set from Basic Load Balancer's backend to Standard Load Balancer's backend. We recommend manually creating a Standard Load Balancer and follow [Update or delete a load balancer used by virtual machine scale sets](./update-load-balancer-with-vm-scale-set.md) to complete the migration.
+* The script cannot migrate Virtual Machine Scale Set from Basic Load Balancer's backend to Standard Load Balancer's backend. For this type of upgrade, see [Upgrade a basic load balancer used with Virtual Machine Scale Sets](./upgrade-basic-standard-virtual-machine-scale-sets.md) for instructions and more information.
 
 ## Change IP allocation method to Static for frontend IP Configuration (Ignore this step if it's already static)
 
@@ -98,4 +98,4 @@ Yes it migrates traffic. If you would like to migrate traffic personally, use [t
 
 ## Next steps
 
-[Learn about Standard Load Balancer](load-balancer-overview.md)
+[Learn about Standard Load Balancer](load-balancer-overview.md)