Merge pull request #204250 from stegag/patch-31

Update vpn-gateway-howto-aws-bgp.md

Author: PRMerger10

articles/vpn-gateway/vpn-gateway-howto-aws-bgp.md

@@ -53,7 +53,8 @@ For example, if you set your AWS **Inside IPv4 CIDR** to be **169.254.21.0/30**,
    >
    > [!IMPORTANT]
    >
-   > Your APIPA addresses must not overlap between the on-premises VPN devices and all connected Azure VPN gateways.
+   > 1. Your APIPA addresses must not overlap between the on-premises VPN devices and all connected Azure VPN gateways.
+   > 2. If you choose to configure multiple APIPA BGP peer addresses on the VPN gateway, you must also configure all Connection objects with their corresponding IP address of your choice. If you fail to do so, all connections will use the first APIPA IP address in the list no matter how many IPs are present.
    >
 
 ## Prerequisites
@@ -264,4 +265,4 @@ Verify that you have a **local network gateway** and **connection** for **each o
 2. In the navigation pane, click **Site-to-Site VPN Connections**.
 3. Select the first connection you made and then select the **Tunnel Details** tab.
 4. Verify that the **Status** of both tunnels shows as **UP**.
-5. Verify that the **Details** of both tunnels shows one or more BGP routes.
+5. Verify that the **Details** of both tunnels shows one or more BGP routes.