From 27c38bb1bcc19d8861d0a74ce6f725341b4c525c Mon Sep 17 00:00:00 2001 From: Tom Plant Date: Tue, 14 Apr 2026 20:16:12 +1000 Subject: [PATCH] Azure Front Door supports managed certificates for wildcard domains See https://azure.microsoft.com/en-us/updates?id=496631 --- articles/frontdoor/domain.md | 1 - 1 file changed, 1 deletion(-) diff --git a/articles/frontdoor/domain.md b/articles/frontdoor/domain.md index dbd59ff3231b2..6c2b83f3ff2a0 100644 --- a/articles/frontdoor/domain.md +++ b/articles/frontdoor/domain.md @@ -124,7 +124,6 @@ Sometimes, you might need to provide your own TLS certificates. Common scenarios * You want Azure Key Vault to issue your certificate by using a partner certification authority. * You need to use a TLS certificate that a client application recognizes. * You need to use the same TLS certificate on multiple systems. -* You use [wildcard domains](front-door-wildcard-domain.md). Azure Front Door doesn't provide managed certificates for wildcard domains. > [!NOTE] > * As of September 2023, Azure Front Door supports Bring Your Own Certificates (BYOC) for domain ownership validation. Front Door approves the domain ownership if the Certificate Name (CN) or Subject Alternative Name (SAN) of the certificate matches the custom domain. If you select Azure managed certificate, the domain validation uses the DNS TXT record.