I am blocked adding a custom domain to Azure Front Door Standard/Premium and need an internal escalation.
Issue When creating a custom domain in Azure Front Door, I receive:
“Another custom domain with the same host name already exists.”
This happens immediately, before DNS validation.
Affected hostnames
demo.bluectrl.app
bluectrl.app (apex domain)
Subscription
Resource Group: xxxxx
Front Door Profile: xxxxx
SKU: Azure Front Door Standard
Facts
The domain was recently purchased (new owner)
DNS is currently clean and delegated to the registrar
No Azure Front Door profile in my subscription uses these hostnames
az afd custom-domain list confirms the hostnames do not exist in this profile
DNS queries show no CNAME or A records pointing to Azure Front Door
The error persists across retries and after full DNS reset
Conclusion
This appears to be an orphaned global hostname ownership record in Azure Front Door (leftover from a previous tenant/subscription).
This is a known backend condition that cannot be resolved by customers and requires cleanup by the Azure Front Door engineering team.
Request
As I do not have a technical support plan, I kindly ask a Microsoft moderator to:
Escalate this internally to the Azure Front Door product/engineering team
Request removal of the orphaned global hostname ownership for:
demxxxapp
bxxxl.app
Thank you for your assistance.