Skip to content

Azure Front Door supports managed certificates for wildcard domains#128407

Open
pl4nty wants to merge 1 commit intoMicrosoftDocs:mainfrom
pl4nty:patch-1
Open

Azure Front Door supports managed certificates for wildcard domains#128407
pl4nty wants to merge 1 commit intoMicrosoftDocs:mainfrom
pl4nty:patch-1

Conversation

@pl4nty
Copy link
Copy Markdown
Contributor

@pl4nty pl4nty commented Apr 14, 2026

@prmerger-automator
Copy link
Copy Markdown
Contributor

@pl4nty : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 27c38bb:

✅ Validation status: passed

File Status Preview URL Details
articles/frontdoor/domain.md ✅Succeeded

For more details, please refer to the build report.

@ttorble ttorble requested a review from Copilot April 14, 2026 13:58
@ttorble
Copy link
Copy Markdown
Contributor

ttorble commented Apr 14, 2026

@johndowns

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged tracking label for the PR review team label Apr 14, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
> * 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.

Copilot uses AI. Check for mistakes.
@johndowns
Copy link
Copy Markdown
Contributor

Hey @duongau, not sure if you are a better person to review this (and also take over the doc)?

@halkazwini
Copy link
Copy Markdown
Contributor

Hi @johndowns, I've already shared it with a PM last week, waiting on their response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants