Updates

Author: mbender-ms

articles/load-balancer/TOC.yml

@@ -4,8 +4,6 @@
   items:
   - name: What is Azure Load Balancer?
     href: load-balancer-overview.md
-  - name: Upgrade guidance from basic to standard load balancer
-    href: load-balancer-basic-upgrade-guidance.md
 - name: Quickstarts
   items:
   - name: Create a public load balancer

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

@@ -12,14 +12,13 @@ ms.date: 09/19/2022
 # Upgrading from Basic Load Balancer - Guidance
 
 In this article, we'll discuss guidance for upgrading your Basic Load Balancer instances to Standard Load Balancer. Standard Load Balancer is recommend for all production instances and provides many [key differences](#basic-load-balancer-sku-vs-standard-load-balancer-sku) to your infrastructure.
-## Load balancer upgrade steps
+## Steps to complete the upgrade
 
 We recommend the following approach to upgrade to Standard Load Balancer:
 
 1. Learn about some of the [key differences](#basic-load-balancer-sku-vs-standard-load-balancer-sku) between Basic Load Balancer and Standard Load Balancer. 
 1. Identify the Basic load balancer to upgrade. 
 1. Create a migration plan for planned downtime. 
-1. Create migration plan for planned downtime.
 1. Perform migration with [automated PowerShell scripts](#upgrade-using-automated-scripts) for your scenario or create a new Standard Load Balancer with the Basic Load Balancer configurations.
 1. Verify your application and workloads are receiving traffic through the standard load balancer. Then delete your basic load balancer resource. 
 

articles/virtual-network/ip-services/public-ip-basic-upgrade-guidance.md

@@ -23,9 +23,9 @@ We recommend the following approach to upgrade to Standard SKU Public IP address
     1. If you need a zone redundant public IP address, create a new Standard Public IP address using [Portal](create-public-ip-portal.md), [PowerShell](create-public-ip-powershell.md), [CLI](create-public-ip-cli.md), or [ARM template](create-public-ip-template.md).
     1. If you do not need a zone redundant public IP address, use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli). 
 1. Create a migration plan for planned downtime.
-1. Depending on the service associated with your Basic Public IP addresses, perform the upgrade based on the following table:
+1. Depending on the resource associated with your Basic Public IP addresses, perform the upgrade based on the following table:
 
-    | Service using Basic Public IP addresses | Decision path |
+    | Resource using Basic Public IP addresses | Decision path |
     | ------ | ------ |
     | Virtual Machine or Virtual Machine Scale Sets | use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli). |
     | Load Balancer (Basic) | use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli).   |
@@ -40,6 +40,7 @@ This section lists out some key differences between these two Public IP addresse
 |""| Standard Public IP SKU | Basic Public IP SKU |
 |---------|---------|---------|
 | **Idle Timeout** | Have an adjustable inbound originated flow idle timeout of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle timeout of 4 minutes. | Have an adjustable inbound originated flow idle timeout of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle timeout of 4 minutes. |
+| **Allocation method** | Static. | For IPv4: Dynamic or Static; For IPv6: Dynamic. |
 | **Security** | Secure by default model and be closed to inbound traffic when used as a frontend. Allow traffic with [network security group](../network-security-groups-overview.md#network-security-groups) is required (for example, on the NIC of a virtual machine with a Standard SKU Public IP attached). | Open by default. Network security groups are recommended but optional for restricting inbound or outbound traffic. |
 | **[Availability zones](../../availability-zones/az-overview.md)** | Supported. Standard IPs can be non-zonal, zonal, or zone-redundant. Zone redundant IPs can only be created in [regions where three availability zones](../../availability-zones/az-region.md) are live. IPs created before zones are live won't be zone redundant. | Not supported |
 | **[Routing preference](routing-preference-overview.md)** | Supported to enable more granular control of how traffic is routed between Azure and the Internet. | Not supported. |