Add new AppConfiguration lab

Instructions/Labs/[new] AZ400_M05_Enable_Dynamic_Configuration_and_Feature_Flags.md

@@ -0,0 +1,272 @@
+---
+lab:
+    title: 'Enable Dynamic Configuration and Feature Flags'
+    module: 'Module 05: Implement a secure continuous deployment using Azure Pipelines'
+---
+
+# Enable Dynamic Configuration and Feature Flags
+
+# Student lab manual
+
+## Lab requirements
+
+- This lab requires **Microsoft Edge** or an [Azure DevOps supported browser.](https://learn.microsoft.com/azure/devops/server/compatibility?view=azure-devops#web-portal-supported-browsers)
+
+- **Set up an Azure DevOps organization:** If you don't already have an Azure DevOps organization that you can use for this lab, create one by following the instructions available at [Create an organization or project collection](https://learn.microsoft.com/azure/devops/organizations/accounts/create-organization?view=azure-devops).
+
+- Identify an existing Azure subscription or create a new one.
+
+- Verify that you have a Microsoft account or an Azure AD account with the Contributor or the Owner role in the Azure subscription. For details, refer to [List Azure role assignments using the Azure portal](https://learn.microsoft.com/azure/role-based-access-control/role-assignments-list-portal) and [View and assign administrator roles in Azure Active Directory](https://learn.microsoft.com/azure/active-directory/roles/manage-roles-portal).
+
+## Lab overview
+
+[Azure App Configuration](https://learn.microsoft.com/azure/azure-app-configuration/overview) provides a service to manage application settings and feature flags centrally. Modern programs, especially those running in a cloud, generally have many distributed components. Spreading configuration settings across these components can lead to hard-to-troubleshoot errors during application deployment. Use App Configuration to store all the settings for your application and secure their accesses in one place.
+
+## Objectives
+
+After you complete this lab, you will be able to:
+
+- Enable dynamic configuration
+- Manage feature flags
+
+## Lab duration
+
+-   Estimated time: **60 minutes**
+
+## Instructions
+
+### Exercise 0: Configure the lab prerequisites
+
+In this exercise, you will set up the prerequisites for the lab, which consist of a new Azure DevOps project with a repository based on the [eShopOnWeb](https://github.com/MicrosoftLearning/eShopOnWeb).
+
+#### Task 1: (skip if done) Create and configure the team project
+
+In this task, you will create an **eShopOnWeb** Azure DevOps project to be used by several labs.
+
+1.  On your lab computer, in a browser window open your Azure DevOps organization. Click on **New Project**. Give your project the name **eShopOnWeb** and choose **Scrum** on the **Work Item process** dropdown. Click on **Create**.
+
+#### Task 2: (skip if done) Import eShopOnWeb Git Repository
+
+In this task you will import the eShopOnWeb Git repository that will be used by several labs.
+
+1.  On your lab computer, in a browser window open your Azure DevOps organization and the previoulsy created **eShopOnWeb** project. Click on **Repos>Files** , **Import**. On the **Import a Git Repository** window, paste the following URL https://github.com/MicrosoftLearning/eShopOnWeb.git  and click on **Import**: 
+
+1.  The repository is organized the following way:
+    - **.ado** folder contains Azure DevOps YAML pipelines
+    - **.devcontainer** folder container setup to develop using containers (either locally in VS Code or GitHub Codespaces)
+    - **.azure** folder contains Bicep&ARM infrastructure as code templates used in some lab scenarios.
+    - **.github** folder container YAML GitHub workflow definitions.
+    - **src** folder contains the .NET 6 website used on the lab scenarios.
+
+#### Task 3: (skip if done) Set main branch as default branch
+
+1. Go to **Repos>Branches**
+1. Hover on the **main** branch then click the ellipsis on the right of the column
+1. Click on **Set as default branch**
+
+### Exercise 1: (skip if done) Import and run CI/CD Pipelines
+
+In this exercise, you will import and run the CI pipeline, configure the service connection with your Azure Subscription and then import and run the CD pipeline.
+
+#### Task 1: Import and run the CI pieline
+
+Let's start by importing the CI pipeline named [eshoponweb-ci.yml](https://github.com/MicrosoftLearning/eShopOnWeb/blob/main/.ado/eshoponweb-ci.yml).
+
+1. Go to **Pipelines>Pipelines**
+
+1. Click on **Create Pipeline** button
+
+1. Select **Azure Repos Git (Yaml)**
+
+1. Select the **eShopOnWeb** repository
+
+1. Select **Existing Azure Pipelines YAML File**
+
+1. Select the **/.ado/eshoponweb-ci.yml** file then click on **Continue**
+
+1. Click the **Run** button to run the pipeline
+
+1. Your pipeline will take a name based on the project name. Let's **rename** it for identifying the pipeline better. Go to **Pipelines>Pipelines** and click on the recently created pipeline. Click on the elipsis and **Rename/Remove** option. Name it **eshoponweb-ci** and click on **Save**.
+
+#### Task 2: Manage the service connection
+
+You can create a connection from Azure Pipelines to external and remote services for executing tasks in a job.
+
+In this task, you will create a service principal by using the Azure CLI, which will allow Azure DevOps to:
+- Deploy resources on your azure subscription
+- Deploy the eShopOnWeb application
+
+> **Note**: If you do already have a service principal, you can proceed directly to the next task.
+
+You will need a service principal to deploy  Azure resources from Azure Pipelines.
+
+A service principal is automatically created by Azure Pipeline when you connect to an Azure subscription from inside a pipeline definition or when you create a new service connection from the project settings page (automatic option). You can also manually create the service principal from the portal or using Azure CLI and re-use it across projects. 
+
+1.  From the lab computer, start a web browser, navigate to the [**Azure Portal**](https://portal.azure.com), and sign in with the user account that has the Owner role in the Azure subscription you will be using in this lab and has the role of the Global Administrator in the Azure AD tenant associated with this subscription.
+1.  In the Azure portal, click on the **Cloud Shell** icon, located directly to the right of the search textbox at the top of the page. 
+1.  If prompted to select either **Bash** or **PowerShell**, select **Bash**. 
+
+   >**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and select **Create storage**. 
+
+1.  From the **Bash** prompt, in the **Cloud Shell** pane, run the following commands to retrieve the values of the Azure subscription ID attribute: 
+
+    ```sh
+    subscriptionName=$(az account show --query name --output tsv)
+    subscriptionId=$(az account show --query id --output tsv)
+    echo $subscriptionName
+    echo $subscriptionId
+    ```
+
+    > **Note**: Copy both values to a text file. You will need them later in this lab.
+
+1.  From the **Bash** prompt, in the **Cloud Shell** pane, run the following command to create a service principal:
+
+    ```sh
+    az ad sp create-for-rbac --name sp-az400-azdo --role contributor --scopes /subscriptions/$subscriptionId
+    ```
+
+    > **Note**: The command will generate a JSON output. Copy the output to text file. You will need it later in this lab.
+
+1. Next, from the lab computer, start a web browser, navigate to the Azure DevOps **eShopOnWeb** project. Click on **Project Settings>Service Connections (under Pipelines)** and **New Service Connection**.
+
+1. On the **New service connection** blade, select **Azure Resource Manager** and **Next** (may need to scroll down).
+
+1. The choose **Service principal (manual)** and click on **Next**.
+
+1. Fill in the empty fields using the information gathered during previous steps:
+    - Subscription Id and Name
+    - Service Principal Id (or clientId), Key (or Password) and TenantId.
+    - In **Service connection name** type **azure subs**. This name will be referenced in YAML pipelines when needing an Azure DevOps Service Connection to communicate with your Azure subscription.
+
+1. Click on **Verify and Save**.
+
+#### Task 3: Import and run the CD pipeline
+
+1. Go to **Pipelines>Pipelines**
+
+1. Click on **New pipeline** button
+
+1. Select **Azure Repos Git (Yaml)**
+
+1. Select the **eShopOnWeb** repository
+
+1. Select **Existing Azure Pipelines YAML File**
+
+1. Select the **/.ado/eshoponweb-ci.yml** file then click on **Continue**
+
+1. In the YAML pipeline definition, customize:
+- **YOUR-SUBSCRIPTION-ID** with your Azure subscription id.
+- **az400eshop-NAME** replace NAME to make it globally unique.
+- **AZ400-EWebShop-NAME** with the resource group name defined before in the lab.
+
+1. Click on **Save and Run** and wait for the pipeline to execute succesfully.
+
+    > **Note**: The deployment may take a few minutes to complete.
+
+    The CD definition consists of the following tasks:
+    - **Resources**: it is prepared to automatically trigger based on CI pipeline completion. It also downloads the repository for the bicep file.
+    - **AzureResourceManagerTemplateDeployment**: Deploys the Azure Web App using bicep template.
+
+1. Your pipeline will take a name based on the project name. Let's **rename** it for identifying the pipeline better. Go to **Pipelines>Pipelines** and click on the recently created pipeline. Click on the ellipsis and **Rename/Remove** option. Name it **eshoponweb-cd-webapp-code** and click on **Save**.
+
+### Exercise 2: Manage Azure App Configuration
+
+In this exercise, you will create the App Configuration resource in Azure, enable the managed identity and then test the full solution.
+
+>Note: This exercise doesn't require any coding skills. The website's code implements already Azure App Configuration functionalities.
+If you want to know how to implement this in your application, please take a look at these tutorials: [Use dynamic configuration in an ASP.NET Core app](https://learn.microsoft.com/azure/azure-app-configuration/enable-dynamic-configuration-aspnet-core) and [Manage feature flags in Azure App Configuration](https://learn.microsoft.com/azure/azure-app-configuration/manage-feature-flags).
+
+#### Task 1: Create the App Configuration resource
+
+1. In the Azure Portal, search for the **App Configuration** service
+1. Click **Create app configuration** then select:
+    - Your Azure Subscription
+    - The Resource Group created previously (it should be named **AZ400-EWebShop-NAME**)
+    - The location
+    - A unique like **appcs-NAME-REGION** for example
+    - Select the **Free** pricing tier
+1. Click on **Review + create** then **Create**
+1. After creating the App Configuration service, go to **Overview** and copy/save the value of the **Endpoint**.
+
+#### Task 2: Enable Managed Identity
+
+1. Go to the Web App deployed using the pipeline (it should be named **az400-webapp-NAME**).
+1. In the **Settings** section, click on **Identity** then switch status to **On** in the **System Assigned** section, click **save>yes** and wait a few seconds for the operation to finish.
+1. Go back to the App Configuration service and click on **Acceess control** then **Add role assignment**.
+1. In the **Role** section, select **App Configuration Data Reader**
+1. In the **Members** section, check **Manage Identity** then select the managed identity of your Web App (they should have the same name).
+1. Click on **Review and assign**
+
+#### Task 3: Configure the Web App
+
+In order to make sure that your website is accessing App Configuration, you need to update its configuration.
+1. Go back to your Web App.
+1. In the **Settings** section, click on **Configuration**.
+1. Add two new application settings:
+    - First app setting
+        - **Name:** UseAppConfig
+        - **Value:** true
+    - Second app setting
+        - **Name:** AppConfigEndpoint
+        - **Value:** *the value you saved/copied previously from App Configuration Endpoint. It should look like https://appcs-NAME-REGION.azconfig.io*
+1. Click **Ok** then **Save** and wait for the settings to be updated.
+1. Go to **Overview** and click on **Browse**
+1. At this step, you will see no changes in the website since the App Configuration doesn't contain any data. This is what you will do in the next tasks.
+
+#### Task 4: Test the Configuration Management
+
+1. In your website, select **Visual Studio** in the **Brand** drop-down list and click on the arrow button (**>**).
+1. You will see a message saying *"THERE ARE NO RESULTS THAT MATCH YOUR SEARCH"*.
+The goal of this Lab is to be able to update that value without updating the website's code or redeploying it.
+1. In order to try this, go back to App Configuration.
+1. In the **Operations** section, select **Configuration Explorer**.
+1. Click on **Create > Key-value** then add:
+    - **Key:** eShopWeb:Settings:NoResultsMessage
+    - **Value:** *type your custom message*
+1. Click **Apply** then go back to your website and refresh the page.
+1. You should see your new message instead of the old default value.
+
+Congratulations! In this task, you tested the **Configuration explorer** in Azure App Configuration.
+
+#### Task 5: Test the Feature Flag
+
+Let's continue to test the Feature manager.
+1. In order to try this, go back to App Configuration.
+1. In the **Operations** section, select **Feature manager**.
+1. Click on **Create** then add:
+    - **Enable feature flag:** Checked
+    - **Feature flag name:** SalesWeekend
+1. Click **Apply** then go back to your website and refresh the page.
+1. You should see an image with text "ALL T-SHIRTS ON SALE THIS WEEKEND".
+1. You can disable this feature in App Configuration and then you would see that the image disappears.
+
+Congratulations! In this task, you tested the **Feature manager** in Azure App Configuration.
+
+### Exercise 3: Remove the Azure lab resources
+
+In this exercise, you will remove the Azure resources provisioned in this lab to eliminate unexpected charges.
+
+>**Note**: Remember to remove any newly created Azure resources that you no longer use. Removing unused resources ensures you will not see unexpected charges.
+
+#### Task 1: Remove the Azure lab resources
+
+In this task, you will use Azure Cloud Shell to remove the Azure resources provisioned in this lab to eliminate unnecessary charges.
+
+1. In the Azure portal, open the **Bash** shell session within the **Cloud Shell** pane.
+1. List all resource groups created throughout the labs of this module by running the following command:
+
+    ```sh
+    az group list --query "[?starts_with(name,'AZ400-EWebShop-')].name" --output tsv
+    ```
+
+1. Delete all resource groups you created throughout the labs of this module by running the following command:
+
+    ```sh
+    az group list --query "[?starts_with(name,'AZ400-EWebShop-')].[name]" --output tsv | xargs -L1 bash -c 'az group delete --name $0 --no-wait --yes'
+    ```
+
+    >**Note**: The command executes asynchronously (as determined by the --nowait parameter), so while you will be able to run another Azure CLI command immediately afterwards within the same Bash session, it will take a few minutes before the resource groups are actually removed.
+
+## Review
+
+In this lab, you learned how to dynamically enable configuration and manage feature flags.