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/standard-premium/how-to-add-custom-domain.md
+13-4Lines changed: 13 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: duongau
7
7
ms.service: frontdoor
8
8
ms.topic: how-to
9
9
ms.workload: infrastructure-services
10
-
ms.date: 03/18/2022
10
+
ms.date: 09/06/2022
11
11
ms.author: duau
12
12
#Customer intent: As a website owner, I want to add a custom domain to my Front Door configuration so that my users can use my custom domain to access my content.
13
13
---
@@ -37,18 +37,24 @@ A custom domain is managed by Domains section in the portal. A custom domain can
37
37
38
38
:::image type="content" source="../media/how-to-add-custom-domain/add-domain-button.png" alt-text="Screenshot of add domain button on domain landing page.":::
39
39
40
-
1. The **Add a domain** page will appear where you can enter information about of the custom domain. You can choose Azure-managed DNS, which is recommended or you can choose to use your own DNS provider. If you choose Azure-managed DNS, select an existing DNS zone and then select a custom subdomain or create a new one. If you're using another DNS provider, manually enter the custom domain name. Select **Add** to add your custom domain.
40
+
1. The **Add a domain** page will appear where you can enter information about of the custom domain. You can choose **Non-Azure validated domain** or **Azure pre-validated domain**.
41
+
***Azure pre-validated domain** are domains validated by another Azure service. When you select this option, there is no need to valiate domain ownership on Azure Front Door. A dropdown list of the domains validated and grouped by the supported Azure services are populated.
42
+
***Non-Azure validated domain** need domain ownership validation. When you select Non-Azure validated domain, Azure-managed DNS is recommended or you can choose to use your own DNS provider. If you choose Azure-managed DNS, select an existing DNS zone and then select a custom subdomain or create a new one. If you're using another DNS provider, manually enter the custom domain name. Select **Add** to add your custom domain.
41
43
42
44
> [!NOTE]
43
-
> Azure Front Door supports both Azure managed certificate and customer-managed certificates. If you want to use customer-managed certificate, see [Configure HTTPS on a custom domain](how-to-configure-https-custom-domain.md).
44
-
45
+
> * Azure Front Door supports both Azure managed certificate and customer-managed certificates. For Non-Azure validated domain, the managed certificate is issued and managed by Azure Front Door. For Azure pre-validated domain, the managed certificate (Azure managed) is issued and managed by the other Azure service. For both scenarios, you can bring your own certificate. If you want to use customer-managed certificate, see [Configure HTTPS on a custom domain](how-to-configure-https-custom-domain.md).
46
+
> * Azure Front Door supports loading Azure pre-validated domains and Azure DNS zones cross subscriptions on portal.
47
+
> * Currently Azure pre-validated domain supports domain validated by Static Web App.
48
+
45
49
:::image type="content" source="../media/how-to-add-custom-domain/add-domain-page.png" alt-text="Screenshot of add a domain page.":::
46
50
47
51
A new custom domain is created with a validation state of **Submitting**.
48
52
49
53
:::image type="content" source="../media/how-to-add-custom-domain/validation-state-submitting.png" alt-text="Screenshot of domain validation state submitting.":::
50
54
51
55
Wait until the validation state changes to **Pending**. This operation could take a few minutes.
56
+
> [!NOTE]
57
+
> The validation state for Azure pre-validated domain goes into **Approved**. Please skip to Associate the custom domain with your Front Door Endpoint directly and complete the remaining steps.
52
58
53
59
:::image type="content" source="../media/how-to-add-custom-domain/validation-state-pending.png" alt-text="Screenshot of domain validation state pending.":::
54
60
@@ -97,6 +103,9 @@ After you've validated your custom domain, you can then add it to your Azure Fro
97
103
1. The **Add or update the CNAME record** page will appear and display the CNAME record information that must be provided before traffic can start flowing. If you're using Azure DNS hosted zones, the CNAME records can be created by selecting the **Add** button on the page. If you're using another DNS provider, you must manually enter the CNAME record name and value as shown on the page.
98
104
99
105
:::image type="content" source="../media/how-to-add-custom-domain/add-update-cname-record.png" alt-text="Screenshot of add or update CNAME record.":::
106
+
107
+
> [!NOTE]
108
+
> For Azure pre-validated domain, please go to the DNS hosting service and manually change the CNAME record for this domain from the other Azure service endpoint to Azure Front Door endpoint, regardless of whether the domain is hosted on Azure DNS or other DNS services. The DNS state column on Azure Front Door domain blade is non-editable or clickable.
100
109
101
110
1. Once the CNAME record gets created and the custom domain is associated to the Azure Front Door endpoint completes, traffic flow will start flowing.
0 commit comments