Merge pull request #233670 from halkazwini/rs-ps2

Route Server: Freshness: Quickstart: Create and configure Route Server using Azure PowerShell

Author: prmerger-automator[bot]

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

@@ -4,10 +4,10 @@ description: In this quickstart, you learn how to create and configure an Azure
 services: route-server
 author: halkazwini
 ms.author: halkazwini
-ms.date: 07/28/2022
+ms.date: 04/06/2023
 ms.topic: quickstart
 ms.service: route-server
-ms.custom: devx-track-azurepowershell, mode-api, template-quickstart
+ms.custom: template-quickstart, devx-track-azurepowershell, mode-api, engagement-fy23
 ---
 
 # Quickstart: Create and configure Route Server using Azure PowerShell
@@ -67,7 +67,7 @@ $subnetConfig = Add-AzVirtualNetworkSubnetConfig @subnet
 
 $virtualnetwork | Set-AzVirtualNetwork
 
-$vnetInfo = Get-AzVirtualNetwork -Name myVirtualNetwork
+$vnetInfo = Get-AzVirtualNetwork -Name myVirtualNetwork -ResourceGroupName myRouteServerRG
 $subnetId = (Get-AzVirtualNetworkSubnetConfig -Name RouteServerSubnet -VirtualNetwork $vnetInfo).Id
 ```
 
@@ -104,13 +104,13 @@ $subnetId = (Get-AzVirtualNetworkSubnetConfig -Name RouteServerSubnet -VirtualNe
 
 To establish BGP peering from the Route Server to your NVA use [Add-AzRouteServerPeer](/powershell/module/az.network/add-azrouteserverpeer):
 
-The “your_nva_ip” is the virtual network IP assigned to the NVA. The “your_nva_asn” is the Autonomous System Number (ASN) configured in the NVA. The ASN can be any 16-bit number other than the ones in the range of 65515-65520. This range of ASNs are reserved by Microsoft.
+The `your_nva_ip` is the virtual network IP assigned to the NVA. The `your_nva_asn` is the Autonomous System Number (ASN) configured in the NVA. The ASN can be any 16-bit number other than the ones in the range of 65515-65520. This range of ASNs is reserved by Microsoft.
 
 ```azurepowershell-interactive
 $peer = @{
-    PeerName = 'myNVA"
-    PeerIp = '192.168.0.1'
-    PeerAsn = '65501'
+    PeerName = 'myNVA'
+    PeerIp = 'your_nva_ip'
+    PeerAsn = 'your_nva_asn'
     RouteServerName = 'myRouteServer'
     ResourceGroupName = myRouteServerRG'
 }
@@ -131,7 +131,7 @@ $routeserver = @{
 Get-AzRouteServer @routeserver
 ```
 
-The output will look like the following:
+The output looks like the following:
 
 ``` 
 RouteServerAsn : 65515
@@ -144,6 +144,9 @@ RouteServerIps : {10.5.10.4, 10.5.10.5}
 
 If you have an ExpressRoute and an Azure VPN gateway in the same virtual network and you want them to exchange routes, you can enable route exchange on the Azure Route Server.
 
+> [!IMPORTANT]
+> Azure VPN gateway must be configured in **active-active** mode and have the ASN set to 65515.
+
 1. To enable route exchange between Azure Route Server and the gateway(s), use [Update-AzRouteServer](/powershell/module/az.network/update-azrouteserver) with the *-AllowBranchToBranchTraffic* flag:
 
 ```azurepowershell-interactive