How to Deploy Azure Logic Apps on Private ASE via CI/CD Without a VNet Agent
A development team successfully configured an Azure DevOps pipeline to deploy Logic Apps Standard running on an internal Load Balancer App Service Environment (ILB ASE v3), which lacks a public SCM endpoint. The standard deployment methods fail in this setup because they rely on the private Kudu SCM endpoint, typically requiring a self-hosted agent inside the virtual network. The team's solution uses a Run-From-Package approach, where the pipeline uploads a zip file to Azure Blob Storage and the Logic App pulls it using its own managed identity. This eliminates the need for SAS tokens, SCM access, or a VNet-connected build agent, with the pipeline only communicating with Azure Storage and the ARM management plane. The team documented six real-world failures encountered along the way, including issues with stopped app states, missing Azure CLI, and misconfigured managed identities.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in