Front Door hostname still "owned by another profile" after its custom domain and profile were deleted

The persistent exact-host conflict after both the custom domain and its former profile were deleted strongly indicates an orphaned backend ownership record, which Microsoft Support or the Azure Front Door engineering team will likely need to clear.

Azure Front Door does not permit a custom domain validated in one Front Door or Microsoft CDN profile to be added to another profile.^1^ Your evidence shows that the visible owner has been deleted but the service-wide ownership check has not released the hostname. A closely matching case was resolved when the backend team cleared that ownership record.^2^

Request backend cleanup

1. In the Azure portal, open the target Front Door profile.
2. Select Support + Troubleshooting under Help.
3. Complete the diagnostics, then select Create a support request.^3^
4. Use a description such as:

   Azure Front Door Standard custom hostname did.devsandbox.verifiedorchestration.com returns nameAvailable: false, reason Conflict, and “already owned by another profile.”

   The custom-domain deletion completed at 07:13 UTC on 27 October 2026, and the source profile deletion completed at 22:42 UTC. The conflict remained at 22:48 UTC. The source was automatically migrated from Azure CDN Standard from Microsoft (classic) in April 2026.

   Please inspect and clear any orphaned global custom-domain ownership record for this exact hostname.

5. Privately attach or provide:
   • Source and target subscription IDs.
   • Source and target profile resource IDs and frontDoorId values.
   • Custom-domain resource ID, if retained in deployment logs or activity history.
   • Operation/correlation IDs for the domain and profile deletion operations.
   • The checkHostNameAvailability request and response, including timestamp.
   • The deletion entries from Azure Activity Log.
   • Confirmation that you can publish a DNS ownership record if support requests it.

Technical support requests generally require an eligible Azure support plan.^4^ Without one, keep this Q&A question open for moderator attention and request escalation to the Front Door product team, but Q&A escalation is not guaranteed to provide backend remediation.

Adding a TXT record now will not resolve this stage of the failure: Front Door issues the _dnsauth token only after the custom-domain resource reaches validation. Your request is being rejected earlier by hostname availability.^5^

Other migrated profiles

The migration documentation does not establish that CDN migration generally leaves orphaned claims, so the April 2026 migration should be supplied as relevant history rather than asserted as the cause. Microsoft documents CDN classic migration as a tier upgrade and provides post-migration DNS and cleanup steps, but it does not document a customer-accessible operation for deleting an ownership record that remains after the corresponding Azure resource is gone.^6^

For remaining migrated profiles, use this as prudent operational guidance—not as a guarantee against orphaned records:

1. Inventory each custom hostname and export the profile configuration and resource IDs.
2. Move its CNAME to the Standard/Premium endpoint and verify production traffic there.
3. Remove the hostname from all route associations.
4. Delete the custom-domain resource and wait for that operation to finish.
5. Before deleting the profile, test adding or checking that exact hostname from its intended destination profile.
6. Delete the old profile only after traffic works on the destination and rollback is no longer required.

Warning: Removing a custom domain or deleting a profile can interrupt production traffic; perform this only in an approved maintenance window after validating dependencies and retaining an exported configuration. Profile deletion removes its endpoints, origins, and custom domains.^7^

If availability remains Conflict after the visible custom-domain resource has been successfully deleted, there is no documented self-service command that targets the residual global claim. Preserve the old profile and evidence where possible, and escalate before deleting more resources.

References

1. Configure a custom domain on Azure Front Door
2. Azure Front Door Standard/Premium blocks custom domain due to orphaned global hostname ownership (no support plan) - Microsoft Q&A
3. Create an Azure support request
4. Support and troubleshooting for Azure Front Door
5. Domains in Azure Front Door
6. Migration FAQ - Azure Front Door | Microsoft Learn
7. az afd profile delete