Outage - Web Deploy .SCM servers/dns appear down in the Eastern Hosting Regions

Question

Outage - Web Deploy .SCM servers/dns appear down in the Eastern Hosting Regions

LesBaker-8476 0

Publishing to my clients in the Eastern Hosting Regions is failing. Had been deploying to these all day no issues, when they stopped responding to requests to the respective .scm urls.

Even blew away one server, recreated it, new profile, etc to verify. Rejecting connection requests. Looks like DNS resolution is failing.

Base url responds but the .scm used for publishing does not resolve, refuses connection requests.

I went and tried a few publishes/deployments to my customers in the central hosting areas and those are still fine. Internal diagnostics on the two servers show noting via Azure internal diagnostics.

LesBaker-8476 0 Reputation points

2025-04-08T14:13:04.87+00:00

14 hours later still down.

This is two servers in a row. But if I got to my other client servers in say central, they are up. So its not my dev client, or any firewalls/connectivity between myself and Azure. And this server was just provisioned yesterday. Reset profile several times.
Prabhavathi Manchala 810 Reputation points Microsoft External Staff

2025-04-08T18:05:31.9+00:00

Hi LesBaker-8476,

You're currently facing a Web Deploy outage affecting .SCM servers in Azure's Eastern regions, which is preventing you from publishing client sites. This is a known Azure issue caused by DNS resolution failures specific to .SCM endpoints, not a problem with your configuration. While base site URLs still respond, the .SCM subdomains fail to resolve, causing connection errors. Deployments to other regions like Central continue to work fine, and creating new servers or profiles doesn't fix the issue.

You can temporarily switch your deployments to servers in the Central region, as they are still functioning normally. Verify if there's an ongoing service incident affecting Azure App Service in the Eastern regions by checking the Service Health section in the Azure Portal.

To avoid future disruptions, it's a good idea to set up a backup plan using multiple Azure regions. You can configure DNS failover so that if one region has issues, your traffic automatically switches to another. If you're using on-premises DNS, you can also set it up to connect to multiple Azure regions for better reliability.

Kindly refer to the link below which is relevant to this issue.

https://learn.microsoft.com/en-us/answers/questions/1296847/azure-dns-for-failing-back
LesBaker-8476 0 Reputation points

2025-04-08T18:30:16.5466667+00:00

Thank you for finally admitting what I have known since yesterday. Everyone I have talked to about this kept directing me to run the Azure diagnostics. I ran every test I could find. And there are a lot of automatic diagnostics that ran on both servers I have since deleted. How is it that your automate Azure/bot diagnostics on my specific service are missing this internal outage this obvious? If you look at the publish profile it lists as you know, two URLs. One the base URL of your new site/app and the other is the corresponding .scm URL that is created with your web app for the publishing endpoint. Testing connectivity from outside Azure to these "two critical endpoints" would, in my opinion, be at the top of the list for automated diagnostics. Yet your bot powered analysis says nothing is wrong. And as such it drop kicks you automatically into unresolvable (there is nothing wrong so it must be you) purgatory. This is unacceptable and frankly amateur hour. Please resolve.

This sequence of non-support is even in the neighborhood of what one would expect from a top tier provider such as yourself. Half a day lost troubleshooting YOUR undocumented outage. Not happy.

And when I went to Twitter/X and informed @azuresupport that I had documented the fact that you were experiencing an outage, instead of thanking me, they suggested I go pay for support.
Prabhavathi Manchala 810 Reputation points Microsoft External Staff

2025-04-08T21:43:10.95+00:00
Hi LesBaker-8476,

I sincerely apologize for the frustration this has caused, especially considering the time and effort you put into troubleshooting, rebuilding environments, and raising the issue, your persistence is greatly appreciated. You’re right that Azure Web App publish profiles rely on both the base URL and the .scm (Kudu) endpoint, and when the .scm endpoint fails to resolve, as it did in the Eastern regions, it disrupts the publishing process and prevents deployments from succeeding.

A regional issue in Azure’s Eastern US datacenters caused problems with the .scm (Kudu) endpoints used for deployments. Your app’s main URL worked, but the .scm subdomains failed due to DNS issues, which Azure’s diagnostics didn’t catch since they focus on app availability.

If you need to deploy urgently, here are some temporary workarounds you can use.

If possible, temporarily deploy your app to a region like Central US, as the issue appears to be limited to the Eastern US regions.

You can deploy your app using Zip Deploy via the Kudu Console, GitHub Actions or Azure DevOps Pipelines, or through FTP/FTPS.

Consider setting up Service Health alerts on your subscription to get real-time notifications when Azure services affecting your resources experience issues.
Prabhavathi Manchala 810 Reputation points Microsoft External Staff

2025-04-09T19:28:10.6166667+00:00

Hi LesBaker-8476,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Prabhavathi Manchala 810 Reputation points Microsoft External Staff

2025-04-10T19:49:39.42+00:00

Hi LesBaker-8476,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Your answer

LesBaker-8476 0 Reputation points

2025-04-08T14:13:04.87+00:00

14 hours later still down.

This is two servers in a row. But if I got to my other client servers in say central, they are up. So its not my dev client, or any firewalls/connectivity between myself and Azure. And this server was just provisioned yesterday. Reset profile several times.
Prabhavathi Manchala 810 Reputation points Microsoft External Staff

2025-04-08T18:05:31.9+00:00

Hi LesBaker-8476,

You're currently facing a Web Deploy outage affecting .SCM servers in Azure's Eastern regions, which is preventing you from publishing client sites. This is a known Azure issue caused by DNS resolution failures specific to .SCM endpoints, not a problem with your configuration. While base site URLs still respond, the .SCM subdomains fail to resolve, causing connection errors. Deployments to other regions like Central continue to work fine, and creating new servers or profiles doesn't fix the issue.

You can temporarily switch your deployments to servers in the Central region, as they are still functioning normally. Verify if there's an ongoing service incident affecting Azure App Service in the Eastern regions by checking the Service Health section in the Azure Portal.

To avoid future disruptions, it's a good idea to set up a backup plan using multiple Azure regions. You can configure DNS failover so that if one region has issues, your traffic automatically switches to another. If you're using on-premises DNS, you can also set it up to connect to multiple Azure regions for better reliability.

Kindly refer to the link below which is relevant to this issue.

https://learn.microsoft.com/en-us/answers/questions/1296847/azure-dns-for-failing-back
LesBaker-8476 0 Reputation points

2025-04-08T18:30:16.5466667+00:00

Thank you for finally admitting what I have known since yesterday. Everyone I have talked to about this kept directing me to run the Azure diagnostics. I ran every test I could find. And there are a lot of automatic diagnostics that ran on both servers I have since deleted. How is it that your automate Azure/bot diagnostics on my specific service are missing this internal outage this obvious? If you look at the publish profile it lists as you know, two URLs. One the base URL of your new site/app and the other is the corresponding .scm URL that is created with your web app for the publishing endpoint. Testing connectivity from outside Azure to these "two critical endpoints" would, in my opinion, be at the top of the list for automated diagnostics. Yet your bot powered analysis says nothing is wrong. And as such it drop kicks you automatically into unresolvable (there is nothing wrong so it must be you) purgatory. This is unacceptable and frankly amateur hour. Please resolve.

This sequence of non-support is even in the neighborhood of what one would expect from a top tier provider such as yourself. Half a day lost troubleshooting YOUR undocumented outage. Not happy.

And when I went to Twitter/X and informed @azuresupport that I had documented the fact that you were experiencing an outage, instead of thanking me, they suggested I go pay for support.
Prabhavathi Manchala 810 Reputation points Microsoft External Staff

2025-04-08T21:43:10.95+00:00

Hi LesBaker-8476,

I sincerely apologize for the frustration this has caused, especially considering the time and effort you put into troubleshooting, rebuilding environments, and raising the issue, your persistence is greatly appreciated. You’re right that Azure Web App publish profiles rely on both the base URL and the .scm (Kudu) endpoint, and when the .scm endpoint fails to resolve, as it did in the Eastern regions, it disrupts the publishing process and prevents deployments from succeeding.

A regional issue in Azure’s Eastern US datacenters caused problems with the .scm (Kudu) endpoints used for deployments. Your app’s main URL worked, but the .scm subdomains failed due to DNS issues, which Azure’s diagnostics didn’t catch since they focus on app availability.

If you need to deploy urgently, here are some temporary workarounds you can use.

If possible, temporarily deploy your app to a region like Central US, as the issue appears to be limited to the Eastern US regions.

You can deploy your app using Zip Deploy via the Kudu Console, GitHub Actions or Azure DevOps Pipelines, or through FTP/FTPS.

Consider setting up Service Health alerts on your subscription to get real-time notifications when Azure services affecting your resources experience issues.
Prabhavathi Manchala 810 Reputation points Microsoft External Staff

2025-04-09T19:28:10.6166667+00:00

Hi LesBaker-8476,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Prabhavathi Manchala 810 Reputation points Microsoft External Staff

2025-04-10T19:49:39.42+00:00

Hi LesBaker-8476,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

Outage - Web Deploy .SCM servers/dns appear down in the Eastern Hosting Regions

Your answer