CI/CD for Azure Web Apps

Application Insights
Azure DevOps
Web Apps

Solution ideas

This article is a solution idea. If you'd like us to expand the content with more information, such as potential use cases, alternative services, implementation considerations, or pricing guidance, let us know by providing GitHub feedback.

Azure Web Apps is a fast and simple way to create web apps using ASP.NET, Java, Node.js, Python, and other languages and frameworks. Deliver value faster to your customers with a continuous integration and continuous deployment (CI/CD) pipeline that pushes each of your changes automatically to Azure Web Apps.

Architecture

Architecture diagram

Download a Visio file of this architecture.

Workflow

  1. Identify the work item in the backlog.
  2. Change the application source code.
  3. Commit your application code and configuration to a code repository, while linking the commit to the work item.
  4. Changes to the repo trigger continuous integration for building and testing the application.
  5. The build pipeline builds the application and runs tests.
  6. Upon successful build pipeline execution, the continuous deployment trigger orchestrates the deployment of application artifacts with environment-specific parameters.
  7. Once the app is deployed, Azure Application Insights collects health, performance, and usage data.
  8. Review the health, performance, and usage information.
  9. Create new issues or update backlog items with Application Insights data.

Components

Scenario details

Potential use cases

Azure Web Apps offer numerous benefits that include:

  • Highly secure web apps development.
  • Multilingual and versatile framework.
  • Global scale with high availability.
  • Quick analytics and actionable insights.
  • Secure integration with other SaaS apps.

Contributors

This article is maintained by Microsoft. It was originally written by the following contributors.

Principal author:

To see non-public LinkedIn profiles, sign in to LinkedIn.

Next steps