Share via

Domain connecting problem

Thomas G Gagnon 0 Reputation points
2026-02-23T21:03:01.9566667+00:00

Hi guys I'm having trouble connecting my domain to static web app. I get this error message has if it's already been connected to the app but it hasn't. User's image

it's been a few days and I still get the same error.

Azure Static Web Apps
Azure Static Web Apps

An Azure service that provides streamlined full-stack web app development.


1 answer

Sort by: Most helpful
  1. Golla Venkata Pavani 5,390 Reputation points Microsoft External Staff Moderator
    2026-02-23T21:59:43.4566667+00:00

    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:

    1. 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.
    2. 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.
    3. 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.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.