Share via

Failure to create the custom domain

Allan Hull 0 Reputation points
2026-03-30T14:14:39.6733333+00:00

Attempting to add custom domain (Azure Front Door > Domain). CoPilot assistance didn't yield resolution to this error.

User's image

Azure Front Door
Azure Front Door

An Azure service that provides a cloud content delivery network with threat protection.


2 answers

Sort by: Most helpful
  1. Ravi Varma Mudduluru 9,985 Reputation points Microsoft External Staff Moderator
    2026-03-30T14:57:42.96+00:00

    Hello @ Allan Hull

    Thank you reaching out to Microsoft Q&A.

    The custom domain was already associated with an Azure Front Door (AFD) profile, and an attempt was made to add the same domain to another AFD profile. A custom domain cannot be associated with multiple AFD profiles simultaneously.

    The backend team performed a cleanup operation in the tenant, which resolved the conflict, and you were then able to successfully create the custom domain.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments No comments

  2. Q&A Assist
    2026-03-30T14:15:03.0333333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error indicates that the hostname being added to Azure Front Door is already bound as a custom domain on another Azure resource (for example, another Front Door, App Service, Static Web App, or a resource in a different subscription/tenant). Azure blocks reuse of the same custom hostname to prevent domain takeover.

    To resolve:

    1. Confirm the hostname is not already in use in the current subscription:
      • Check all Front Door profiles, App Services, Static Web Apps, and other services that can have custom domains.
      • If the hostname is found, remove the custom domain binding from that resource first, then retry adding it to the desired Front Door.
    2. Check other subscriptions/tenants:
      • If the domain might have been used previously in another subscription, directory, or by a colleague, verify there is no lingering custom-domain binding there.
    3. If the domain is locked to an inaccessible/unknown resource:
      • Open an Azure support ticket and request that the custom domain be released.
      • Provide proof of domain ownership (for example, a screenshot of DNS settings at the registrar) so Support can manually unbind the hostname from the old resource.
      • After Support confirms the release, add the custom domain again in Azure Front Door.

    Also ensure that, once the custom domain is successfully added to Front Door, there is at least one routing rule with path /* associated with that frontend host so traffic routes correctly.


    References:

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.