Module: 01

Lab: 01

Exercise 1/Task: 04

Step: 18

Description of issue
"Drag the As a customer, I want to view new tutorials work item from the Done stage into the QA Approved stage."

At this stage the work item is in the Approved column not in Done.

Module: 18

Lab/Demo: Integration between Azure DevOps and Teams

Exercise 0

Task: 01

Step: 06

Description of issue

When creating this project, I have been reproing an error every time I try and create a Project, like so:

The project has GH access, and despite checking 'Yes, I want to fork this repository', clicking 'Authorize', and then entering a valid GH username/password, the Project creation will fail w/error above. I tried simply deleting the DevOps Project (as existing note recommends) and trying again, however I experienced the same behavior. I check in GH and the repo had not been successfully created.

The only way I can find to get this to work is to run through the initial setup process, encounter the error, scroll back to the top of the page. Re-enter a new name such as 'Tailwind Traders2' in the 'New Project Name' field, re-select my Organization, verify 'Tailwind Traders' is still selected in the 'Selected Template' field, and then click the Create Project button again - it will then succeed in the 2nd attempt.

If I do not select the 'Yes I want to for this repo' in the GH section, I consistently fail with a perms error.

Uncertain what is the root-cause, but it almost seems as if the 'Authorize' process to GH is buggy in DevOps site & is not succeeding on first attempt of creation of any given project name in this module, and only successfully auths on the 2nd attempt in same browser session.

Module: 03

Lab/Demo: 03

Task: 01

Step: 03

Description of issue

Azure DevOps does not default to the TailwindTraders-Website repo. Instructions need to make sure to mention selecting the correct repo to find the WebSite.png file.

Task 1: Step 3: To the left of the Files pane, in the listing of the repo folder and file hierarchy, expand 
the Documents folder and its Images subfolder, in the Images subfolder, locate the Website.png 
entry, hover with the mouse pointer over its right end to reveal the vertical ellipsis symbol 
representing the More menu, click More, and, in the dropdown menu, click Download to 
download the Website.png file to the local Downloads folder on your lab computer.

Repro steps:

1. Visit demo generator and create a Tailwind Traders project.
2. Navigate to Azure DevOps and follow lab instructions.

Module: 10

Lab/Demo: 10 Lab: Creating a Release Dashboard

Task: 01 Task 1: Create an Azure DevOps Starter resource

Step: 01

Description of issue
The portal defaults to authorizing with git hub and the instructions do not say to switch it to DevOps (there is a link in the UI)
This causes much confusion and time to figure it out.

Repro steps:

1. start the lab
2. follow instructions
3. notice the github auth

Module: 03-20

Lab: all

Exercise: 00 Task: 01

Step: 06 (might depend on the lab)

Description of issue
In the note after Step 6 of Task 1 "Configure the team project" the text needs a small update to clarify what is meant. The user needs to navigate to the Azure DevOps organization, not the DevOps organization.
This issue has been corrected in Module 1 and 2 in a separate commit but all modules from 3 upwards are affected, too.

Now:

1. Click Create Project

Note: Wait for the process to complete. This should take about 2 minutes. In case the process fails, navigate to your DevOps organization, delete the project, and try again.

Then:

1. Click Create Project

Note: Wait for the process to complete. This should take about 2 minutes. In case the process fails, navigate to your Azure DevOps organization, delete the project, and try again.

Module: 7

Lab/Demo: Integrating Azure Key Vault with Azure DevOps

Student lab manual

Ex 1 Task: 3

Step: 17

Description of issue: attendees get confused on the Azure subscription dropdown list, clarifying note would be helpful.

Repro steps:

Module: 09

Lab/Demo: Lab: Package Management with Azure Artifacts

Excercise: 0

Task: 2

Step: 08

Description of issue: When you open the VM and download the project trying to use with VS2019 Community it constantly gets an import issue with the package, pre-installed software is not installed in some VMs.

Repro steps:
1- Clone PUL repo
2- Open With VS2019

Module: 12

Lab/Demo: 12

Task: 2

Step: 4

Description of issue
The repository is empty

Module: 19

Lab: 19

Task: 02

Step: 02

Remove Ex1.Task2.2

The source repo was updated .

Module: 20

Lab/Demo: Validating Code Bases for Compliance

Task: 02

Step: 17

Description of issue
The pipeline run fails with the error
##[error]No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form https://aka.ms/azpipelines-parallelism-request

I followed the instruction to the letter, created my project Public and switch it to Private as requested at the step 16, but I still got the same error.

I tried doing Task: 03, which is Create a pipeline by using the classic editor, and I also got the exact same error.

Screenshots will make it easier to navigate in the portal
(and also makes it easier to navigate the lab - screenshots are strong visual cues when going back and forth between lab guide and Azure Portal / ADO Portal)

Module: 14

Demo: Run Terraform in Azure Cloud Shell

Step: 6 - invalid terraform file:

The file shown to copy and paste does not work with the terraform version installed with the Azure Cloud Shell and returns the error insufficient features blocks.

provider "azurerm" {
}
resource "azurerm_resource_group" "rg" {
        name = "testResourceGroup"
        location = "westus"
}

Step 10 (terraform apply) returns with this error:

│ Error: Insufficient features blocks
│
│   on  line 0:
│   (source code not available)
│
│ At least 1 "features" blocks are required.

Adding an empty features block fixes the issue:

provider "azurerm" {
  features { }
}
resource "azurerm_resource_group" "rg" {
        name = "testResourceGroup"
        location = "westus"
}

Module: 14

Lab/Demo: Automating infrastructure deployments in the Cloud with Terraform and Azure Pipelines

Task: 03

Step: 09

Description of issue

I am pretty sure that the terraform lab is not quite working as described in the note section due to a subtlety in the way that Terraform plan and apply works.

In this section notes step iii it states that terraform will apply the changes determined during the planning stages.

This is not quite true as the way that the release steps are configures will call "Terraform apply -auto-approve" This will in fact perform a second plan before applying that plan.

In order to work as described, the plan file should be saved by adding "-out=tfplan" as a parameter to the plan step, then adding "tfplan" as a parameter to the apply step

It is also good practice to put an approval between the plan and the apply to allow for a review of the plan output

I can understand simplifying this for a lab, but not sure where the line is between showing good practice and keeping it simple 😉

Module: 10

Lab/Demo: 02

Task: 01

Step: 03

Description of issue

This lab requires that the DevOps Starter be created using Azure DevOps rather than GitHub. GitHub is the default option that's selected, so there needs to be steps added in Task 1, between Steps 2 and 3, to open the DevOps starter settings blade and change it to Azure DevOps, similar to in Module 08 Lab 01, Implementing GitHub Actions by using DevOps Starter, which has the following instructions in Task 1 to confirm that GitHub is selected (though in this case, we need to actually change it):

3. On the Start fresh with a new application page of the DevOps Starter blade, click the here link in the Setting up DevOps starter with GitHub, click here text.

Note: This will display the DevOps starter settings blade.

4. On the DevOps starter settings blade, ensure that the GitHub tile is selected and click Done.

If the instructions are followed as written, users will hit their first roadblock in Task 1, Step 4 when they are told to flip the Add a database slider to On, as that slider is not present on a GitHub starter. All the remaining instructions assume the starter was created in Azure DevOps.

Repro steps:

1. Follow the instructions as written up through Step 4.

Module: 12

Lab/Demo: 12

Task: 02

Step: 24

Description of issue
In the work item in visual studio - the process has changed so the accessing of the work item does not work when following the instructions. The learner was able to finish by skipping that step, but it would be great to have a walk through of the updates.

Repro steps:

1. Do the lab up to that point
2. View the UI and process change message in Visual Studio

Module: 12

Lab/Demo: Feature_Flag_Management_with_LaunchDarkly_and_Azure_DevOps

Task: 01

Step: 01

Description of issue

Repro steps:
In the Configure the team project step, when we create the Launch Darkly Project the Project is created, but there the repo is empty. Please check.

Module: 16

Lab/Demo: 01

Task: 01

Step: 04

It is not obvious that you need to use the shorter location name without spaces and the version information is not output (only entered into a variable).

Module: 12

Lab/Demo: 12 Integration between Azure DevOps and Teams

Task: 01

Step: 5-6

Description of issue
The log in instructions and the set up instructions use the wrong words - most students can add the boards by understanding that ADD to teams means ADD the bot (not mentioned in the instructions) but that the log in functionality works differently now.

In order to log in you need to @Azure Devops signin - but you need to click the prompts or it dose not work - this can be frustrating - especially since the instructions say to do another option that is no longer available.

Repro steps:

Module: 00

Lab/Demo: 00

Task: 00

Step: 00

1. C:\Users\Abc\Documents\Devops\Code\virtual-environments\images\win\scripts\Installers\Install-VS.json is the correct file name to install VS
2. az400m05-vm0.deployment.template.parameters.json is the correct filename with the parameters.
3. The project name in Exercise 0 is Integrating Azure Key Vault with Azure DevOps and not Configuring Agent Pools and Understanding Pipeline Styles
   (4. C:\Labview does not exist, but can be set to any directory where the repo was cloned if you do not want to clone to C:)

Repro steps:

1. N/A

Module 19 describes the Secure DevOps kit for Azure (AzSK). This kit is being phased out in FY21:

AzSK Sunset Notice

In the next version, the Azure Tenant Security Solution (AzTS) (developed by the same team) should be referenced instead:

Azure Tenant Security Solution

Module: 04

Lab: Version Controlling with Git in Azure Repos

Task: 01

Description of issue
It should be made clear that if one followed the flow and already did complete the lab for Module 2 that the steps up to Exercise 2 are not required anymore (creating a project, cloning the repo).

Module: 06

Lab: Enabling Continuous Integration with Azure Pipelines

Exercise: 01

Task: 01

Step: 16

Description of issue:
A recent Microsoft blog post has brought up a concern that might effect some AZ-400 participants, https://devblogs.microsoft.com/devops/change-in-azure-pipelines-grant-for-private-projects/

There is now a chance for some participants to not be granted the free tier of 1800 minutes in private projects which has caused issues when attempting portions of the course (Module 6 is one example). The error that occurs when this section is attempted without the free tier was "the agent request is not running because you have reached the maximum number of requests that can run for parallelism type 'Microsoft-Hosted-Private'. Current position in queue: 1" which can make troubleshooting difficult without being aware of the recent change.

The blog post proceeds to tell users to reach out to "[email protected]" with the users name and the name of the DevOps organization to have the free tier applied to your organization.

Module: 00

Lab/Demo: Implementing GitHub Actions by using DevOps Starter

Student lab manual

Task: 01

Step: 14

Description of issue
Step 14 says: Change the line 20 to

Repro steps:

Module: 13

Lab/Demo: 13

Task: 01

Step: 02

Description of issue

https://github.com/Azure/azure-quickstart-templates/blob/master/101-vm-simple-windows/azuredeploy.json (not found)

Missing steps, prior to Step 6, it should mention that learners must go to Azure Pipeline > Pipelines > Create a new pipeline

Module: 16

Lab/Demo: 16

Description of issue
the demo genererator´s CI template uses a (preview) "replace token" task for the appsettings.json. It does not look for "__" prefix/suffix as second "replace task". Result: CI/CD works but the pod crashes when starting because the connectionstring to the DB is not included this way on the appsettings.json.

Module: 10

Lab: Creating a Release Dashboard

Exercise: 01

Task: 02

Step: 02

Description of issue
The file referenced in this task has a different name and is stored in a different path.
The correct file path is: Application/aspnet-core-dotnet-core/Pages/Index.cshtml

1. In the Azure DevOps portal, in the vertical menu on the left side, click Repos, in the list of folders in the repository, navigate to the Applications\aspnet-core-dotnet-core\Pages\Shared folder and click the Index.chtml entry.
2. On the Index.chtml pane, click Edit, in line 20, replace
   Your ASP.NET Core app is up and running on Azure
   with
   Your ASP.NET Core app v1.1 is up and running on Azure
   click Commit, and, on the Commit pane, click Commit again. This will automatically trigger the build pipeline.

Module: 02

Lab/Demo: Sharing Team Knowledge using Azure Project Wikis

Task: Task 1

Step: 7

Description of issue
I am not able to see Create project button after step 6

Repro steps:
1.
1.
1.

Module: 20

Lab/Demo: 01

Task: 04

Step: 05

There is no longer a Create pull request checkbox on the edit page of a master branch.

What worked was as follows:

• On repo/File, click the master branch selector.
• Click + New Branch
• Enter branch1
• Click Create Branch
• Follow the editing steps
• Commit
• Click create Pull Request
• Click Create Pull request in the pull request dialog
• Continue with the Lab

Repro steps:

Module: 11

Lab/Demo: 11b

Task: 2

Step: 1

Github pages is rendering wronk link on "deploy to azure" button, it is rendering a link referencing the button image itself (img src). The correct link is still rendered on html but the button link is taking nowhere but to the button image itselv. Inspecting the page code, it shows the correct element chained with anoter that references the button image.

Repro steps:

1. Opem the github pages for the lab 11b
2. On exercise 0, task 2, click on the button "Deploy to azure".
3. Inspect the page source code to view the correct link and the link to the button image wrongly rendered

Module: 03

Lab/Demo: 03

Task: 1 and 2

Step: 00

Description of issue: no Devspaces file anymore in "main" branch of template repo, only in "create-ci-cd-action" branch

Module: 05

Lab: Configuring Agent Pools and Understanding Pipeline Styles

Exercise: 02 Task: 01

Step: 14

Description of issue

From the PowerShell snippet the string "PS C:> " should be removed so that it can be easily copied and pasted directly into a PowerShell prompt. In addition in the first line the current directory should be changed to the root of the drive so that the folder won't be created in the user's context.

Now:

PS C:\> mkdir agent ; cd agent
PS C:\agent> Add-Type -AssemblyName System.IO.Compression.FileSystem ;
[System.IO.Compression.ZipFile]::ExtractToDirectory("$HOME\Downloads\vsts-agent-win-x64-[AGENT_VERSION].zip", "$PWD")

Then:

cd \
mkdir agent ; cd agent
Add-Type -AssemblyName System.IO.Compression.FileSystem ;
[System.IO.Compression.ZipFile]::ExtractToDirectory("$HOME\Downloads\vsts-agent-win-x64-[AGENT_VERSION].zip", "$PWD")

[Warning 1]
Ubuntu 16.04 LTS environment is deprecated and will be removed on September 20, 2021. Migrate to ubuntu-latest instead. For more details, see actions/runner-images#3287.

So in 4 days this lab will give an error. Same for Lab 16

#Module 11: Implementing Continuous Deployment using Azure Pipelines

Lab/Demo: Lab: Setting Up and Running Functional Tests

Task: 2

Step: 1 to 4

Description of issue
Issue with Lab: Setting Up and Running Functional Tests Student lab manual while creating template.

In exercise 0, Task2:Create Azure resources, Step 4. Review + Create with the given details throwing error. The custom deployment is failing and unable to process further with the rest of the lab.

Below is the error message:
{"code":"InvalidContentLink","message":"Unable to download deployment content from 'https://gallery.azure.com/artifact/20161101/Microsoft.CustomScriptExtension-arm.2.0.50/Artifacts/MainTemplate.json'. The tracking Id is '2927f399-cd2e-476c-b4ac-992ff7f5be7d'. Please see https://aka.ms/arm-deploy for usage details."}

Repro steps:

1. Logged into lab.
2. After creating project, move to Step1 of Task2 in Exercise0. When we click the deploy to Azure button, it opens a custom deploy template in a new window outside the lab machine.
3. After filling the required details, when we click review+finish> Validation Fails with errors.
4. ERROR TYPE
   Unable to download deployment content from 'https://gallery.azure.com/artifact/20161101/Microsoft.CustomScriptExtension-arm.2.0.50/Artifacts/MainTemplate.json'. The tracking Id is '2927f399-cd2e-476c-b4ac-992ff7f5be7d'. Please see https://aka.ms/arm-deploy for usage details. (Code: InvalidContentLink)

Module: 05

Can't do the Microsoft-hosted agents related taks has Microsoft changed the policy on new free acccounts.
Can you do some edits on the steps

Information: https://devblogs.microsoft.com/devops/change-in-azure-pipelines-grant-for-private-projects/

Module: 10

Lab: 10a Controlling Deployments using Release Gates

Exercise: 02

Description of issue
The stage Canary Environment fails due to an issue with the task "Enable Continuous Monitoring", Error message is:

Error: Failed to enable continuous monitoring. Error: Error: Failed to update Application Insights 'PU234457724-Canary' Resource. Error: BadRequest - WorkspaceResourceId can be set only on api-version 2020-02-02 (CODE: 400)

This is also file as a task issue:
microsoft/azure-pipelines-tasks#14794

Module: 6

Lab/Demo: Enabling Continuous Integration with Azure Pipelines

Ex 1 Task 1

Step: 13

Some new devops organizations do not have retention tab on the pipeline edit view --> either delete those steps or add a note to tell students they can see it in "project settings" (PR proposing this option).

Module: several

Lab: several

Description of issue
Ubuntu 16.04 which will be removed September 20, 2021 (see actions/runner-images#3287). In some labs pipelines are configured using that version. Labs need to be tested with higher versions and instructions changed.

What should we change?

Compared to Lab 10a this lab 11a should be simplified by using AZ CLI commands for the cloud shell instead of letting users create everything in the portal. Especially the creation of the App Insights resource can be simplified if it would be done from the app service directly instead of letting them create it manually. The lab is already long enough and the focus should be on the release pipeline, not the creation of Azure Resources.

Lab

Lab 11a Configuring Pipelines as Code with YAML

Relevant screenshots

paste here 😉

Module: 01

Lab/Demo: 01 Lab: Agile Planning and Portfolio Management with Azure Boards

Task: 1 Configure que team project

Step: 1 On your lab computer, start a web browser and navigate to

Description of issue

Please fix the markdown on LODS, it's difficult to navigate to the Demo generator. If you click on the link it will open a new window on the local computer. Not on the LODS VM.
Would be great to add the T at the left to open the address inside the VM.

Repro steps:

1. On your lab computer, start a web browser and navigate to Azure DevOps Demo Generator. This utility site will automate the process of creating a new Azure DevOps project within your account that is prepopulated with content (work items, repos, etc.) required for the lab.

Module: 14

Lab/Demo: Deploying apps with Chef on Azure

Task: 01

Step: 01

Description of issue

https://gallery.azure.com is deprecated.

Repro steps:

Module: 11

Lab/Demo: 11b

Task: 02

Step: 01

Description of issue
Lab: 11b; Exercise: 0; Task: 02; Step: 01

While visualizing the markdown in a Web Browser the button redirecting to the Custom Deployment doens't work.

Repro steps:

1. Open Lab11b
2. Click the button: Deploy to Azure
3. The .png opens instead of the URI

Module: 11

Lab/Demo: Setting Up and Running Functional Tests

Task: 03

Step: 06

Description of issue:
"Once the Selenium test execution phase starts, monitor the web browser tests.", However user will likely to see this error
"[error]Cannot find appcmd.exe location. Verify IIS is configured on az40011bvm and try operation again."

Due to few issues with the Powershell script that sets up the VM.
https://raw.githubusercontent.com/microsoft/azuredevopslabs/master/labs/vstsextend/selenium/armtemplate/chrome_firefox_VSTSagent_IIS.ps1

#copy geckodriver
Invoke-WebRequest https://github.com/Microsoft/almvm/blob/master/labs/vstsextend/selenium/armtemplate/geckodriver.exe?raw=true -OutFile "C:\Program Files\Mozilla Firefox\geckodriver.exe"

This line could fail due to TLS certificate with Invoke-WebRequest command. Then the last line to install IIS will not run. User will see "[error]Cannot find appcmd.exe location. Verify IIS is configured on az40011bvm and try operation again." and can't see the Selenium test run in browsers.

Also the next section installs the local agent, the exe version is out of date and not needed, because we installed the agent earlier in Task 1, Configure a self-hosted Azure DevOps agent

Fix:

1. Fixed the potential TLS issue with the Invoke-WebRequest command or move the IIS install line to earlier location in the script.
2. Remove the section to install the outdated Agent exe.

Repro steps:

Module: 14

Lab/Demo: 01

Task: 04

Step: 03

Description of issue
Been trying to reproduce the lab, Ansible with Azure, a couple of times now and it failed to be reproduced.
What I've seen, is that if you install ansible using the apt command, subsequent tasks will fail. One, because version 2.5 is installed and it will fail here: "ansible-galaxy collection install azure.azcollection", and if ansible 2.9 is installed via apt command, it will fail at Task 8, Step 10, here: "ansible-playbook ~/PartsUnlimitedMRP/Labfiles/AZ-400T05-ImplemntgAppInfra/Labfiles/ansible/new_vm_web.yml --extra-vars "vmname=<VM_name> resgrp=az400m14l03arg vnet=az400m1403vm1VNET subnet=az400m1403vm1Subnet"".

Also I've changed the default version of python that is used and it worked; but I had to change the version in the commands where python2.7 string was found and replace it with 3.6

It was more troubleshooting than following the steps, but it was an experience.

Thanks.

Module: 1

Lab/Demo: Configuring Pipelines as Code with YAML

Description of issue

Attendees were not able to select ASP.NET template when creating a pipeline (it was taking the one on the repo by default)
YAML example given had some indentation issues.

Repro steps:

Module: 10

Lab/Demo: 10 Controlling deployments using release gates

Task: 2 configure post deployment gates

Step: 01

Description of issue
The instructions are not clear- all pipelines is the page but not helpful when not on the page. Additionally, the instructions say to go to the left oval for post deployment settings, and post deployment settings are on the right hand side of the rectangle.

Recommend explicit path to the pipeline and correct instructions on getting to the gate....

Repro steps:

Module: 06

Lab : Lab: Integrating External Source Control with Azure Pipelines

Task: Configuring your Azure Pipelines project

Step: 7 On the Summary tab of the build job’s pane, verify that the build completed successfully.

Description of issue:

The task doesn't complete successfully, instead students get the following error message:

Repro steps:

We completed the required Lab preparation and the billing is setup as follows:

However, students are still experiencing the issue. For the other labs while using Azure repos, pipelines can run without issues. The problem is just with GitHub, maybe change the project to Public to leverage the free tier?

Module: az-400

Lab/Demo: 15 & 16

Task: 00

Step: 00

Description of issue

In the Build task, from the CI pipeline, it looks for a microsft / aspnetcore: 1.0-2.0 image that no longer exists and prevents both labs from being able to start as soon as possible.
Repro steps:

Hi,

Are Modules 02 and 04 supposed to be duplicates of one another?

Module: 01

Lab/Demo: 01

Task: 03

Step: 11

Description of issue

instructions is not clear set the estimated number all of the time attendees look for this feature but its just out their.
refer it as square box or something.

On the Taskboard tab of the Sprints view, in the rectangle 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.

Repro steps: