Deploying to App Service Environment from Azure DevOps

3
votes

We have 1 internal ASE in a subnet. In a different subnet in the same network, we have deployed a Virtual Machine that acts as Azure DevOps Agent Windows v2

We are able to deploy Web Apps manually (using Visual Studio) from a machine that access to this Virtual Network, but cant get deployment working from Azure DevOps.

Here's what we have done

  • Default NSG rules exist so traffic is enabled on 80/443 ports. Updated NSG to allow traffic to/from: 13.107.6.183 and 13.107.9.183 (checked with all ports)
  • Pipeline Task added flag -allowUntrusted

The error we get during deployment is:

More Information: Could not connect to the remote computer ("{myapp}.scm.{customdomain}.com"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started.  Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Error: Unable to connect to the remote server
Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xx.xx.xx.xx:443
Error count: 1.

Are we missing anything in NSG rules?

1
azureazure-devopsazure-deploymentazure-app-service-envrmnt

1 Answers

5
votes

Internet-based CI systems, such as GitHub and Azure DevOps, will still work with an ILB ASE if the build agent is internet accessible and on the same network as ILB ASE. So in case of Azure DevOps, if the build agent is created on the same VNET as ILB ASE (different subnet is fine), it will be able to pull code from Azure DevOps git and deploy to ILB ASE.

https://docs.microsoft.com/en-us/azure/app-service/environment/create-ilb-ase

You can also follow the detailed steps in this article

Hope this helps!