Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
Azure Static Web App - Custom domains validated but returning 404 "Web Site not found"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 59%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAW%3C/text%3E%3C/svg%3E)
A. Washington
0
Reputation points
I've successfully validated both my custom domains in Azure Static Web Apps with green checkmarks and SSL certificates showing expiry dates. DNS records are configured correctly in GoDaddy (A record @ pointing to Azure IP, CNAME www pointing to *.azurestaticapps.net), and whatsmydns.net confirms propagation to Azure IPs globally. However, when visiting the domains, I get a 404 error stating "Custom domain has not been configured inside Azure" even though Azure portal shows them as validated. The default azurestaticapps.net URL works fine. I've tried deleting and re-adding the domains, waiting for propagation (2+ hours), and clearing cache. What additional steps are needed to get Azure to route traffic to these validated custom domains?
Azure DNS
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 48%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
RAMAMURTHY MAKARAPU 1,125 Reputation points Microsoft External Staff Moderator2025-12-03T17:05:03.6066667+00:00 Hi @A. Washington,
Thank you for submitting your question on Microsoft Q&A.
Even if your custom domain is validated in the Azure Portal, the app will still show a 404 if one of the following is missing
Even though the domain was successfully validated, that only proves you own the DNS records. Azure does not automatically bind the domain to your Web App. You must manually bind it.
To confirm this:
- Open your App Service in the Azure Portal.
- Go to Custom domains.
- Look under Assigned custom domains.
- Your domain (for example,
app.example.com) must be listed there.
If the domain appears only under Validated but not under Assigned, it means it isn’t actually connected to your app yet. To fix this, click Add custom domain or Add binding and complete the binding process. This step is what tells Azure, “Use this domain for my web app,” not just that you own it.
-
A. Washington 0 Reputation points
2025-12-03T17:22:39.72+00:00 @RAMAMURTHY MAKARAPU Thank you I am waiting patiently. My site has been down since last yesterday. Tried everything and it is fully validated. I moved my site domains form SquareSpace to Azure yesterday. Domains are connected to the site in Azure since yesterday.
-
RAMAMURTHY MAKARAPU 1,125 Reputation points Microsoft External Staff Moderator
2025-12-03T22:03:33.7966667+00:00 Hi @**A. Washington,
**Thanks for the details you provided in the private message form that the symptoms you’re seeing point to routing/certificate mismatch on the Azure Static Web Apps (SWA) platform, sometimes compounded by apex-domain DNS constraints at GoDaddy and HSTS history from your previous host.For the apex domain (x-xxxxx.com), you need to use the correct DNS method for GoDaddy. GoDaddy does not support ALIAS/ANAME or CNAME-flattening at the root domain, which Azure Static Web Apps normally prefers. Because of this limitation, Microsoft recommends either moving your DNS to Azure DNS or, if you want to stay with GoDaddy, using an A-record that points directly to the Static Web App’s stable inbound IP.
In your Static Web App (SWA), you can find this stableInboundIP in the Overview > JSON view. The IP you used appears to be correct.
So your DNS setup at GoDaddy should be:
- A record for
@→x.xxx.xxx.xxx(apex domain) - CNAME for
www→*.azurestaticapps.net(subdomain)
This is the recommended setup when GoDaddy cannot use ALIAS/ANAME.
note: Using an A-record on the apex domain locks your traffic to a single regional IP and bypasses SWA’s global distribution. If global performance becomes important later, you may want to move your DNS to Azure DNS where ALIAS is supported.
Squarespace often enables HSTS on domains, which forces browsers to use strict HTTPS rules. If your old Squarespace site had HSTS enabled especially withincludeSubDomainsor if it was preloaded—your browser will automatically block any connection that doesn’t match the expected HTTPS certificate. That’s why, after you migrate DNS, you may immediately see errors like NET::ERR_CERT_COMMON_NAME_INVALID with no option to bypass. This is normal behavior when HSTS is active.What you should do:
Make sure your new site does not send an HSTS header until its HTTPS certificate is fully set up and valid on the new host.
Check whether your domain is in the HSTS preload list using https://hstspreload.org.
If it is preloaded, browsers will continue enforcing strict HTTPS regardless of cache clearing.
You must request removal from the preload list after your site serves a correct HTTPS certificate for some time. If the domain is not preloaded, normal browser cache expiration will eventually accept the new certificate once DNS and SWA bindings are correct.
If you want, I can also rewrite this in a shorter or more formal documentation style.
Reference :
https://learn.microsoft.com/en-us/azure/static-web-apps/apex-domain-external
Kindly let us know if the above comment helps or you need further assistance on this issue.
Please "upvote" if the information helped you. This will help us and others in the community as well.
- A record for
-
RAMAMURTHY MAKARAPU 1,125 Reputation points Microsoft External Staff Moderator
2025-12-06T01:33:31.35+00:00 Hi @A. Washington,
Could you please review my comments, follow the steps, and let me know whether your issue has been resolved?
Sign in to comment
Sign in to answer