Skip to content

Commit 883c8bd

Browse files
committed
update with pre-validated information
1 parent 525b32d commit 883c8bd

File tree

3 files changed

+30
-16
lines changed

3 files changed

+30
-16
lines changed
6.9 KB
Loading
44.5 KB
Loading

articles/frontdoor/standard-premium/how-to-configure-https-custom-domain.md

Lines changed: 30 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,22 @@ ms.service: frontdoor
77
ms.topic: article
88
ms.workload: infrastructure-services
99
ms.date: 06/06/2022
10-
ms.author: amsriva
10+
ms.author: duau
1111
ms.custom: devx-track-azurepowershell
1212
#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.
1313
---
1414

1515
# Configure HTTPS on an Azure Front Door custom domain using the Azure portal
1616

1717

18-
Azure Front Door enables secure TLS delivery to your applications by default when a custom domain is added. By using the HTTPS protocol on your custom domain, you ensure your sensitive data get delivered securely with TLS/SSL encryption when it's sent across the internet. When your web browser is connected to a web site via HTTPS, it validates the web site's security certificate and verifies it gets issued by a legitimate certificate authority. This process provides security and protects your web applications from attacks.
18+
Azure Front Door enables secure TLS delivery to your applications by default when a custom domain is added. By using the HTTPS protocol on your custom domain, you ensure your sensitive data get delivered securely with TLS/SSL encryption when it's sent across the internet. When your web browser is connected to a web site via HTTPS, it validates the web site's security certificate, and verifies it gets issued by a legitimate certificate authority. This process provides security and protects your web applications from attacks.
19+
20+
Azure Front Door supports Azure managed certificate and customer-managed certificates.
21+
22+
* A non-Azure validated domain requires domain ownership validation. The managed certificate (AFD managed) is issued and managed by Azure Front Door. Azure Front Door by default automatically enables HTTPS to all your custom domains using Azure managed certificates. No extra steps are required for getting an AFD managed certificate. A certificate is created during the domain validation process.
23+
24+
* An Azure pre-validated domain doesn't require domain validation because it's already validated by another Azure service. The managed certificate (Azure managed) is issued and managed by the Azure service. No extra steps are required for getting an Azure managed certificate. Azure Front Door doesn't issue a new managed certificate for this scenario and instead will reuse the managed certificate issued by the Azure service. For supported Azure service for pre-validated domain, refer to [custom domain](how-to-add-custom-domain.md).
1925

20-
Azure Front Door supports both Azure managed certificate and customer-managed certificates.
21-
* Non-Azure validated domain requires domain ownership validation. The managed certificate (AFD managed) is issued and managed by Azure Front Door. Azure Front Door by default automatically enables HTTPS to all your custom domains using Azure managed certificates. No extra steps are required for getting an AFD managed certificate. A certificate is created during the domain validation process.
22-
* Azure pre-validated domain doesn't require domain validation because it is already validated by another Azure service. The managed certificate (Azure managed) is issued and managed by the other Azure service. No extra steps are required for getting an Azure managed certificate. Azure Front Door doesn't issue managed certificate for this scenario and reuse the managed certificat issued by the other Azure service. For supported Azure service for pre-validated domain, please refer to [custom domain](how-to-add-custom-domain.md).
2326
* For both scenarios, you can bring your own certificate.
2427

2528
## Prerequisites
@@ -36,26 +39,37 @@ Azure Front Door supports both Azure managed certificate and customer-managed ce
3639

3740
:::image type="content" source="../media/how-to-configure-https-custom-domain/add-new-custom-domain.png" alt-text="Screenshot of domain configuration landing page.":::
3841

39-
1. On the **Add a domain** page, for *DNS type* select the **Non-Azure pre-validated domain** option.
40-
1. For *DNS management* select the **Azure managed DNS** option.
42+
1. On the **Add a domain** page, enter or select the following information, then select **Add** to onboard the custom domain.
4143

4244
:::image type="content" source="../media/how-to-configure-https-custom-domain/add-domain-azure-managed.png" alt-text="Screen shot of add a domain page with Azure managed DNS selected.":::
4345

46+
| Setting | Value |
47+
|--|--|
48+
| Domain type | Select **Non-Azure pre-validated domain** |
49+
| DNS management | Select **Azure managed DNS (Recommended)** |
50+
| DNS zone | Select the **Azure DNS zone** that host the custom domain. |
51+
| Custom domain | Select an existing domain or add a new domain. |
52+
| HTTPS | Select **AFD managed (Recommended)** |
53+
4454
1. Validate and associate the custom domain to an endpoint by following the steps in enabling [custom domain](how-to-add-custom-domain.md).
4555

46-
1. Once the custom domain gets associated to endpoint successfully, an AFD managed certificate gets deployed to Front Door. This process may take from several minutes to an hour to complete.
56+
1. Once the custom domain gets associated to an endpoint successfully, an AFD managed certificate gets deployed to Front Door. This process may take from several minutes to an hour to complete.
4757

4858
## Azure managed certificates for Azure pre-validated domain
4959

5060
1. Select **Domains** under settings for your Azure Front Door profile and then select **+ Add** to add a new domain.
5161

5262
:::image type="content" source="../media/how-to-configure-https-custom-domain/add-new-custom-domain.png" alt-text="Screenshot of domain configuration landing page.":::
5363

54-
1. On the **Add a domain** page, for *DNS type* select the **Azure pre-validated domain** option.
64+
1. On the **Add a domain** page, enter or select the following information, then select **Add** to onboard the custom domain.
5565

56-
1. For *Pre-validated custom domains* select the pre-validated domain from the dropdown list.
66+
:::image type="content" source="../media/how-to-configure-https-custom-domain/add-pre-validated-domain.png" alt-text="Screen shot of add a domain page with pre-validated domain.":::
5767

58-
1. For HTTPS select **Azure managed**.
68+
| Setting | Value |
69+
|--|--|
70+
| Domain type | Select **Azure pre-validated domain** |
71+
| Pre-validated custom domain | Select a custom domain name from the drop-down list of Azure services. |
72+
| HTTPS | Select **Azure managed (Recommended)** |
5973

6074
1. Validate and associate the custom domain to an endpoint by following the steps in enabling [custom domain](how-to-add-custom-domain.md).
6175

@@ -165,22 +179,22 @@ Azure Front Door can now access this key vault and the certificates it contains.
165179
166180
### AFD managed certificate for Non-Azure pre-validated domain
167181
168-
AFD managed certificates are automatically rotated when your custom domain uses a CNAME record that points to an Azure Front Door standard or premium endpoint.
182+
AFD managed certificates are automatically rotated when your custom domain uses a CNAME record that points to an Azure Front Door Standard or Premium endpoint.
169183
170184
Front Door won't automatically rotate certificates in the following scenarios:
171185
172-
* The custom domain's CNAME record is pointing to other DNS resources.
173-
* The custom domain points to Azure Front Door through a long chain. For example, if you put Azure Traffic Manager before Azure Front Door, the CNAME chain is `contoso.com` CNAME in `contoso.trafficmanager.net` CNAME in `contoso.z01.azurefd.net`.
186+
* The custom domain CNAME record is pointing to other DNS resources.
187+
* The custom domain points to the Azure Front Door through a long chain. For example, if you put Azure Traffic Manager before Azure Front Door, the CNAME chain is `contoso.com` CNAME in `contoso.trafficmanager.net` CNAME in `contoso.z01.azurefd.net`.
174188
175189
The domain validation state will become *Pending Revalidation* 45 days before the managed certificate expires, or *Rejected* if the managed certificate issuance is rejected by the certificate authority. Refer to [Add a custom domain](how-to-add-custom-domain.md#domain-validation-state) for actions for each of the domain states.
176190
177191
### Azure managed certificate for Azure pre-validated domain
178192
179-
Azure managed certifiate is automatically rotated by the other Azure service.
193+
Azure managed certificates are automatically rotated by the Azure service that validates the domain.
180194
181195
### <a name="rotate-own-certificate"></a>Use your own certificate
182196
183-
In order for the certificate to be automatically rotated to the latest version when a newer version of the certificate is available in your key vault, set the secret version to 'Latest'. If a specific version is selected, you have to reselect the new version manually for certificate rotation. It takes up to 24 hours for the new version of the certificate/secret to be automatically deployed.
197+
In order for the certificate to automatically be rotated to the latest version when a newer version of the certificate is available in your key vault, set the secret version to 'Latest'. If a specific version is selected, you have to reselect the new version manually for certificate rotation. It takes up to 24 hours for the new version of the certificate/secret to be automatically deployed.
184198
185199
If you want to change the secret version from ‘Latest’ to a specified version or vice versa, add a new certificate.
186200

0 commit comments

Comments
 (0)