Azure Front Door supports managed certificates for wildcard domains#128407
Azure Front Door supports managed certificates for wildcard domains#128407pl4nty wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
|
@pl4nty : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 27c38bb: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates Azure Front Door documentation to reflect that managed certificates are now supported for wildcard domains.
Changes:
- Removes the statement claiming Azure Front Door doesn’t provide managed certificates for wildcard domains.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * 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. |
There was a problem hiding this comment.
The PR removes the statement that managed certs aren’t supported for wildcard domains, but the surrounding section still only lists scenarios for bringing your own cert. To align with the PR purpose, consider adding an explicit note in this section that Azure managed certificates can be used with wildcard domains (and, if applicable, any constraints such as supported wildcard level or DNS validation requirements), so readers don’t infer BYOC is still required for wildcard domains.
| > * 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. | |
| > * Azure managed certificates can be used with wildcard custom domains. When you select an Azure managed certificate, domain validation uses the DNS TXT record. | |
| > * 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. |
|
Hey @duongau, not sure if you are a better person to review this (and also take over the doc)? |
|
Hi @johndowns, I've already shared it with a PM last week, waiting on their response. |
See https://azure.microsoft.com/en-us/updates?id=496631