Skip to content

Commit 2964c85

Browse files
committed
updated date and steps for freshness.
1 parent d7cdb0a commit 2964c85

File tree

1 file changed

+17
-6
lines changed

1 file changed

+17
-6
lines changed

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

Lines changed: 17 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: traffic-manager
55
author: asudbring
66
ms.author: allensu
77
manager: twooley
8-
ms.date: 04/19/2021
8+
ms.date: 07/18/2022
99
ms.topic: quickstart
1010
ms.service: traffic-manager
1111
ms.workload: infrastructure-services
@@ -40,13 +40,13 @@ For this quickstart, you'll need two instances of a web application deployed in
4040
| Resource group | Select **Create new** and enter *myResourceGroupTM1* in the text box.|
4141
| Name | Enter a unique **Name** for your web app. This example uses *myWebAppEastUS*. |
4242
| Publish | Select **Code**. |
43-
| Runtime stack | Select **ASP.NET V4.7**. |
43+
| Runtime stack | Select **ASP.NET V4.8**. |
4444
| Operating System | Select **Windows**. |
4545
| Region | Select **East US**. |
4646
| Windows Plan | Select **Create new** and enter *myAppServicePlanEastUS* in the text box. |
4747
| Sku and size | Select **Standard S1 100 total ACU, 1.75-GB memory**. |
4848

49-
1. Select the **Monitoring** tab, or select **Next: Monitoring**. Under **Monitoring**, set **Application Insights** > **Enable Application Insights** to **No**.
49+
1. Select the **Monitoring** tab, or select **Next** to the **Monitoring** tab. Under **Monitoring**, set **Application Insights > Enable Application Insights** to **No**.
5050

5151
1. Select **Review and create**.
5252

@@ -93,7 +93,7 @@ Add the website in the *East US* as primary endpoint to route all the user traff
9393

9494
:::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.":::
9595

96-
1. Select **OK**.
96+
1. Select **Add**.
9797
1. To create a failover endpoint for your second Azure region, repeat steps 3 and 4 with these settings:
9898

9999
| Setting | Value |
@@ -104,7 +104,7 @@ Add the website in the *East US* as primary endpoint to route all the user traff
104104
| Target resource | Select **Choose an app service** > **West Europe**. |
105105
| Priority | Select **2**. All traffic goes to this failover endpoint if the primary endpoint is unhealthy. |
106106

107-
1. Select **OK**.
107+
1. Select **Add**.
108108

109109
When you're done adding the two endpoints, they're displayed in **Traffic Manager profile**. Notice that their monitoring status is **Online** now.
110110

@@ -140,7 +140,18 @@ The primary endpoint isn't available, so you were routed to the failover endpoin
140140

141141
## Clean up resources
142142

143-
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.
143+
When you're done using the private link service, delete the resource group to clean up the resources used in this quickstart.
144+
145+
1. Enter **myResourceGroupTM1** in the search box at the top of the portal, and select **myResourceGroupTM1** from the search results.
146+
147+
1. Select **Delete resource group**.
148+
149+
1. In **TYPE THE RESOURCE GROUP NAME**, enter **myResourceGroupTM1**.
150+
151+
1. Select **Delete**.
152+
153+
1. Repeat steps 1-4 for the second resource group **myResourceGroupTM2**.
154+
144155

145156
## Next steps
146157

0 commit comments

Comments
 (0)