Merge pull request #295226 from halkazwini/rs-portal

Update portal quickstart

Author: v-shils

articles/route-server/media/quickstart-create-route-server-portal/create-route-server.png

@@ -5,15 +5,15 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-route-server
 ms.topic: quickstart
-ms.date: 02/10/2025
+ms.date: 02/25/2025
 ms.custom: mode-ui
 ---
 
 # Quickstart: Create an Azure Route Server using the Azure portal
 
 In this quickstart, you learn how to create an Azure Route Server to peer with a network virtual appliance (NVA) in your virtual network using the Azure portal.
 
-:::image type="content" source="./media/environment-diagram.png" alt-text="Diagram of Route Server deployment environment using the Azure portal.":::
+:::image type="content" source="./media/route-server-diagram.png" alt-text="Diagram of Route Server deployment environment using the Azure portal.":::
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
@@ -49,11 +49,11 @@ In this section, you create a route server.
     | Region | Select **East US** or any region you prefer to create the route server in. |
     | Routing Preference | Select **ExpressRoute**. Other available options: **VPN** and **ASPath**. |
     | **Configure virtual networks** |  |
-    | Virtual network | Select **Create new**. <br>In **Name**, enter ***myRouteServerVNet***. <br>In **Address range**, enter ***10.0.0.0/16***. <br>In **Subnet name** and **Address range**, enter ***RouteServerSubnet*** and ***10.0.1.0/26*** respectively. <br>Select **OK**. |
+    | Virtual network | Select **Create new**. <br>In **Name**, enter ***myVirtualNetwork***. <br>In **Address range**, enter ***10.0.0.0/16***. <br>In **Subnet name** and **Address range**, enter ***RouteServerSubnet*** and ***10.0.1.0/26*** respectively. <br>Select **OK**. |
     | Subnet | Once you created the virtual network and subnet, the **RouteServerSubnet** will populate. <br>- The subnet must be named *RouteServerSubnet*.<br>- The subnet must be a minimum of /26 or larger. |
     | **Public IP address** |  |
     | Public IP address | Select **Create new**. or select an existing Standard public IP resource to assign to the Route Server. To ensure connectivity to the backend service that manages the Route Server configuration, a public IP address is required. |
-    | Public IP address name | Enter ***myRouteServerVNet-ip***. A Standard public IP address is required to ensure connectivity to the backend service that manages the route server. |
+    | Public IP address name | Enter ***myVirtualNetwork-ip***. A Standard public IP address is required to ensure connectivity to the backend service that manages the route server. |
 
     :::image type="content" source="./media/quickstart-create-route-server-portal/create-route-server.png" alt-text="Screenshot that shows the Basics tab or creating a route server." lightbox="./media/quickstart-create-route-server-portal/create-route-server.png":::     
 

articles/route-server/media/route-server-diagram.png

@@ -3,7 +3,7 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-route-server
 ms.topic: include
-ms.date: 06/17/2022
+ms.date: 02/25/2025
 ---
 > [!IMPORTANT]
-> Azure Route Servers created before November 1, 2021, that don't have a public IP address associated, are deployed with the [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) offering. The public preview offering is not backed by General Availability SLA and support. To deploy Azure Route Server with the General Availability offering, and to achieve General Availability SLA and support, please delete and recreate your Route Server.
+> Route servers created before November 1, 2021, without an associated public IP address, were deployed with the [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) offering. The public preview offering doesn't include General Availability SLA and support. To deploy a route server with the General Availability offering and qualify for the General Availability SLA and support, delete and recreate your route server.