Merge pull request #313293 from siddomala/16ARSpeers

Added 16 BGP peers

Author: prmerger-automator[bot]

articles/route-server/configure-route-server.md

@@ -303,7 +303,7 @@ The page output shows the following fields:
 
 * **Prefix**: Address prefix known to the current entity (learned from Route Server)
 * **Next hop type**: Can be VPN, HubBgpConnection (NVA BGP peers), Virtual Network Connection, or ExpressRoute.
-* **Next hop**: This is the IP address of the next hop (This will be "on-link" for Virtual Network connections)
+* **Next hop**: This is the IP address of the next hop (For virtual network connections, this will be "on-link". For ExpressRoute, this will be the IP address of the Microsoft Enterprise Edge Router)
 * **Origin**: Link to the resource ID of the next hop (This will be empty for Virtual Network Connections)
 * **AS Path**: BGP Attribute AS (autonomous system) path lists all the AS numbers that need to be traversed to reach the location where the prefix that the path is attached to, is advertised from.
 

includes/route-server-limits.md

@@ -7,7 +7,7 @@ ms.date: 02/07/2025
 ---
 | Resource | Limit |
 |----------|-------|
-| Number of BGP peers | 8 |
+| Number of BGP peers | 16 |
 | Number of routes each BGP peer can advertise to Azure Route Server <sup>1</sup> | 4,000 |
 | Number of VMs in the virtual network (including peered virtual networks) that Azure Route Server can support | 50,000 |
 | Number of virtual networks that Azure Route Server can support | 500 |