An Azure service that provides streamlined full-stack web app development.
Thanks for reaching out and sharing the details. The blue "404 Web Site not found" page showing up even though your custom domains appear as Validated is a known behavior on Azure Static Web Apps. It typically happens after several add/delete attempts, leaving the domain binding in an inconsistent state on Azure’s side.
Recommended Reset Steps
To start fresh:
- In the Azure portal, navigate to your Static Web App > Custom domains.
- Delete both custom domains if they are still listed.
- If they don’t remove cleanly, wait 10–15 minutes and try again. You can also use the Azure CLI command az staticwebapp hostname delete for a more reliable removal.
After deletion, go to your DNS provider and temporarily remove any CNAME or ALIAS records that were pointing to your Static Web App. This prevents old records from interfering.Important: After deletion, give Azure at least 24 hours to fully release the domain binding before you re-add them. Re-adding too soon is often what causes things to get stuck.
Correct Setup Process
Domain ownership verification (TXT record) is required, but it is not sufficient by itself. You also need proper routing records so traffic actually reaches your app:
- For a www subdomain: Add a CNAME record pointing to your app’s default hostname (<your-app>.azurestaticapps.net).
- For the apex/root domain: Many registrars (including GoDaddy) have limitations with apex records. A common workaround is to configure the www version first and then set up domain forwarding from the root to www. For full apex support, consider using Azure DNS.
Once your DNS records are updated (allow 5–30 minutes for propagation):
- In the Azure portal, go to Custom domains >+ Add >Custom domain on other DNS.
- Enter your domain, add the TXT verification record provided by Azure, and complete the validation.
- Azure will automatically issue a free SSL/TLS certificate once the domain is successfully bound.
Reference :
https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain-external
https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain
https://learn.microsoft.com/en-us/azure/static-web-apps/apex-domain-external
After these changes, test both the default *.azurestaticapps.net URL (which should load normally) and your custom domains.
If you still see the 404 after a full reset and DNS propagation, feel free to reply with a description of your current DNS records and what you see in the Custom domains blade
If the answer is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you