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
Copy file name to clipboardExpand all lines: articles/frontdoor/quickstart-create-front-door.md
+46-28Lines changed: 46 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,53 +30,71 @@ Sign in to the Azure portal at https://portal.azure.com.
30
30
## Prerequisites
31
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
32
33
-
1. On the top left-hand side of the screen, select **Create a resource** > **Web** > **Web App** > **Create**.
33
+
1. On the top left-hand side of the screen, select **Create a resource** > **Web** > **Web App**.
34
34
2. In **Web App**, enter or select the following information and enter default settings where none are specified:
35
35
36
36
| Setting | Value |
37
37
| --- | --- |
38
-
| Name | Enter a unique name for your web app |
39
38
| Resource group | Select **New**, and then type *myResourceGroupFD1*|
40
-
| App Service plan/Location | Select **New**. In the App Service plan, enter *myAppServicePlanEastUS*, and then select **OK**.
41
-
| Location | East US |
42
-
|||
43
-
44
-
3. Select **Create**.
45
-
4. A default website is created when the Web App is successfully deployed.
46
-
5. Repeat steps 1-3 to create a second website in a different Azure region with the following settings:
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:
47
49
48
50
| Setting | Value |
49
51
| --- | --- |
50
-
| Name | Enter a unique name for your Web App |
51
52
| Resource group | Select **New**, and then type *myResourceGroupFD2*|
52
-
| App Service plan/Location | Select **New**. In the App Service plan, enter *myAppServicePlanWestEurope*, and then select **OK**.
53
-
| Location | West Europe |
54
-
|||
55
-
56
-
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
+
57
59
## Create a Front Door for your application
58
60
### A. Add a frontend host for Front Door
59
61
Create a Front Door configuration that directs user traffic based on lowest latency between the two backends.
60
62
61
-
1. On the top left-hand side of the screen, select **Create a resource** > **Networking** > **Front Door** > **Create**.
62
-
2. In the **Create a Front Door**, you start with adding the basic info and provide a subscription where you want the Front Door to be configured. Similarly, like any other Azure resource you also need to provide a ResourceGroup and a Resource Group region if you are creating a new one. Lastly, you need to provide a name for your Front Door.
63
-
3. Once the basic info is filled in, the first step you need to define is the **frontend host** for the configuration. The result should be a valid domain name like `myappfrontend.azurefd.net`. This hostname needs to be globally unique but Front Door will take care of that validation.
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**.
64
78
65
79
### B. Add application backend and backend pools
66
80
67
-
Next, you need to configure your application backend(s) in a backend pool for Front Door to know where your application resides.
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.
68
82
69
-
1. Click the '+' icon to add a backend pool and then specify a **name** for your backend pool, say`myBackendPool`.
70
-
2. Next, click on Add Backends to add your websites created earlier.
71
-
3. Select **Target host type** as 'App Service', select the subscription in which you created the web site and then choose the first web site from the **Target host name**, that is, *myAppServicePlanEastUS.azurewebsites.net*.
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.
72
86
4. Leave the remaining fields as is for now and click **Add'**.
73
-
5. Repeat steps 2 to 4 to add the other website, that is, *myAppServicePlanWestEurope.azurewebsites.net*
74
-
6. You can optionally choose to update the Health Probes and Load-Balancing settings for the backend pool, but the default values should also work. 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**.
75
90
76
91
77
92
### C. Add a routing rule
78
-
Lastly, click the '+' icon on Routing rules 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`.
79
-
Click **Add** to add the routing rule for your Front Door. You should now be good to creating the Front Door and so click on **Review and Create**.
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**
80
98
81
99
>[!WARNING]
82
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.
@@ -89,7 +107,7 @@ If you want to test Front Door's instant global failover in action, you can go t
89
107
You can also test behavior, by disabling the backend in the backend pool configuration for your Front Door.
90
108
91
109
## Clean up resources
92
-
When no longer needed, delete the resource groups, web applications, and all related resources.
110
+
When no longer needed, delete the **myResourceGroupFD1**, **myResourceGroupFD2**, and **myResourceGroupFD0** resource groups:
93
111
94
112
## Next steps
95
-
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.
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.
0 commit comments