You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: 'Quickstart: Create Front Door profile for high availability of applications'
3
-
description: This quickstart article describes how to create a Front Door for your highly available and highperformance global web application.
2
+
title: 'Quickstart: Set up high availability with Azure Front Door Service'
3
+
description: This quickstart describes how to use Azure Front Door Service for your highly available and high-performance global web application.
4
4
services: front-door
5
5
documentationcenter: ''
6
6
author: sharad4u
@@ -11,103 +11,155 @@ ms.devlang: na
11
11
ms.topic: quickstart
12
12
ms.tgt_pltfrm: na
13
13
ms.workload: infrastructure-services
14
-
ms.date: 08/31/2018
14
+
ms.date: 04/27/2020
15
15
ms.author: sharadag
16
16
# Customer intent: As an IT admin, I want to direct user traffic to ensure high availability of web applications.
17
17
---
18
18
19
19
# Quickstart: Create a Front Door for a highly available global web application
20
20
21
-
This quickstart describes how to create a Front Door profile that delivers high availability and high performance for your global web application.
21
+
Get started with Azure Front Door by using the Azure portal to set up high availability for a web application.
22
22
23
-
The scenario described in this quickstart includes two instances of a web application running in different Azure regions. A Front Door configuration based on equal [weighted and same priority backends](front-door-routing-methods.md) is created that helps direct user traffic to the nearest set of site backends running the application. Front Door continuously monitors the web application and provides automatic failover to the next available backend when the nearest site is unavailable.
23
+
In this quickstart, Azure Front Door pools two instances of a web application that run in different Azure regions. You create a Front Door configuration based on equal weighted and same priority backends. This configuration directs traffic to the nearest site that runs the application. Azure Front Door continuously monitors the web application. The service provides automatic failover to the next available site when the nearest site is unavailable.
24
24
25
-
If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
25
+
## Prerequisites
26
26
27
-
## Sign in to Azure
28
-
Sign in to the Azure portal at https://portal.azure.com.
27
+
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
28
+
29
+
## Create two instances of a web app
30
+
31
+
This quickstart requires two instances of a web application that run in different Azure regions. Both the web application instances run in *Active/Active* mode, so either one can take traffic. This configuration differs from an *Active/Stand-By* configuration, where one acts as a failover.
32
+
33
+
If you don't already have a web app, use the following steps to set up example web apps.
34
+
35
+
1. Sign in to the Azure portal at https://portal.azure.com.
36
+
37
+
1. From the home page or the Azure menu, select **Create a resource**.
38
+
39
+
1. Select **Web** > **Web App**.
40
+
41
+
42
+
43
+
1. In **Web App**, select the **Subscription** to use.
44
+
45
+
1. For **Resource Group**, select **Create new**. Enter *FrontDoorQS_rg1* for the **Name** and select **OK**.
46
+
47
+
1. Under **Instance Details**, enter a unique **Name** for your web app. This example uses *WebAppContoso-1*.
48
+
49
+
1. Select a **Runtime stack**, in this example, *.NET Core 2.1 (LTS)*.
50
+
51
+
1. Select a region, such as *Central US*.
52
+
53
+
1. For **Windows Plan**, select **Create new**. Enter *myAppServicePlanCentralUS* for **Name** and select **OK**.
54
+
55
+
1. Be sure that the **Sku and size** is **Standard S1 100 total ACU, 1.75 GB memory**.
56
+
57
+
1. Select **Review + create**, review the **Summary**, and then select **Create**. It might take several minutes for the deployment to complete.
58
+
59
+
60
+
61
+
After your deployment is complete, create a second web app. Use the same procedure with the same values, except for the following values:
62
+
63
+
| Setting | Value |
64
+
| --- | --- |
65
+
|**Resource group**| Select **New** and enter *FrontDoorQS_rg2*|
66
+
|**Name**| Enter a unique name for your Web App, in this example, *WebAppContoso-2*|
67
+
|**Region**| A different region, in this example, *South Central US*|
68
+
|**App Service plan** > **Windows Plan**| Select **New** and enter *myAppServicePlanSouthCentralUS*, and then select **OK**|
29
69
30
-
## Prerequisites
31
-
This quickstart requires that you have deployed two instances of a web application running in different Azure regions (*East US* and *West Europe*). Both the web application instances run in Active/Active mode, that is, either of them can take traffic at any time unlike a Active/Stand-By configuration where one acts as a failover.
32
-
33
-
1. On the top left-hand side of the screen, select **Create a resource** > **Web** > **Web App**.
34
-
2. In **Web App**, enter or select the following information and enter default settings where none are specified:
35
-
36
-
| Setting | Value |
37
-
| --- | --- |
38
-
| Resource group | Select **New**, and then type *myResourceGroupFD1*|
39
-
| Name | Enter a unique name for your web app |
40
-
| Runtime stack | Select a Runtime stack for your app |
41
-
| Region | West US |
42
-
| App Service plan/Location | Select **New**. In the App Service plan, enter *myAppServicePlanEastUS*, and then select **OK**.|
43
-
|Sku and size | Select **Change Size** Select **Standard S1 100 total ACU, 1.75 GB memory**|
44
-
45
-
3. Select **Review + Create**.
46
-
4. Review the Summary information for the Web App. Select **Create**.
47
-
5. After approximately 5 minutes, a default website is created when the Web App is successfully deployed.
48
-
6. Repeat steps 1-3 to create a second website in a different Azure region with the following settings:
49
-
50
-
| Setting | Value |
51
-
| --- | --- |
52
-
| Resource group | Select **New**, and then type *myResourceGroupFD2*|
53
-
| Name | Enter a unique name for your Web App |
54
-
| Runtime stack | Select a Runtime stack for your app |
55
-
| Region | West Europe |
56
-
| App Service plan/Location | Select **New**. In the App Service plan, enter *myAppServicePlanWestEurope*, and then select **OK**.|
57
-
|Sku and size | Select **Change Size** Select **Standard S1 100 total ACU, 1.75 GB memory**|
58
-
59
70
## Create a Front Door for your application
60
-
### A. Add a frontend host for Front Door
61
-
Create a Front Door configuration that directs user traffic based on lowest latency between the two backends.
62
-
63
-
1. On the top left-hand side of the screen, select **Create a resource** > **Networking** > **Front Door**.
64
-
2. In **Create a Front Door**, enter or select the following information and enter default settings where none are specified:
65
-
66
-
| Setting | Value |
67
-
| --- | --- |
68
-
|Subscription | Select the subscription you want Front Door created in.|
69
-
| Resource group | Select **New**, and then type *myResourceGroupFD0*|
70
-
| Resource group location | Central US |
71
-
72
-
> [!NOTE]
73
-
> You do not need to create a new Resource Group to deploy Front Door into. If you can also select an existing Resource Group.
74
-
75
-
3. Click **Next: Configuration**.
76
-
4. Click the '+' icon on the Frontends/domains card. For **Host name** enter `<Your Initials>frontend`. This hostname needs to be globally unique, Front Door will take care of validation.
77
-
5. Click **Add**.
78
-
79
-
### B. Add application backend and backend pools
80
-
81
-
Next, you need to configure your Frontends/domains and application backend(s) in a backend pool for Front Door to know where your application resides.
82
-
83
-
1. Click the '+' icon on the Backend pools card to add a backend pool for **Name** for your backend pool, enter `myBackendPool`.
84
-
2. Next, click on **Add a backend** to add your websites created earlier.
85
-
3. Select **Backend host type** as 'App Service', select the subscription in which you created the web site and then choose the first web site from the **Backend host name** dropdown.
86
-
4. Leave the remaining fields as is for now and click **Add'**.
87
-
5. Select **Backend host type** as 'App Service', select the subscription in which you created the web site and then choose the **second** web site from the **Backend host name** dropdown.
88
-
6. Leave the remaining fields as is for now and click **Add'**.
89
-
7. You can optionally choose to update the Health Probes and Load-Balancing settings for the backend pool, but the default values should also work. In either case, click **Add**.
90
-
91
-
92
-
### C. Add a routing rule
93
-
1. Lastly, click the '+' icon on Routing rules card to configure a routing rule. This is needed to map your frontend host to the backend pool, which basically is configuring that if a request comes to `myappfrontend.azurefd.net`, then forward it to the backend pool `myBackendPool`.
94
-
2. For **Name** enter 'LocationRule'.
95
-
3. Click **Add** to add the routing rule for your Front Door.
96
-
4. Click on **Review and Create**.
97
-
5. Review the settings for the Front Door creation. Click **Create**
98
-
99
-
>[!WARNING]
100
-
> You **must** ensure that each of the frontend hosts in your Front Door has a routing rule with a default path ('/\*') associated with it. That is, across all of your routing rules there must be at least one routing rule for each of your frontend hosts defined at the default path ('/\*'). Failing to do so, may result in your end-user traffic not getting routed correctly.
101
-
102
-
## View Front Door in action
103
-
Once you create a Front Door, it will take a few minutes for the configuration to be deployed globally everywhere. Once complete, access the frontend host you created, that is, go to a web browser and hit the URL `myappfrontend.azurefd.net`. Your request will automatically get routed to the nearest backend to you from the specified backends in the backend pool.
104
-
105
-
### View Front Door handle application failover
106
-
If you want to test Front Door's instant global failover in action, you can go to one of the web sites you created and stop it. Based on the Health Probe setting defined for the backend pool, we will instantly fail over the traffic to the other web site deployment.
107
-
You can also test behavior, by disabling the backend in the backend pool configuration for your Front Door.
71
+
72
+
Configure Azure Front Door to direct user traffic based on lowest latency between the two web apps servers. To begin, add a frontend host for Azure Front Door.
73
+
74
+
1. From the home page or the Azure menu, select **Create a resource**. Select **Networking** > **Front Door**.
75
+
76
+
1. In **Create a Front Door**, select a **Subscription**.
77
+
78
+
1. For **Resource group**, select **New**, then enter *FrontDoorQS_rg0* and select **OK**. You can use an existing resource group instead.
79
+
80
+
1. If you created a resource group, select a **Resource group location**, and then select **Next: Configuration**.
81
+
82
+
1. In **Frontends/domains**, select **+** to open **Add a frontend host**.
83
+
84
+
1. For **Host name**, enter a globally unique hostname. This example uses *contoso-frontend*. Select **Add**.
85
+
86
+
87
+
88
+
Next, create a backend pool that contains your two web apps.
89
+
90
+
1. Still in **Create a Front Door**, in **Backend pools**, select **+** to open **Add a backend pool**.
91
+
92
+
1. For **Name**, enter *myBackendPool*.
93
+
94
+
1. Select **Add a backend**. For **Backend host type**, select *App Service*.
95
+
96
+
1. Select your subscription, and then choose the first web app you created from **Backend host name**. In this example, the web app was *WebAppContoso-1*. Select **Add**.
97
+
98
+
1. Select **Add a backend** again. For **Backend host type**, select *App Service*.
99
+
100
+
1. Select your subscription, again, and choose the second web app you created from **Backend host name**. Select **Add**.
101
+
102
+
103
+
104
+
Finally, add a routing rule. A routing rule maps your frontend host to the backend pool. The rule forwards a request for `contoso-frontend.azurefd.net` to **myBackendPool**.
105
+
106
+
1. Still in **Create a Front Door**, in **Routing rules**, select **+** to configure a routing rule.
107
+
108
+
1. In **Add a rule**, for **Name**, enter *LocationRule*. Accept all the default values, then select **Add** to add the routing rule.
109
+
110
+
>[!WARNING]
111
+
> You **must** ensure that each of the frontend hosts in your Front Door has a routing rule with a default path (`\*`) associated with it. That is, across all of your routing rules there must be at least one routing rule for each of your frontend hosts defined at the default path (`\*`). Failing to do so may result in your end-user traffic not getting routed correctly.
112
+
113
+
1. Select **Review + Create**, and then **Create**.
114
+
115
+
116
+
117
+
## View Azure Front Door in action
118
+
119
+
Once you create a Front Door, it takes a few minutes for the configuration to be deployed globally. Once complete, access the frontend host you created. In a browser, go to `contoso-frontend.azurefd.net`. Your request will automatically get routed to the nearest server to you from the specified servers in the backend pool.
120
+
121
+
If you created these apps in this quickstart, you'll see an information page.
122
+
123
+
To test instant global failover in action, try the following steps:
124
+
125
+
1. Open a browser, as described above, and go to the frontend address: `contoso-frontend.azurefd.net`.
126
+
127
+
1. In the Azure portal, search for and select *App services*. Scroll down to find one of your web apps, **WebAppContoso-1** in this example.
128
+
129
+
1. Select your web app, and then select **Stop**, and **Yes** to verify.
130
+
131
+
1. Refresh your browser. You should see the same information page.
132
+
133
+
>[!TIP]
134
+
>There is a little bit of delay for these actions. You might need to refresh again.
135
+
136
+
1. Find the other web app, and stop it as well.
137
+
138
+
1. Refresh your browser. This time, you should see an error message.
139
+
140
+
108
141
109
142
## Clean up resources
110
-
When no longer needed, delete the **myResourceGroupFD1**, **myResourceGroupFD2**, and **myResourceGroupFD0** resource groups:
143
+
144
+
After you're done, you can remove all the items you created. Deleting a resource group also deletes its contents. If you don't intend to use this Front Door, you should remove resources to avoid unnecessary charges.
145
+
146
+
1. In the Azure portal, search for and select **Resource groups**, or select **Resource groups** from the Azure portal menu.
147
+
148
+
1. Filter or scroll down to find a resource group, such as **FrontDoorQS_rg0**.
149
+
150
+
1. Select the resource group, then select **Delete resource group**.
151
+
152
+
>[!WARNING]
153
+
>This action is irreversable.
154
+
155
+
1. Type the resource group name to verify, and then select **Delete**.
156
+
157
+
Repeat the procedure for the other two groups.
111
158
112
159
## Next steps
113
-
In this quickstart, you created a Front Door that allows you to direct user traffic for web applications that require high availability and maximum performance. To learn more about routing traffic, read the [Routing Methods](front-door-routing-methods.md) used by Front Door.
160
+
161
+
Advance to the next article to learn how to add a custom domain to your Front Door.
162
+
> [!div class="nextstepaction"]
163
+
> [Add a custom domain](front-door-custom-domain.md)
164
+
165
+
To learn more about routing traffic, see [Front Door routing methods](front-door-routing-methods.md).
0 commit comments