We encountered an issue recently where a large number of deployments were launched to Web App which are all using the same Azure App Service.

This resulted in high CPU usage on the App Service and deployments started failing and terminating with errors connecting to the /msdeploy.axd endpoint of the Web App. Additionally the Web Apps themselves became unresponsive and we had to stop all Web Apps and start them one by one and then re-launch deployments in series to resolve.

A simple workaround is to ask users not to launch too many deployments at once, but it would be useful if Octopus Deploy could use similar behaviour to when deploying to a tentacle and allow the configuration of how many concurrent deployments to the same Azure App Service.