Merge branch 'master' into az-400-modernization

Author: LuizMacedo

.github/ISSUE_TEMPLATE/bug.yml

@@ -8,7 +8,7 @@ body:
       value: |
         # Thanks for taking the time to fill out this bug report!
         
-        **Replace issue name M00-LAB00:QUICK_DESCRIPTION, for example "M01-LAB01: My new issue"**
+        **Replace issue name LAB00:QUICK_DESCRIPTION, for example "LAB01: My new issue"**
   - type: input
     id: contact
     attributes:

.github/ISSUE_TEMPLATE/feedback.yml

@@ -8,7 +8,7 @@ body:
       value: |
         # Thanks for taking the time to fill out this feedback report!
         
-        **Replace feedback name M00-LAB00:QUICK_DESCRIPTION, for example "M01-LAB01: My new feedback"**
+        **Replace feedback name LAB00:QUICK_DESCRIPTION, for example "LAB01: My new feedback"**
   - type: input
     id: contact
     attributes:

.github/pull_request_template.md

@@ -1,4 +1,4 @@
-**Replace issue name M00-LAB00:QUICK_DESCRIPTION, for example "M01-LAB01: My new issue" (or same name as linked Issue)**
+**Replace issue name LAB00:QUICK_DESCRIPTION, for example "LAB01: My new issue" (or same name as linked Issue)**
 
 ## Related Issue
 

.github/release.yml

@@ -0,0 +1,20 @@
+# .github/release.yml
+
+changelog:
+  exclude:
+    labels:
+      - ignore-for-release
+    authors:
+      - octocat
+  categories:
+    - title: Breaking Changes 🛠
+      labels:
+        - Semver-Major
+        - breaking-change
+    - title: Exciting New Features 🎉
+      labels:
+        - Semver-Minor
+        - enhancement
+    - title: Other Changes
+      labels:
+        - "*"

Instructions/Labs/AZ400_M00_Validate_lab_environment.md

@@ -10,25 +10,28 @@ lab:
 
 ## Instructions
 
-1. Get a new **Azure Pass promocode** (valid for 30 days) from the instructor or other source.
-2. Use a private browser session to get a new **Microsoft Account (MSA)** at [Microsoft account](https://account.microsoft.com) or use an existing one.
-3. Using the same browser session, go to [Microsoft Azure Pass](https://www.microsoftazurepass.com) to redeem your Azure Pass using your Microsoft Account (MSA). For details, see [Redeem a Microsoft Azure Pass](https://www.microsoftazurepass.com/Home/HowTo?Length=5). Follow the instructions for redemption.
-4. Using the same browser session, go to [Microsoft Azure](https://portal.azure.com), then search at the top of the portal screen for **Azure DevOps**. In the resulting page, click **Azure DevOps organizations**.
-5. Next, click on the link labelled **My Azure DevOps Organizations** or navigate directly to [My Information](https://aex.dev.azure.com).
+> **Note**: Start at step 4, if you do already have a **personal Microsoft Account** setup and an active Microsoft Azure Pass subscription linked to that account.
+
+1. Get a new **Azure Pass promocode** from the instructor or other source.
+2. Use a private browser session to get a new **personal Microsoft Account (MSA)** at [https://account.microsoft.com](https://account.microsoft.com).
+3. Using the same browser session, go to [https://www.microsoftazurepass.com](https://www.microsoftazurepass.com) to redeem your Azure Pass using your Microsoft Account (MSA). For details, see [Redeem a Microsoft Azure Pass](https://www.microsoftazurepass.com/Home/HowTo?Length=5). Follow the instructions for redemption. 
+
+4. Open a browser and navigate to [https://portal.azure.com](https://portal.azure.com), then search at the top of the Azure portal screen for **Azure DevOps**. In the resulting page, click **Azure DevOps organizations**. 
+5. Next, click on the link labelled **My Azure DevOps Organizations** or navigate directly to [https://aex.dev.azure.com](https://aex.dev.azure.com).
 6. On the **We need a few more details** page, select **Continue**.
 7. In the drop-down box on the left, choose **Default Directory**, instead of “Microsoft Account”.
 8. If prompted (*"We need a few more details"*), provide your name, e-mail address, and location and click **Continue**.
-9. Back at [My Information](https://aex.dev.azure.com) with **Default Directory** selected click the blue button **Create new organization**.
+9. Back at [https://aex.dev.azure.com](https://aex.dev.azure.com) with **Default Directory** selected click the blue button **Create new organization**.
 10. Accept the *Terms of Service* by clicking **Continue**.
 11. If prompted (*"Almost done"*), leave the name for the Azure DevOps organization at default (it needs to be a globally unique name) and pick a hosting location close to you from the list.
 12. Once the newly created organization opens in **Azure DevOps**, click **Organization settings** in the bottom left corner.
 13. At the **Organization settings** screen click **Billing** (opening this screen takes a few seconds).
 14. Click **Setup billing** and on the right-hand side of the screen select the **Azure Pass - Sponsorship** subscription and click **Save** to link the subscription with the organization.
-15. Once the screen shows the linked Azure Subscription ID at the top, change the number of **Paid parallel jobs** for **MS Hosted CI/CD** from 0 to **1**. Then click the **SAVE** button at the bottom.
-16. **Wait at least 3 hours before using the CI/CD capabilities** so that the new settings are reflected in the back end. Otherwise, you will still see the message *"This agent is not running because you have reached the maximum number of requests…"*.
-17. In Organization Settings, go to Security -> **Policies**
-18. **Turn on** "Third-party application access via OAuth"
+15. Once the screen shows the linked Azure Subscription ID at the top, change the number of **Paid parallel jobs** for **MS Hosted CI/CD** from 0 to **1**. Then click the **SAVE** button at the bottom. 
+16. In **Organization Settings**, go to section **Security** and click **Policies**.
+17. Toggle the switch to **On** for **Third-party application access via OAuth**
     > Note: The OAuth setting helps enable tools such as the DemoDevOpsGenerator to register extensions. Without this, several labs may fail due to a lack of the required extensions.
-19. **Turn on** "Allow public projects"
-    > Note: The public projects setting will allow some of the labs to use the free version of some extensions.
-20. OPTIONAL: you can validate this new setting has been successfully applied by creating and triggering a build pipeline. To do this either talk to the instructor or create a demo project into the newly created organization with billing enabled, using [Azure DevOps Demo Generator](https://azuredevopsdemogenerator.azurewebsites.net).
+18. Toggle the switch to **On** for **Allow public projects**
+    > Note: Extensions used in some labs might require a public project to allow using the free version.
+19. **Wait at least 3 hours before using the CI/CD capabilities** so that the new settings are reflected in the backend. Otherwise, you will still see the message *"No hosted parallelism has been purchased or granted"*.
+20. OPTIONAL: you can validate these new settings have been successfully applied by creating and triggering a build pipeline. To do this either talk to the instructor or create a demo project into the newly created organization with billing enabled, using [Azure DevOps Demo Generator](https://azuredevopsdemogenerator.azurewebsites.net).

Instructions/Labs/AZ400_M01_Agile_Planning_and_Portfolio_Management_with_Azure_Boards.md

@@ -236,8 +236,8 @@ The sprint backlog should contain all the information the team needs to successf
 
     > **Note**: The current sprint has a pretty limited scope. There are two tasks in the **To do** stage. At this point, neither task has been assigned. Both show a numeric value to the right of **Unassigned** entry representing the remaining work estimate.
 
-1. In the rectangle representing the **Add page for most recent tutorial**, click the **Unassigned** entry and, in the list of user accounts, select your account to assign the task to yourself.
-1. Assign the **Add page for most recent tutorial** task to yourself.
+1.  In the rectangle representing the **Add page for most recent tutorials**, click the **Unassigned** entry and, in the list of user accounts, select your account to assign the task to yourself.
+1.  Assign the **Add page for most recent tutorial** task to yourself. 
 
     > **Note**: This automatically updates the **Work By: Assigned To** section of the **Work details** pane.
 
@@ -263,9 +263,9 @@ The sprint backlog should contain all the information the team needs to successf
 
     > **Note**: Note that the **Work details** panel has been updated to reflect your available bandwidth. The actual number displayed in the **Work details** panel might vary, but your total sprint capacity will be equal to the number of working days remaining till the end of the sprint, since you allocated 1 hour per day. Take a note of this value since you will use it in the upcoming steps.
 
-    > **Note**: One convenient feature of the boards is that you can easily update key data in-line. It's a good practice to regularly update the **Remaining Work** estimate to reflect the amount of time expected for each task. Let's say you've reviewed the work for the **Add page for most recent tutorial** task and found that it will actually take longer than originally expected.
+    > **Note**: One convenient feature of the boards is that you can easily update key data in-line. It's a good practice to regularly update the **Remaining Work** estimate to reflect the amount of time expected for each task. Let's say you've reviewed the work for the **Add page for most recent tutorials** task and found that it will actually take longer than originally expected. 
 
-1. On the **Taskboard** tab of the **Sprints** view, in the square box representing the **Add page for most recent tutorial**, set the estimated number of hours to match your total capacity for this sprint, which you identified in the previous step.
+1.  On the **Taskboard** tab of the **Sprints** view, in the square box representing the **Add page for most recent tutorials**, set the estimated number of hours to match your total capacity for this sprint, which you identified in the previous step.
 
     ![Review the "Work details" section information, team´s assigned time is bigger than capacity.](images/m1/over_capacity_v1.png)
 

Instructions/Labs/AZ400_M03_Configuring_Agent_Pools_and_Understanding_Pipeline_Styles.md

@@ -132,7 +132,7 @@ In this task, you will configure the LOD VM as an Azure DevOps self-hosting agen
     | Enter agent pool (press enter for default) | **az400m05l05a-pool** |
     | Enter agent name | **az400m05-vm0** |
     | Enter work folder (press enter for _work) | **Enter** |
-    | Enter Perform an unzip for tasks for each step. (press enter for N) | **Enter** |
+    | **(Only if shown)** Enter Perform an unzip for tasks for each step. (press enter for N) | **Enter** |
     | Enter run agent as service? (Y/N) (press enter for N) | **Y** |
     | Enter User account to use for the service (press enter for NT AUTHORITY\NETWORK SERVICE) | **Enter** |
     | Enter whether to prevent service starting immediately after configuration is finished? (Y/N) (press enter for N) | **Enter** |
@@ -152,6 +152,10 @@ In this task, you will configure the LOD VM as an Azure DevOps self-hosting agen
     demands:
     - agent.name -equals az400m05-vm0
     ```
+1. For `Task: NugetToolInstaller@0`, click on **Settings (link that is displaying above the task in grey colour)**, modify **Version of NuGet.exe to install** > **4.0.0**  and click on **Add**. 
+1.  On the **PartsUnlimited** edit pane, in the upper right corner of the pane, click **Save** and, on the **Save** pane, click **Save** again. This will automatically trigger the build based on this pipeline. 
+1.  In the Azure DevOps portal, in the vertical navigational pane on the left side, in the **Pipelines** section, click **Pipelines**.
+1.  On the **Recent** tab of the **Pipelines** pane, click the **PartsUnlimited** entry, on the **Runs** tab of the **PartsUnlimited** pane, select the most recent run, on the **Summary** pane of the run, scroll down to the bottom, in the **Jobs** section, click **Phase 1** and monitor the job until its successful completion. 
 
 1. For `Task: NugetInstaller@0`, click on **Settings (link that is displaying above the task in grey colour)**, modify **Version of NuGet.exe to install** > **4.0.0**  and click on **Add**.
 1. On the **PartsUnlimited** edit pane, in the upper right corner of the pane, click **Save** and, on the **Save** pane, click **Save** again. This will automatically trigger the build based on this pipeline.

Instructions/Labs/AZ400_M03_Implementing_GitHub_Actions_by_using_DevOps_Starter.md

@@ -76,9 +76,10 @@ In this task, you will create an Azure DevOps Starter project that automatically
     | Repository | **az400m08l01** |
     | Subscription | the name of the Azure subscription you are using for this lab |
     | Web app name | any valid, globally unique host name in the **azurewebsites.net** DNS namespace |
-    | Location | the name of any Azure region in which you can provision an Azure web app |
+    | Location | the name of any Azure region in which you can provision an Azure web app. **East US** recommended |
 
-    > **Note**: Wait for the provisioning to complete. This should take about 1 minute.
+   > **Note**: Some **Location** may fail due to unavailable resources . **East US** recommended.
+   > **Note**: Wait for the provisioning to complete. This should take about 1 minute.
 
 1. On the **Deploy_DevOps_Project_az400m08l01 \| Overview** blade, click **Go to Resource**.
 1. On the **az400m08l01** blade, on the **GitHub Workflow** tile, click **Authorize**.

Instructions/Labs/AZ400_M03_Integrating_External_Source_Control_with_Azure_Pipelines.md

@@ -62,9 +62,9 @@ In this task, you will fork a GitHub repo and install Azure Pipelines in your Gi
 
     > **Note**: You have the option to specify repositories to include, but for the purposes of this lab, just include all of them. Note that Azure DevOps requires the listed set of permissions to fulfill its services.
 
-7. If prompted, authenticate with your GitHub password to continue.
-8. When prompted, on the **Setup your Azure Pipelines project** page, in the **Select your Azure DevOps organization** dropdown list, select your Azure DevOps account and click **Create a new project**.
-9. When prompted, on the **Setup your Azure Pipelines project** page, in the **Project name** textbox, type **Integrating External Source Control with Azure Pipelines**, leave the **Project visibility** set to **Private**, and click **Continue**.
+7.  If prompted, authenticate with your GitHub password to continue.
+8.  When prompted, on the **Setup your Azure Pipelines project** page, firstly, click **Switch Directories** and ensure 'Default Directory' is selected. Then, in the **Select your Azure DevOps organization** dropdown list, select your Azure DevOps account and click **Create a new project**.
+9.  When prompted, on the **Setup your Azure Pipelines project** page, in the **Project name** textbox, type **Integrating External Source Control with Azure Pipelines**, leave the **Project visibility** set to **Private**, and click **Continue**.
 10. On the **Azure Pipelines by Microsoft would like permission to** page, click **Authorize Azure Pipelines**.
 
 #### Task 2: Configuring your Azure Pipelines project