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
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
19
20
-
Azure Front Door supports both Azure managed certificate and customer-managed certificates. 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 Azure managed certificate. A certificate is created during the domain validation process. You can also use your own certificate by integrating Azure Front Door Standard/Premium with your Key Vault.
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).
23
+
* For both scenarios, you can bring your own certificate.
21
24
22
25
## Prerequisites
23
26
@@ -27,19 +30,36 @@ Azure Front Door supports both Azure managed certificate and customer-managed ce
27
30
28
31
* If you're using Azure to host your [DNS domains](../../dns/dns-overview.md), you must delegate the domain provider's domain name system (DNS) to an Azure DNS. For more information, see [Delegate a domain to Azure DNS](../../dns/dns-delegate-domain-azure-dns.md). Otherwise, if you're using a domain provider to handle your DNS domain, you must manually validate the domain by entering prompted DNS TXT records.
29
32
30
-
## Azure managed certificates
33
+
## AFD managed certificates for Non-Azure pre-validated domain
31
34
32
35
1. Select **Domains** under settings for your Azure Front Door profile and then select **+ Add** to add a new domain.
33
36
34
37
:::image type="content" source="../media/how-to-configure-https-custom-domain/add-new-custom-domain.png" alt-text="Screenshot of domain configuration landing page.":::
35
38
36
-
1. On the **Add a domain** page, for *DNS management* select the **Azure managed DNS** option.
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.
37
41
38
42
:::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.":::
39
43
40
44
1. Validate and associate the custom domain to an endpoint by following the steps in enabling [custom domain](how-to-add-custom-domain.md).
41
45
42
-
1. Once the custom domain gets associated to endpoint successfully, an Azure managed certificate gets deployed to Front Door. This process may take from several minutes to an hour to complete.
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.
47
+
48
+
## Azure managed certificates for Azure pre-validated domain
49
+
50
+
1. Select **Domains** under settings for your Azure Front Door profile and then select **+ Add** to add a new domain.
51
+
52
+
:::image type="content" source="../media/how-to-configure-https-custom-domain/add-new-custom-domain.png" alt-text="Screenshot of domain configuration landing page.":::
53
+
54
+
1. On the **Add a domain** page, for *DNS type* select the **Azure pre-validated domain** option.
55
+
56
+
1. For *Pre-validated custom domains* select the pre-validated domain from the dropdown list.
57
+
58
+
1. For HTTPS select **Azure managed**.
59
+
60
+
1. Validate and associate the custom domain to an endpoint by following the steps in enabling [custom domain](how-to-add-custom-domain.md).
61
+
62
+
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.
43
63
44
64
## Using your own certificate
45
65
@@ -143,9 +163,9 @@ Azure Front Door can now access this key vault and the certificates it contains.
143
163
144
164
## Certificate renewal and changing certificate types
145
165
146
-
### Azure-managed certificate
166
+
### AFD managed certificate for Non-Azure pre-validated domain
147
167
148
-
Azure-managed certificates are automatically rotated when your custom domain uses a CNAME record that points to an Azure Front Door standard or premium endpoint.
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.
149
169
150
170
Front Door won't automatically rotate certificates in the following scenarios:
151
171
@@ -154,6 +174,10 @@ Front Door won't automatically rotate certificates in the following scenarios:
154
174
155
175
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.
156
176
177
+
### Azure managed certificate for Azure pre-validated domain
178
+
179
+
Azure managed certifiate is automatically rotated by the other Azure service.
180
+
157
181
### <a name="rotate-own-certificate"></a>Use your own certificate
158
182
159
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.
0 commit comments