Skip to content

Commit f634f69

Browse files
Merge pull request #230174 from johndowns/front-door-managed-tls-issuance
Front Door - Add information about managed TLS certificates
2 parents 6d4b4c4 + 767d0a2 commit f634f69

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

articles/frontdoor/domain.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: johndowns
66
ms.service: frontdoor
77
ms.topic: conceptual
88
ms.workload: infrastructure-services
9-
ms.date: 03/06/2023
9+
ms.date: 03/10/2023
1010
ms.author: jodowns
1111
---
1212

@@ -93,8 +93,6 @@ For more information on how Azure Front Door works with TLS, see [End-to-end TLS
9393

9494
Azure Front Door can automatically manage TLS certificates for subdomains and apex domains. When you use managed certificates, you don't need to create keys or certificate signing requests, and you don't need to upload, store, or install the certificates. Additionally, Azure Front Door can automatically rotate (renew) managed certificates without any human intervention. This process avoids downtime caused by a failure to renew your TLS certificates in time.
9595

96-
Azure Front Door's certificates are issued by our partner certification authority, DigiCert.
97-
9896
The process of generating, issuing, and installing a managed TLS certificate can take from several minutes to an hour to complete, and occasionally it can take longer.
9997

10098
#### Domain types
@@ -108,6 +106,12 @@ The following table summarizes the features available with managed TLS certifica
108106

109107
When you use Azure Front Door-managed TLS certificates with apex domains, the automated certificate rotation might require you to revalidate your domain ownership. For more information, see [Apex domains in Azure Front Door](apex-domain.md#azure-front-door-managed-tls-certificate-rotation).
110108

109+
#### Managed certificate issuance
110+
111+
Azure Front Door's certificates are issued by our partner certification authority, DigiCert. For some domains, you must explicitly allow DigiCert as a certificate issuer by creating a [CAA domain record](https://wikipedia.org/wiki/DNS_Certification_Authority_Authorization) with the value: `0 issue digicert.com`.
112+
113+
Azure fully manages the certificates on your behalf, so any aspect of the managed certificate, including the root issuer, can change at any time. These changes are outside your control. Make sure to avoid hard dependencies on any aspect of a managed certificate, such as checking the certificate thumbprint, or pinning to the managed certificate or any part of the certificate hierarchy. If you need to pin certificates, you should use a customer-managed TLS certificate, as explained in the next section.
114+
111115
### Customer-managed TLS certificates
112116

113117
Sometimes, you might need to provide your own TLS certificates. Common scenarios for providing your own certificates include:

0 commit comments

Comments
 (0)