freshness review

Author: duongau

articles/frontdoor/quickstart-create-front-door.md

@@ -5,7 +5,7 @@ services: front-door
 author: duongau
 ms.author: duau
 manager: KumudD
-ms.date: 10/02/2023
+ms.date: 11/13/2024
 ms.topic: quickstart
 ms.service: azure-frontdoor
 ms.custom: template-tutorial, mode-ui, engagement-fy23
@@ -16,7 +16,7 @@ ms.custom: template-tutorial, mode-ui, engagement-fy23
 
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
 
-This quickstart shows you how to use the Azure portal to set up high availability for a web application with Azure Front Door (classic). You create an Azure Front Door (classic) configuration that distributes traffic across two instances of a web application running in different Azure regions. The configuration uses equal weighted and same priority backends, which means that Azure Front Door directs traffic to the closest available site that hosts the application. Azure Front Door also monitors the health of the web application and performs automatic failover to the next nearest site if the closest site is down.
+This quickstart guides you through setting up high availability for a web application using Azure Front Door (classic) via the Azure portal. You configure Azure Front Door to distribute traffic across two web application instances in different Azure regions. The setup uses equal weighted and same priority backends, directing traffic to the nearest available site. Azure Front Door also monitors the health of the web applications and automatically fails over to the next nearest site if the closest one is down.
 
 :::image type="content" source="media/quickstart-create-front-door/environment-diagram.png" alt-text="Diagram of Front Door deployment environment using the Azure portal." border="false":::
 
@@ -26,44 +26,42 @@ This quickstart shows you how to use the Azure portal to set up high availabilit
 
 ## Create two instances of a web app
 
-[test](front-door-diagnostics.md#access-log)
+To complete this quickstart, you need two instances of a web application running in different Azure regions. These instances operate in *Active/Active* mode, meaning they can handle traffic simultaneously. This setup differs from *Active/Stand-By* mode, where one instance serves as a backup.
 
-To complete this quickstart, you need two instances of a web application running in different Azure regions. The web application instances operate in *Active/Active* mode, which means that they can both handle traffic simultaneously. This setup is different from *Active/Stand-By* mode, where one instance serves as a backup for the other.
-
-To follow this quickstart, you need two web apps that run in different Azure regions. If you don't have them already, you can use these steps to create example web apps.
+If you don't have the web apps already, follow these steps to create them:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
-1. On the top left corner of the screen, select **+ Create a resource** and then search for **Web App**.
+1. Select **+ Create a resource** from the top left corner and search for **Web App**.
 
     :::image type="content" source="media/quickstart-create-front-door/front-door-create-web-app.png" alt-text="Create a web app in the Azure portal." lightbox="./media/quickstart-create-front-door/front-door-create-web-app.png":::
 
-1. On the Basics tab of the Create Web App page, provide or select the following details.
+1. On the Basics tab of the Create Web App page, provide, or select the following details:
 
     | Setting | Value |
     |--|--|
     | **Subscription** | Choose your subscription. |
-    | **Resource group** | Select **Create new** and type *FrontDoorQS_rg1* in the text box. |
-    | **Name** | 	Type a unique **Name** for your web app. For example, *WebAppContoso-1*. |
+    | **Resource group** | Select **Create new** and type *FrontDoorQS_rg1*. |
+    | **Name** | Type a unique name for your web app, for example, *WebAppContoso-1*. |
     | **Publish** | Select **Code**. |
     | **Runtime stack** | Select **.NET Core 3.1 (LTS)**. |
     | **Operating System** | Select **Windows**. |
     | **Region** | Select **Central US**. |
-    | **Windows Plan** | Select **Create new** and type *myAppServicePlanCentralUS* in the text box. |
+    | **Windows Plan** | Select **Create new** and type *myAppServicePlanCentralUS*. |
     | **Sku and size** | Select **Standard S1 100 total ACU, 1.75 GB memory**. |
 
-1. Select **Review + create** and verify the summary details. Then, select **Create** to initiate the deployment process. The deployment may take several minutes to complete.
+1. Select **Review + create**, verify the summary details, and then select **Create** to initiate the deployment. The deployment may take several minutes.
 
     :::image type="content" source="media/quickstart-create-front-door/create-web-app.png" alt-text="Screenshot showing Create Web App page." lightbox="./media/quickstart-create-front-door/create-web-app.png":::
 
-Once you have successfully deployed your first web app, proceed to create another one. Follow the same steps and enter the same values as before, except for the ones listed:
+1. After deploying the first web app, create another one with the same steps but with the following changes:
 
-| Setting | Value |
-|--|--|
-| **Resource group** | Select **Create new** and type *FrontDoorQS_rg2* |
-| **Name** | Type a unique name for your Web App, for example, *WebAppContoso-2* |
-| **Region** | Select a different region than the first Web App, for example, *East US* |
-| **App Service plan** > **Windows Plan** | Select **New** and type *myAppServicePlanEastUS*, and then select **OK** |
+    | Setting | Value |
+    |--|--|
+    | **Resource group** | Select **Create new** and type *FrontDoorQS_rg2*. |
+    | **Name** | Type a unique name for your web app, for example, *WebAppContoso-2*. |
+    | **Region** | Select a different region, for example, *East US*. |
+    | **App Service plan** > **Windows Plan** | Select **New** and type *myAppServicePlanEastUS*, then select **OK**. |
 
 ## Create a Front Door for your application
 
@@ -138,54 +136,53 @@ Lastly, create a routing rule. A routing rule links your frontend host to the ba
 
 
 ## View Azure Front Door in action
+Once you create a Front Door, it takes a few minutes for the configuration to be deployed globally. After deployment, access the frontend host you created by navigating to its address in your browser. Your requests automatically get routed to the nearest server from the specified servers in the backend pool.
 
-Once you create a Front Door, it takes a few minutes for the configuration to be deployed globally; once completed, access the frontend host you created. In the browser, go to your frontend host address. Your requests automatically get routed to your nearest server from the specified servers in the backend pool.
-
-If you followed this quickstart to create these apps, you see an information page.
+If you followed this quickstart to create the web apps, you should see an information page.
 
-To test the instant global failover feature, try the following steps:
+To test the instant global failover feature, follow these steps:
 
-1. Navigate to the resource group **FrontDoorQS_rg0** and select the Front Door service.”
+1. Navigate to the resource group **FrontDoorQS_rg0** and select the Front Door service.
 
     :::image type="content" source="./media/quickstart-create-front-door/front-door-view-frontend-service.png" alt-text="Screenshot of frontend service." lightbox="./media/quickstart-create-front-door/front-door-view-frontend-service.png":::
 
 1. From the **Overview** page, copy the **Frontend host** address.
 
     :::image type="content" source="./media/quickstart-create-front-door/front-door-view-frontend-host-address.png" alt-text="Screenshot of frontend host address." lightbox="./media/quickstart-create-front-door/front-door-view-frontend-host-address.png":::
 
-1. Open the browser, as described previously, and go to your frontend address.
+1. Open your browser and go to the frontend address.
 
-1. In the Azure portal, search for and select App services. Scroll down to find one of your web apps, for example, *WebAppContoso-1*.
+1. In the Azure portal, search for and select **App services**. Scroll down to find one of your web apps, for example, *WebAppContoso-1*.
 
-1. Select your web app, and then select **Stop**, and **Yes** to confirm.
+1. Select your web app, then select **Stop**, and confirm by selecting **Yes**.
 
-1. Refresh your browser. You should see the same information page.
+1. Refresh your browser. You should still see the information page.
 
     > [!TIP]
-    > These actions may take some time to take effect. You may need to refresh the browser again.”
+    > These actions may take some time to take effect. You may need to refresh the browser again.
 
-1. Locate the other web app, and stop it as well.
+1. Locate the other web app and stop it as well.
 
 1. Refresh your browser. This time, you should see an error message.
 
-   :::image type="content" source="media/quickstart-create-front-door/web-app-stopped-message.png" alt-text="Both instances of the web app stopped." lightbox="./media/quickstart-create-front-door/web-app-stopped-message.png":::
+    :::image type="content" source="media/quickstart-create-front-door/web-app-stopped-message.png" alt-text="Both instances of the web app stopped." lightbox="./media/quickstart-create-front-door/web-app-stopped-message.png":::
 
 ## Clean up resources
 
-After you're done, you can delete all the items you created. Deleting the resource group also deletes its contents. If you don't intend to use this Front Door, you should delete the resources to avoid incurring unnecessary charges.
+After completing the quickstart, you can delete the resources, you created to avoid unnecessary charges. Deleting a resource group also deletes all its contents.
 
-1. In the Azure portal, search for and select **Resource groups**, or choose **Resource groups** from the Azure portal menu.
+1. In the Azure portal, search for and select **Resource groups** from the menu.
 
-1. Filter or scroll down to find a resource group, for example, *FrontDoorQS_rg0*.
+1. Locate the resource group you want to delete, such as *FrontDoorQS_rg0*.
 
-1. Choose the resource group, then select **Delete** resource group.
+1. Select the resource group, then select **Delete resource group**.
 
     > [!WARNING]
-    > This action can't be undone.
+    > This action is irreversible.
 
-1. Enter the name of the resource group that you want to delete, and then select **Delete**.
+1. Enter the name of the resource group to confirm deletion, then select **Delete**.
 
-1. Repeat these steps for the remaining two groups.
+1. Repeat these steps for the other resource groups.
 
 ## Next steps