Updated some clarity on HOBO and zone redundancy in Expressroute

articles/expressroute/expressroute-about-virtual-network-gateways.md

@@ -88,7 +88,7 @@ The Auto-Assigned Public IP feature simplifies ExpressRoute gateway deployment b
 
 **How it works:**  
 
-When you create an ExpressRoute gateway, Microsoft automatically provisions and manages the public IP address in a secure, backend subscription. This IP is encapsulated within the gateway resource, enabling Microsoft to enforce policies such as data rate limits and enhance auditability.
+When you create an ExpressRoute gateway, Microsoft automatically provisions and manages the public IP address in a secure, backend subscription. This IP is encapsulated within the gateway resource, enabling Microsoft to enforce policies such as data rate limits and enhance auditability. Previously it was possible to create the public IP resource as a zonal resource which ensured that all instances of the gateway in that zone shared the same public IP address. New behavior is that the gateway is always zone redundant.
 
 **Availability:**  
 

articles/expressroute/expressroute-howto-add-gateway-portal-resource-manager.md

@@ -79,8 +79,7 @@ The steps for this tutorial use the values in the following configuration refere
     | Minimum Scale Units | This option is only available when you select the **ErGwScale (Preview)** SKU. Enter the minimum number of scale units you want to use. For more information, see [ExpressRoute Gateway Scale Units](scalable-gateway.md). |
     | Maximum Scale Units | This option is only available when you select the **ErGwScale (Preview)** SKU. Enter the maximum number of scale units you want to use. For more information, see [ExpressRoute Gateway Scale Units](scalable-gateway.md). |
     | Virtual network | Select *vnet-1*. |
-    | **Public IP address** | |
-    | Assignment | By default, all ExpressRoute Gateways will have an [Auto-Assigned Public IP](expressroute-about-virtual-network-gateways.md#auto-assigned-public-ip). |
+    | **Public IP address** | ExpressRoute Gateways now have an [Auto-Assigned Public IP](expressroute-about-virtual-network-gateways.md#auto-assigned-public-ip). This Public IP address is automatically assigned to the gateway during its creation, which means zonal gateways can no longer be created. |
 
     > [!IMPORTANT]
     > If you plan to use IPv6-based private peering over ExpressRoute, please make sure to create your gateway with a Public IP address of type Standard, Static using the [PowerShell instructions](./expressroute-howto-add-gateway-resource-manager.md#add-a-gateway).

articles/expressroute/expressroute-howto-add-gateway-resource-manager.md

@@ -41,8 +41,6 @@ The steps for this task use a VNet based on the values in the following configur
 | Gateway IP Name | *GWIP* |
 | Gateway IP configuration Name | *gwipconf* |
 | Type | *ExpressRoute* |
-| Gateway Public IP Name  | *gwpip* |
-
 ## Add a gateway
 
 > [!IMPORTANT]
@@ -111,8 +109,8 @@ The steps for this task use a VNet based on the values in the following configur
 
    > [!NOTE]
    > Basic SKU public IP isn't supported with new ExpressRoute virtual network gateway.
-   > Creating a public IP is no longer required, Microsoft will create and manage your public IP.
-   
+   > Creating a public IP is no longer required, [Microsoft will create and manage your public IP](expressroute-about-virtual-network-gateways.md#auto-assigned-public-ip). This means all ExpressRoute virtual network gateways are created as zone-redundant.
+
 1. Create the configuration for your gateway. The gateway configuration defines the subnet and the public IP address to use. In this step, you're specifying the configuration that will be used when you create the gateway. Use the following sample to create your gateway configuration.
 
    ```azurepowershell-interactive