Merge pull request #205131 from AbdullahBell/trafficmanagerQSPortal

Quickstart: Create a Traffic Manager profile using the Azure portal | Freshness review

Author: PRMerger12

articles/traffic-manager/quickstart-create-traffic-manager-profile.md

@@ -5,7 +5,7 @@ services: traffic-manager
 author: greg-lindsay
 ms.author: greglin
 manager: twooley
-ms.date: 04/19/2021
+ms.date: 07/18/2022
 ms.topic: quickstart
 ms.service: traffic-manager
 ms.workload: infrastructure-services
@@ -40,13 +40,13 @@ For this quickstart, you'll need two instances of a web application deployed in
     | Resource group          | Select **Create new** and enter *myResourceGroupTM1* in the text box.|
     | Name                    | Enter a unique **Name** for your web app. This example uses *myWebAppEastUS*. |
     | Publish                 | Select **Code**. |
-    | Runtime stack           | Select **ASP.NET V4.7**. |
+    | Runtime stack           | Select **ASP.NET V4.8**. |
     | Operating System        | Select **Windows**. |
     | Region                  | Select **East US**. |
     | Windows Plan            | Select **Create new** and enter *myAppServicePlanEastUS* in the text box. |
     | Sku and size            | Select **Standard S1 100 total ACU, 1.75-GB memory**. |
 
-1. Select the **Monitoring** tab, or select **Next: Monitoring**.  Under **Monitoring**, set **Application Insights** > **Enable Application Insights** to **No**.
+1. Select the **Monitoring** tab, or select **Next** to the **Monitoring** tab. Under **Monitoring**, set **Application Insights > Enable Application Insights** to **No**.
 
 1. Select **Review and create**.
 
@@ -93,7 +93,7 @@ Add the website in the *East US* as primary endpoint to route all the user traff
 
     :::image type="content" source="./media/quickstart-create-traffic-manager-profile/add-traffic-manager-endpoint.png" alt-text="Screenshot of where you add an endpoint to your Traffic Manager profile.":::
 
-1. Select **OK**.
+1. Select **Add**.
 1. To create a failover endpoint for your second Azure region, repeat steps 3 and 4 with these settings:
 
     | Setting | Value |
@@ -104,7 +104,7 @@ Add the website in the *East US* as primary endpoint to route all the user traff
     | Target resource | Select **Choose an app service** > **West Europe**. |
     | Priority | Select **2**. All traffic goes to this failover endpoint if the primary endpoint is unhealthy. |
 
-1. Select **OK**.
+1. Select **Add**.
 
 When you're done adding the two endpoints, they're displayed in **Traffic Manager profile**. Notice that their monitoring status is **Online** now.
 
@@ -140,7 +140,18 @@ The primary endpoint isn't available, so you were routed to the failover endpoin
 
 ## Clean up resources
 
-When you're done, delete the resource groups, web applications, and all related resources. To do so, select each individual item from your dashboard and select **Delete** at the top of each page.
+When you're done using the private link service, delete the resource group to clean up the resources used in this quickstart.
+
+1. Enter **myResourceGroupTM1** in the search box at the top of the portal, and select **myResourceGroupTM1** from the search results.
+
+1. Select **Delete resource group**.
+
+1. In **TYPE THE RESOURCE GROUP NAME**, enter **myResourceGroupTM1**.
+
+1. Select **Delete**.
+
+1. Repeat steps 1-4 for the second resource group **myResourceGroupTM2**.
+
 
 ## Next steps