Merge pull request #217776 from halkazwini/rs-limits3

Route Server: Update: Route Server Limits (include file)

Author: prmerger-automator[bot]

articles/route-server/overview.md

@@ -5,7 +5,7 @@ services: route-server
 author: halkazwini
 ms.service: route-server
 ms.topic: overview
-ms.date: 07/27/2022
+ms.date: 11/09/2022
 ms.author: halkazwini
 #Customer intent: As an IT administrator, I want to learn about Azure Route Server and what I can use it for.
 ---

includes/route-server-limits.md

@@ -3,14 +3,14 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: route-server
 ms.topic: include
-ms.date: 07/26/2022
+ms.date: 11/09/2022
 ---
 | Resource | Limit |
 |----------|-------|
 | Number of BGP peers supported | 8 |
 | Number of routes each BGP peer can advertise to Azure Route Server <sup>1</sup> | 1000 |
 | Number of routes that Azure Route Server can advertise to ExpressRoute or VPN gateway <sup>2</sup>  | 200 |
-| Number of VMs in the virtual network (including peered virtual networks) that Azure Route Server can support <sup>3</sup> | 2000 |
+| Number of VMs in the virtual network (including peered virtual networks) that Azure Route Server can support <sup>3</sup> | 4000 |
 
 <sup>1</sup> If your NVA advertises more routes than the limit, the BGP session will get dropped. In the event BGP session is dropped between the gateway and Azure Route Server, you'll lose connectivity from your on-premises network to Azure.