tag:help.appveyor.com,2012-11-13:/discussions/problems/5373-webdeploy-to-azure-app-service-brokenAppVeyor: Discussion 2018-10-19T08:18:03Ztag:help.appveyor.com,2012-11-13:Comment/409125632016-10-04T22:18:15Z2016-10-04T22:18:15ZWebdeploy to azure app service broken?<div><p>Hi Julian,</p>
<p>Please check that NTLM is disabled in deployment provider
settings. Also please check that you can deploy new project created
today with Visual Studio.</p>
<p>--ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/409125632016-10-04T23:50:05Z2016-10-04T23:50:05ZWebdeploy to azure app service broken?<div><p>Just did publishing to both staging and production Azure web
sites and it worked like a charm: <a href="https://ci.appveyor.com/project/AppVeyor-Website/website/build/1.0.618#L153">
https://ci.appveyor.com/project/AppVeyor-Website/website/build/1.0....</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/409125632016-10-05T05:11:53Z2016-10-05T05:11:53ZWebdeploy to azure app service broken?<div><p>NTLM is set to false in both projects but will test direct
publish today</p></div>julian.elvetag:help.appveyor.com,2012-11-13:Comment/409125632016-10-05T07:05:49Z2016-10-05T07:05:49ZWebdeploy to azure app service broken?<div><p>Hmm, importing a freshly-downloaded .PublishSettings into VS2013
and trying a direct deployment still fails with the same error (a
timeout).</p>
<p>So seems it's not Appveyor but something else.</p>
<p>If I resolve it I'll post the answer here</p></div>julian.elvetag:help.appveyor.com,2012-11-13:Comment/409125632016-10-05T07:24:12Z2016-10-05T07:24:12ZWebdeploy to azure app service broken?<div><p>Ok sorted - Azure server resource problem. The two projects I
had problems with were both (with another service) on the same
appservice plan, which was on the lowest scale setting and was
running 98% CPU. Upscaling has resolved the issue.</p></div>julian.elve