An Azure service that provides streamlined full-stack web app development.
Hello @Pws Admin
This behavior is typically due to DNS record conflicts or GoDaddy limitations rather than Azure propagation delay. For a subdomain such as www, Azure Static Web Apps requires a single public CNAME record that points directly to your default Static Web App hostname (for example, yourapp.azurestaticapps.net), with no URL forwarding, masking, A/AAAA records, or duplicate CNAME/TXT records for the same host. Azure validates using public DNS resolvers, so even if GoDaddy shows the record, validation can still fail if stale records, DNSSEC, or forwarding rules are interfering. For an apex/root domain, GoDaddy does not fully support ALIAS/ANAME or CNAME flattening needed for optimal Azure Static Web Apps root-domain mapping, so the recommended approach is to first configure www as a CNAME and then forward the root domain to www, or move DNS hosting to Azure DNS for full support. For TXT validation, Azure should generate the ownership code after selecting TXT and entering the hostname; if the portal does not generate the code, this may be a portal-side issue, so retry in an InPrivate browser session, clear cache, or use Azure CLI/REST as a workaround. Please follow Microsoft’s official guidance for external DNS custom domain setup and apex domain limitations .
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
Let me know if you have any further assistance needed.