Orphaned custom domain binding from deleted subscription blocking Static Web Ap

Question

Orphaned custom domain binding from deleted subscription blocking Static Web Ap

Dan 0

Domain: codewrinkles.com and www.codewrinkles.com

Issue: Domain was configured in an Azure subscription that was deleted years ago.

Current behavior: New Static Web App shows domain as "Validated" but returns 404

with certificate for *.xxxx-xxxx-0-xxxx-x-xxxxx.p.azurewebsites.net instead of

custom domain certificate.

Need: Backend team to manually release orphaned domain bindings from deleted

subscription so I can use domain in current subscription.

Praneeth Maddali 2,710 Reputation points Microsoft External Staff Moderator

2025-12-10T05:50:05.1866667+00:00
Hi @Dan
Thanks for posting your question and providing those details ofissue with the orphaned domain bindings from that old deleted subscription. I've seen this crop up occasionally where the backend doesn't fully release everything after deletion, leading to that partial validation and the fallback to the default cert.

The best way forward is to have our Azure support team manually clear those lingering bindings on the backend, as it's not something you can resolve directly through the portal or CLI. Here's what I recommend:

Double-check your setup: Make sure your DNS records (CNAME for [www.codewrinkles.com] and TXT/A for the apex domain) are correctly pointing to your new Static Web App's hostname. Tools like dig or nslookup can help confirm this.

Open a support request: Head to the Azure portal, go to Help + support, and create a new technical request. Select Static Web Apps under the service, and describe the issue as an "orphaned custom domain from deleted subscription" with your domain names, old subscription details (if you have them), and screenshots of the validation status and 404 error. Include proof of domain ownership too. They should be able to release it within a few days—aim for Severity C unless it's urgent.

After the fix: Once cleared, add the domains back in your Static Web App's Custom domains section. Azure will handle the new managed certificate automatically.

Reference :

https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain?tabs=azure-portal

https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Praneeth Maddali 2,710 Reputation points Microsoft External Staff Moderator

2025-12-11T07:34:54.62+00:00

Hi @Dan

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

Your answer

Praneeth Maddali 2,710 Reputation points Microsoft External Staff Moderator

2025-12-10T05:50:05.1866667+00:00

Hi @Dan
Thanks for posting your question and providing those details ofissue with the orphaned domain bindings from that old deleted subscription. I've seen this crop up occasionally where the backend doesn't fully release everything after deletion, leading to that partial validation and the fallback to the default cert.

The best way forward is to have our Azure support team manually clear those lingering bindings on the backend, as it's not something you can resolve directly through the portal or CLI. Here's what I recommend:

Double-check your setup: Make sure your DNS records (CNAME for [www.codewrinkles.com] and TXT/A for the apex domain) are correctly pointing to your new Static Web App's hostname. Tools like dig or nslookup can help confirm this.

Open a support request: Head to the Azure portal, go to Help + support, and create a new technical request. Select Static Web Apps under the service, and describe the issue as an "orphaned custom domain from deleted subscription" with your domain names, old subscription details (if you have them), and screenshots of the validation status and 404 error. Include proof of domain ownership too. They should be able to release it within a few days—aim for Severity C unless it's urgent.

After the fix: Once cleared, add the domains back in your Static Web App's Custom domains section. Azure will handle the new managed certificate automatically.

Reference :

https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain?tabs=azure-portal

https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Praneeth Maddali 2,710 Reputation points Microsoft External Staff Moderator

2025-12-11T07:34:54.62+00:00

Hi @Dan

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

Share via

Orphaned custom domain binding from deleted subscription blocking Static Web Ap

Your answer