update

Author: halkazwini

articles/route-server/expressroute-vpn-support.md

@@ -5,8 +5,9 @@ services: route-server
 author: halkazwini
 ms.service: route-server
 ms.topic: conceptual
-ms.date: 10/01/2021
+ms.date: 01/09/2023
 ms.author: halkazwini
+ms.custom: template-concept, 
 ---
 
 # Azure Route Server support for ExpressRoute and Azure VPN
@@ -16,29 +17,32 @@ Azure Route Server supports not only third-party network virtual appliances (NVA
 
 ## How does it work?
 
-When you deploy an Azure Route Server along with an ExpressRoute gateway and an NVA in a virtual network, by default Azure Route Server doesn’t propagate the routes it receives from the NVA and ExpressRoute gateway between each other. Once you enable the route exchange, ExpressRoute and the NVA will learn each other’s routes.
+When you deploy an Azure Route Server along with a virtual network gateway and an NVA in a virtual network, by default Azure Route Server doesn’t propagate the routes it receives from the NVA and virtual network gateway between each other. Once you enable **branch-to-branch** in Route Server, the virtual network gateway and the NVA will exchange their routes.
 
 For example, in the following diagram:
 
 * The SDWAN appliance will receive from Azure Route Server the route from “On-premises 2”, which is connected to ExpressRoute, along with the virtual network route.
 
 * The ExpressRoute gateway will receive the route from “On-premises 1”, which is connected to the SDWAN appliance, along with the virtual network route from Azure Route Server.
 
-    ![Diagram showing ExpressRoute configured with Route Server.](./media/expressroute-vpn-support/expressroute-with-route-server.png)
+:::image type="content" source="./media/expressroute-vpn-support/expressroute-with-route-server.png" alt-text="Diagram showing ExpressRoute gateway and SDWAN NVA exchanging routes through Azure Route Server.":::
 
 You can also replace the SDWAN appliance with Azure VPN gateway. Since Azure VPN gateway and ExpressRoute are fully managed, you only need to enable the route exchange for the two on-premises networks to talk to each other.
 
 > [!IMPORTANT] 
-> * Azure VPN gateway must be configured in [**active-active**](../vpn-gateway/vpn-gateway-activeactive-rm-powershell.md) mode and have the ASN set to 65515.
-> * When you create or delete an Azure Route Server from a virtual network that contains a Virtual Network Gateway (ExpressRoute or VPN), expect downtime until the operation complete.
+> Azure VPN gateway must be configured in [**active-active**](../vpn-gateway/vpn-gateway-activeactive-rm-powershell.md) mode and have the ASN set to 65515.
+>
+
+> [!WARNING]
+> When you create or delete an Azure Route Server from a virtual network that contains a virtual network gateway (ExpressRoute or VPN), expect downtime until the operation complete.
+>
 
-![Diagram showing ExpressRoute and VPN gateway configured with Route Server.](./media/expressroute-vpn-support/expressroute-and-vpn-with-route-server.png)
+:::image type="content" source="./media/expressroute-vpn-support/expressroute-and-vpn-with-route-server.png" alt-text="Diagram showing ExpressRoute gateway and VPN gateways exchanging routes through Azure Route Server.":::
 
 > [!IMPORTANT] 
 > When the same route is learned over ExpressRoute, Azure VPN or an SDWAN appliance, the ExpressRoute network will be preferred.
 >
 
-
 ## Next steps
 
 - Learn more about [Azure Route Server](route-server-faq.md).