Front Door Configuration Issue

Question

We have configured Azure Front Door with domain www.risenfame.com (screenshot attached)

www.risenfame.com is NOT accessible after completing setup successfully.

Endpoint https://rf-gufpf4a4d0euece2.z01.azurefd.net/ is also NOT accessible.
(screenshot attached)

While root domain is accessible.
https://risenfame.com/ is accessible

Answer 1

Hi Juan,

Thanks for reaching out In Microsoft Q&A forum,

Endpoint https://rf-gufpf4a4d0euece2.z01.azurefd.net/ is also NOT accessible.

The "Page not found" error on [www.risenfame.com] and your Front Door endpoint usually means Front Door can't match the incoming request (like for the www host) to any active routing rule, even if validation passed and root works fine. It's super common when the routing setup doesn't explicitly cover the subdomain or endpoint host. Root domain working points to a separate rule or origin just for the apex.

Think of it like this: Front Door checks protocol > host ([www.risenfame.com] or rf-gufpf4a4d0euece2.z01.azurefd.net) > path in that order; no match = that exact error page. Propagation is done since validation shows green, but test with curl -H "Host: [www.risenfame.com]" https://rf-gufpf4a4d0euece2.z01.azurefd.net to mimic.​

Steps:

• Jump into Front Door Designer > Routing rules: Add/edit one for frontend "[www.risenfame.com]" (or endpoint host), pattern "/*", forward to your origin group.​
• Confirm origin group health—ping the backend directly, check ports/probes.​
• Purge cache via portal and wait 5 mins; hit incognito or dig [www.risenfame.com] to verify CNAME.​

If it's still busted after that, grab diagnostics from Overview > Metrics for rule matches.

Official Docs

• Troubleshoot Front Door issues
• Route matching explained
• Configure custom domain HTTPS

Kindly let us know if the above helps or you need further assistance on this issue.

Update:

On top of it I would like to make one rule-based routing: All traffic from https://risenfame.com be redirected to www.risenfame.com. Could you suggest how this can be achieved.

To handle the redirect from risenfame.com to www.risenfame.com, start by adding the root domain as a custom domain in Front Door if it's not there yet (validate with TXT and use Azure DNS for the apex CNAME). Then jump into the rules engine.​

Rules Engine Steps

• Go to your Front Door profile > Rules engine > Add a new rule set (name it something like RootToWWW). Create this one rule:​
• Match condition: Server variable = Host name, operator = Equals, value = risenfame.com (case insensitive).
• Action: URL redirect—set type to 301 permanent, protocol to HTTPS, destination host to www.risenfame.com, and preserve the path and query string.

Associate the rule set with the route tied to your root domain. Purge the Front Door cache from the portal, give it 5 minutes, and test using curl -I https://risenfame.com (look for the 301 response). Peek at the metrics overview for any rule match issues if needed.

Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.