An Azure service that provides streamlined full-stack web app development.
Hi @Thomas G Gagnon,
Thank you for reaching us regarding the issue that you are trying to connect your domain to your Azure Static Web App. The error message you're getting suggests that your domain might be linked to another app or that there are records or settings that need to be cleaned up before proceeding.
Why this happens:
- The domain is still registered to another Azure resource
The domain may still be associated with another Azure resource. Azure does not allow a custom domain to be linked to more than one service at a time, and even if the original resource was deleted, the cleanup process may still be in progress, temporarily locking the domain. - Old DNS validation (TXT) records still exist
Azure requires a TXT record token to validate domain ownership. If an old TXT record, such as "asuid.yourdomain.com", still exists in your DNS, Azure may treat it as an active domain binding, which can result in the portal displaying an “already connected” error. - DNS propagation delays
If DNS records were recently changed or removed, Azure may still use cached DNS data for validation, which can delay the cleanup process longer than normal DNS propagation.
Recommended steps:
- First, confirm the domain is not linked to any other Azure service, including Static Web Apps, App Service, Front Door/CDN, or Storage accounts.
- Then, remove any old asuid TXT records and outdated CNAME or A records from DNS.
- Finally, add the new TXT validation record provided by Azure and wait for full DNS propagation before retrying the domain validation.
Reference:
https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain
Kindly let us know if the above helps or you need further assistance on this issue.
Please "accept" if the information helped you. This will help us and others in the community as well.