The following forum(s) are migrating to a new home on Microsoft Q&A (Preview): Azure App Service - Web Apps!

Ask new questions on Microsoft Q&A (Preview).
Interact with existing posts until December 13, 2019, after which content will be closed to all new and existing posts.

Learn More

 none
ILB ASE using Github RRS feed

  • Question

  • We are looking at switching from a standard app service plan to the new ILB ASE v2 environment for security purposes. We currently use github to push updates into our web apps/APIs. Since the ILB environment is locked down, can we still use github? What are our options here?

    Thank you.

    Friday, November 9, 2018 6:02 PM

Answers

  • Both GitHub (in your case) 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. If you don't want to create your own build agent, you need to use a CI system that uses a pull model, such as Dropbox.

    Additionally, the publishing endpoints for apps in an ILB ASE use the domain that the ILB ASE was created with. This domain appears in the app's publishing profile and in the app's portal blade (Overview > Essentials and also Properties). If you have an ILB ASE with the subdomain contoso.net and an app named mytest, use mytest.contoso.net for FTP and mytest.scm.contoso.net for web deployment.

    Monday, November 12, 2018 6:58 AM
    Moderator
  • See this blog for detail on using Azure Dev Ops with an ASE. Essentially you have to use a deployment agent that has access to Kudu. The agent can be installed on a VM and acts as a proxy for the deployment.

    https://blogs.msdn.microsoft.com/mihansen/2018/01/04/continuous-deployment-with-vststfs-and-app-service-environment-ase/

    • Marked as answer by Vegas577 Tuesday, November 13, 2018 1:23 PM
    Tuesday, November 13, 2018 1:40 AM

All replies

  • Both GitHub (in your case) 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. If you don't want to create your own build agent, you need to use a CI system that uses a pull model, such as Dropbox.

    Additionally, the publishing endpoints for apps in an ILB ASE use the domain that the ILB ASE was created with. This domain appears in the app's publishing profile and in the app's portal blade (Overview > Essentials and also Properties). If you have an ILB ASE with the subdomain contoso.net and an app named mytest, use mytest.contoso.net for FTP and mytest.scm.contoso.net for web deployment.

    Monday, November 12, 2018 6:58 AM
    Moderator
  • Could we also use the new Azure Pipelines service to deploy into the ILB ASE?
    Monday, November 12, 2018 2:59 PM
  • See this blog for detail on using Azure Dev Ops with an ASE. Essentially you have to use a deployment agent that has access to Kudu. The agent can be installed on a VM and acts as a proxy for the deployment.

    https://blogs.msdn.microsoft.com/mihansen/2018/01/04/continuous-deployment-with-vststfs-and-app-service-environment-ase/

    • Marked as answer by Vegas577 Tuesday, November 13, 2018 1:23 PM
    Tuesday, November 13, 2018 1:40 AM