Trouble moving a domain from one app service to another.

Question

Trouble moving a domain from one app service to another.

JC Woodford 0

I'm having trouble adding a custom domain to my app service. I configured the dns on another service and I want to move it to a new one. I deleted the dns and the binding with it, then tried to add it to the new service. It said it added the dns, but wont do the ssl binding, and I get a 404 trying to navigate to the address now.

Praneeth Maddali 4,525 Reputation points Microsoft External Staff Moderator

2026-01-28T20:03:44.09+00:00
Hi @JC Woodford

Sorry to hear you're running into issues migrating your custom domain between App Services—it sounds like a verification or propagation hiccup might be at play, especially since the domain adds but SSL binding fails and you're seeing a 404.

Here's a quick step-by-step to get this sorted:

Double-check removal from the old App Service: Head to the old app's Custom domains page in the Azure portal and confirm the domain is fully removed. If it's lingering, delete it there first.

Add and verify on the new App Service: In the new app's Custom domains section, add the domain and grab the unique verification ID. Update your DNS records at your registrar (e.g., add a TXT record with that ID for asuid.yourdomain.com). Then hit Validate in Azure—it needs to confirm ownership before SSL works.

Update DNS pointers: Point your CNAME (for subdomains) or A record (for apex) to the new app's .azurewebsites.net hostname or IP. Give it 15-30 minutes for propagation, and test with nslookup.

Set up SSL binding: Once verified, go to TLS/SSL settings, create an App Service Managed Certificate (it's free), and bind it to your domain. If it errors, try syncing the cert or re-validating.

Troubleshoot the 404: Clear your browser cache or use incognito mode. If it persists, check Azure's Diagnose and solve problems tool for domain-specific errors

Reference :

https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-custom-domain-issues-azure-app-service

https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-bindings

https://learn.microsoft.com/en-us/azure/app-service/overview-custom-domains

https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain?tabs=root%2Cazurecli

https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-custom-domain-issues-azure-app-service

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.
JC Woodford 0 Reputation points

2026-01-28T20:06:45.8966667+00:00

Yea those steps are the first steps I took before creating a post here. I even waited 3 days now to verify that any historical records get purged. I'm pretty sure its a deeper issue or bug in the system at this point.
Praneeth Maddali 4,525 Reputation points Microsoft External Staff Moderator

2026-01-28T20:15:02.4+00:00
Hi @JC Woodford

Thanks for letting me know you've already tried the basics and waited a few days—that rules out simple propagation issues.

It looks like there might be a lingering internal link from the old App Service causing the verification or binding to fail (this happens sometimes even after removal). Here's the short, simple fix to try:

In the new App Service > Custom domains:

Remove the domain completely (if it's still listed).

Wait 5-10 minutes.

Add it back fresh using the new verification ID shown.

Update your DNS TXT record with that exact new ID.

Click Validate.

2.Once it verifies, add the SSL binding again (use App Service Managed Certificate—it's quick and free).

This reset often clears stuck mappings.

If it still doesn't work after this, open a quick support ticket in the Azure portal (Help + support > New support request). Mention the migration, 404 error, and SSL binding fail—they can check backend logs and fix any hidden conflicts fast.

Reference :

Troubleshoot custom domain issues (covers 404 "Web App not found" and mapping problems): https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-custom-domain-issues-azure-app-service

Troubleshoot domain & TLS/SSL problems (includes cert sync and binding fixes): https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-domain-and-tls-ssl-certificates
Praneeth Maddali 4,525 Reputation points Microsoft External Staff Moderator

2026-02-02T11:34:28.3666667+00:00

Hi @JC Woodford

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?

1 answer

Your answer

JC Woodford 0 Reputation points

2026-01-28T20:06:45.8966667+00:00

Yea those steps are the first steps I took before creating a post here. I even waited 3 days now to verify that any historical records get purged. I'm pretty sure its a deeper issue or bug in the system at this point.
Praneeth Maddali 4,525 Reputation points Microsoft External Staff Moderator

2026-01-28T20:15:02.4+00:00

Hi @JC Woodford

Thanks for letting me know you've already tried the basics and waited a few days—that rules out simple propagation issues.

It looks like there might be a lingering internal link from the old App Service causing the verification or binding to fail (this happens sometimes even after removal). Here's the short, simple fix to try:

In the new App Service > Custom domains:

Remove the domain completely (if it's still listed).

Wait 5-10 minutes.

Add it back fresh using the new verification ID shown.

Update your DNS TXT record with that exact new ID.

Click Validate.

2.Once it verifies, add the SSL binding again (use App Service Managed Certificate—it's quick and free).

This reset often clears stuck mappings.

If it still doesn't work after this, open a quick support ticket in the Azure portal (Help + support > New support request). Mention the migration, 404 error, and SSL binding fail—they can check backend logs and fix any hidden conflicts fast.

Reference :

Troubleshoot custom domain issues (covers 404 "Web App not found" and mapping problems): https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-custom-domain-issues-azure-app-service

Troubleshoot domain & TLS/SSL problems (includes cert sync and binding fixes): https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-domain-and-tls-ssl-certificates
Praneeth Maddali 4,525 Reputation points Microsoft External Staff Moderator

2026-02-02T11:34:28.3666667+00:00

Hi @JC Woodford

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?

Answer 1

To troubleshoot the issue of moving a custom domain from one Azure App Service to another, follow these steps:

Verify Domain Removal: Ensure that the domain has been completely removed from the previous App Service. If the domain is still bound to the old service, it cannot be added to the new one. You may need to contact Azure support to release the domain if it appears locked.
Check DNS Configuration: Make sure that the DNS records are correctly configured for the new App Service. For a root domain, you need an A record pointing to the app's IP address and a TXT record for verification. If you are using a subdomain, a CNAME record is recommended. Ensure that both records are present and correctly configured.
Clear Caches: Clear your browser cache and DNS cache. You can flush the DNS cache on a Windows machine using the command ipconfig /flushdns. This helps to eliminate any cached old IP addresses that may be causing the 404 error.
SSL Binding: If you are having trouble with SSL binding, ensure that you have added a certificate for the domain. If the domain does not have a certificate binding yet, you will encounter issues accessing it securely. You can add a private certificate for the domain and configure the binding accordingly.
Check for Conflicting Records: Ensure that you do not have conflicting DNS records (like both A and CNAME records for the same domain), as this can prevent proper resolution.
Domain Status: In the Azure portal, check that the domain appears as "Active" in the custom domains list for your new App Service. If it does not, you may need to re-add it.

Following these steps should help resolve the issues you are experiencing with moving your custom domain to a new Azure App Service.

Share via

Trouble moving a domain from one app service to another.

1 answer

Your answer