Azure Managed App CI/CD Demo

The goal of this demo is to demonstrate how to build azure pipeline to update azure managed application artifacts in customer environment.

Requirements

The demo requirement is to have the knowledge of

1. Create and publish managed app
2. Azure pipeline

Learning Resources

It is highly recommended to review the following material before starting this demo

1. Managed Applications for the Microsoft Marketplace - Workshop
2. Customize your pipeline
3. Create Azure AD App Registration

Prerequisites

Before using the demo, the following components should exist:

1. Azure managed app offer with at least one plan
2. AAD App Registration

Note

AAD App Registration will be used as part of the managed app plan technical configuration and also as part of Azure pipeline

Publish the managed app demo

1. Find amav1.zip under arm folder and upload it to managed app plan technical configuration
2. Use AAD App Registration Client ID to relocate its corresponding Enterprise App
3. Locate the Object ID for the Enterprise App
4. Enter the objbect ID and AAD tenant ID
5. Save Draft
6. Review and publish

Deploy published managed app

Note

It is highly recommended to use a different tenant for deployment to demonstrate customer environment

1. Deploy the managed app from marketplace, please refer to this link
2. Access the managed resource group, open the webapp url under App Service and you should see the following webpage

Deploy modified Artifact to managed app

1. Modify the web application source code, add extra header line or change logo
2. Establish Azure pipeline using Azure-pipline.yaml file, please refer to this article as a guide HOW-TO Establish Pipeline
3. Add a variable group to azure library amaSecrets and add AAD app registration client ID, client secret ID and tenant ID. Please refer to this article HOW-TO add variable Group
4. Add new environment and call it UpdateManagedApp
5. Add yourself or other AAD User as Approval for the environment, please refer to this articale HOW-TO Create pipeline Environment
6. Run pipeline
7. After it finishes, access managed app webapp and confirm it was updated

As you see the managed app reflects the new site version