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: powerapps-docs/maker/portals/azure-front-door.md
+9-10Lines changed: 9 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: dileepsinghmicrosoft
5
5
6
6
ms.topic: conceptual
7
7
ms.custom:
8
-
ms.date: 09/13/2021
8
+
ms.date: 03/28/2022
9
9
ms.author: dileeps
10
10
ms.reviewer: ndoelman
11
11
contributors:
@@ -15,11 +15,10 @@ contributors:
15
15
16
16
# Set up Azure Front Door with portals
17
17
18
-
As a portal maker, you can use Azure Front Door with Power Apps portals to use its edge caching and Web Application Firewall (WAF) capabilities. In this article, you'll learn how to set up [Azure Front Door Standard/Premium (preview)](/azure/frontdoor/standard-premium/overview) with portals.
18
+
As a portal maker, you can use Azure Front Door with Power Apps portals to use its edge caching and web application firewall (WAF) capabilities. In this article, you'll learn how to set up [Azure Front Door](/azure/frontdoor/overview) with portals.
19
19
20
20
> [!NOTE]
21
-
> - Since Azure Front Door Standard/Premium (preview) is in preview, ensure you follow the preview guidelines as outlined in [Azure documentation](/azure/frontdoor/standard-premium/overview).
22
-
> - Although this article is focused on [Azure Front Door Standard/Premium (preview)](/azure/frontdoor/standard-premium/overview), similar steps can be used for [Azure Front Door](/azure/frontdoor/front-door-overview) or any other content delivery network or WAF provider. The terminology used by various components might be different.
21
+
> - Although this article is focused on [Azure Front Door](/azure/frontdoor/overview), similar steps can be used for any other content delivery network or WAF provider. The terminology used by various components might be different.
23
22
> - While [custom ___domain HTTPS settings using Azure portal](/azure/frontdoor/front-door-faq#can-i-configure-tls-policy-to-control-tls-protocol-versions-) allows you to choose a [default minimum](/azure/frontdoor/front-door-faq#what-tls-versions-are-supported-by-azure-front-door-) TLS version between 1.0 and 1.2, use TLS version 1.2 for strong ciphers.
24
23
25
24
Follow these steps to set up Azure Front Door with portals:
@@ -49,7 +48,7 @@ In this section, you'll learn how to set up the Azure Front Door service and ena
49
48
> [!NOTE]
50
49
> If you've already created the Azure Front Door resource, go to step 3 of the following procedure.
51
50
52
-
1. Sign in to the [Azure portal](https://portal.azure.com), and create a new Azure Front Door (Standard or Premium) resource. More information: [Quickstart: Create an Azure Front Door Standard/Premium profile - Azure portal](/azure/frontdoor/standard-premium/create-front-door-portal)
51
+
1. Sign in to the [Azure portal](https://portal.azure.com), and create a new Azure Front Door (Standard or Premium) resource. More information: [Quickstart: Create an Azure Front Door Standard/Premium profile - Azure portal](/azure/frontdoor/create-front-door-portal)
53
52
54
53

55
54
@@ -102,7 +101,7 @@ Web browsers reject cookies set by Power Apps portals when you use an Azure Fron
102
101
103
102
1. Update your DNS provider by removing the CNAME record created earlier during the custom ___domain setup for portals. Only CNAME should be updated; don't remove the origin host name. DNS will point CNAME to the Azure Front Door endpoint. The only purpose for adding CNAME was to ensure that the custom host name will be present on portals. This presence ensures that portals can serve traffic to this custom ___domain name through Azure Front Door, and all portal cookies will also have the ___domain set up correctly.
104
103
105
-
1. Set up the custom ___domain name on the Azure Front Door endpoint by following these steps: [Create a custom ___domain on Azure Front Door Standard/Premium SKU (preview) using the Azure portal](/azure/frontdoor/standard-premium/how-to-add-custom-___domain).
104
+
1. Set up the custom ___domain name on the Azure Front Door endpoint by following these steps: [Create a custom ___domain on Azure Front Door Standard/Premium SKU using the Azure portal](/azure/frontdoor/standard-premium/how-to-add-custom-___domain).
106
105
107
106
1. Check the following to validate the setup:
108
107
@@ -373,8 +372,8 @@ By default, Azure Front Door has an origin response timeout of 60 seconds. Howev
373
372
374
373
### See also
375
374
376
-
[What is Azure Front Door?](/azure/frontdoor/standard-premium/overview) <br>
377
-
[Quickstart: Create an Azure Front Door Standard/Premium profile - Azure portal](/azure/frontdoor/standard-premium/create-front-door-portal) <br>
378
-
[Create a custom ___domain on Azure Front Door Standard/Premium SKU (preview) using the Azure portal](/azure/frontdoor/standard-premium/how-to-add-custom-___domain) <br>
375
+
[What is Azure Front Door?](/azure/frontdoor/overview) <br>
376
+
[Quickstart: Create an Azure Front Door profile - Azure portal](/azure/frontdoor/create-front-door-portal) <br>
377
+
[Create a custom ___domain on Azure Front Door Standard/Premium SKU using the Azure portal](/azure/frontdoor/standard-premium/how-to-add-custom-___domain) <br>
379
378
[How do I lock down the access to my back end to only Azure Front Door?](/azure/frontdoor/front-door-faq#how-do-i-lock-down-the-access-to-my-backend-to-only-azure-front-door-) <br>
380
-
[Azure Front Door Rules Engine match conditions](/azure/frontdoor/front-door-rules-engine-match-conditions) <br>
379
+
[Azure Front Door Rules Engine match conditions](/azure/frontdoor/front-door-rules-engine-match-conditions) <br>
0 commit comments