Skip to content

Conversation

@afelix-95
Copy link
Contributor

@afelix-95 afelix-95 commented Aug 14, 2025

Intermediate:

  • Minor UI nav steps updated.
  • Replaced "click" with "select".
  • Updated lab 04 duration to 60 minutes, mostly due to multiple provisioning steps waiting periods that add up in the end.
    Advanced:
  • UI nav steps updated.
  • Replaced "click" with "select".
  • Issues with labs 06 and 08:
    • Lab 06 - Task: Configure the application to use App Configuration - Connection strings are added differently now, and the app doesn't seem to recognize the connection in the following task, so dynamic configuration and feature flags don't work.
    • Lab 08 - Task: Automate Load Test with CI/CD in Azure Pipelines - Service connection seems to be glitched, as it won't have the option of managing roles available, blocking the task Update the CI/CD workflow YAML definition file.

@LuizMacedo LuizMacedo requested a review from Copilot August 21, 2025 03:11

This comment was marked as outdated.

@afelix-95 afelix-95 changed the title Update intermediate labs Update intermediate and advanced labs Aug 22, 2025
@LuizMacedo LuizMacedo requested a review from Copilot August 29, 2025 02:00
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates intermediate and advanced Azure DevOps lab instructions to improve user experience by standardizing UI navigation terminology and addressing known issues. The changes primarily replace "click" with "select" throughout the documentation for more professional and accessible language, and update some specific UI navigation paths that have changed.

Key changes include:

  • Standardized terminology from "click" to "select" across all lab instructions
  • Updated Lab 04 duration from 30 to 60 minutes to reflect actual completion time
  • Fixed minor UI navigation inconsistencies and updated deprecated interface paths

Reviewed Changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
Instructions/intermediate/09-package-management-azure-artifacts.md Updated "click" to "select" throughout and corrected step numbering in package creation section
Instructions/intermediate/08-set-up-run-functional-tests.md Standardized UI interaction terminology and fixed pipeline save instruction
Instructions/intermediate/07-deploy-docker-containers-azure-app-service.md Updated terminology and corrected Azure portal navigation paths
Instructions/intermediate/06-implement-github-actions-ci-cd.md Replaced "click" with "select" and updated GitHub UI references
Instructions/intermediate/05-enable-continuous-integration-azure-pipelines.md Standardized terminology throughout Azure DevOps navigation
Instructions/intermediate/04-configure-agent-pools-pipeline-styles.md Updated lab duration and fixed minor wording
Instructions/intermediate/02-implement-microsoft-dev-box.md Updated Microsoft Entra admin center navigation paths
Instructions/intermediate/01-implement-ci-cd-with-github-actions-and-iac-with-bicep.md Updated region references and terminology
Instructions/advanced/08-monitor-application-performance-azure-load-testing.md Standardized terminology and updated pipeline configuration steps
Instructions/advanced/07-deployments-azure-bicep-templates.md Updated UI interaction terminology throughout
Instructions/advanced/06-enable-dynamic-configuration-feature-flags.md Added service connection setup and updated Azure portal navigation
Instructions/advanced/05-integrate-azure-key-vault-azure-devops.md Added service connection configuration and updated terminology
Instructions/advanced/04-control-deployments-release-gates.md Standardized UI terminology and updated Azure portal references
Instructions/advanced/03-configure-pipelines-code-yaml.md Updated terminology and Cloud Shell setup instructions
Instructions/advanced/02-implement-self-service-infrastructure-bicep.md Updated lab duration and fixed storage account naming
Instructions/advanced/01-enhance-workload-traffic-manager-test-azure-chaos-studio.md Simplified deployment parameters and added error handling guidance

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

- **resource-group**: the name of the resource group, for example **rg-az400-container-NAME** (replace NAME)
- **location**: the name of the Azure region, for example **southcentralus**
- **templateFile**: **'infra/webapp.bicep'**
- **templateFile**: **'webapp.bicep'**
Copy link

Copilot AI Aug 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The templateFile path has been changed from 'infra/webapp.bicep' to 'webapp.bicep', but this appears to be inconsistent with the repository structure mentioned earlier which indicates templates are in the 'infra' folder. This change should be verified to ensure the file path is correct.

Suggested change
- **templateFile**: **'webapp.bicep'**
- **templateFile**: **'infra/webapp.bicep'**

Copilot uses AI. Check for mistakes.
--parameters webAppName=eshoponweb-eastus-$(uuidgen)-$(date +%s) \
sku=F1 \
linuxFxVersion="DOTNETCORE|8.0"
--parameters webAppName=eshoponweb-eastus-XXXX sku=S1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@afelix-95 here we can leave the automated way of generating the name:
--parameters webAppName=eshoponweb-eastus-$(uuidgen)-$(date +%s)

, and update only the SKU to S1 as you suggested. No needed for the XXXX add in the description and resource name.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed it because when running the command in cloud shell, it returns an error message that the name is not valid due to the final web app name having more than 24 characters.

--parameters webAppName=eshoponweb-westus-$(date +%s%N) \
sku=F1 \
linuxFxVersion="DOTNETCORE|8.0"
--parameters webAppName=eshoponweb-westus-XXXX sku=S1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as the above comment, you can keep the random webAppName=eshoponweb-eastus-$(uuidgen)-$(date +%s)

### Configure the target environment

> **Note:** You will start by creating the resource groups. You will run the workflow twice in order to deploy two instances of the website in two different Azure regions (East US and West US in this example). You can adapt these to use regions closer to your location if preferred.
> **Note:** You will start by creating the resource groups. You will run the workflow twice in order to deploy two instances of the website in two different Azure regions (East US and West Europe in this example). You can adapt these to use regions closer to your location if preferred.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, revert. The regions are correct, West US and East US.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While the instructions said West US and the resource group created referenced West US, the pipeline and code snippets for the web app reference West Europe. Should I change it all to West US or leave them mixed as they were before?

1. On the **Resource groups** page, select **+ Create**.
1. In the **Resource groups** text box, enter **`rg-eshoponweb-westus`**.
1. In the **Region** drop-down list, select **(US) West US**.
1. In the **Resource groups** text box, enter **`rg-eshoponweb-westeurope`**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, revert. The regions are correct, West US and East US.

1. In the **Resource groups** text box, enter **`rg-eshoponweb-westus`**.
1. In the **Region** drop-down list, select **(US) West US**.
1. In the **Resource groups** text box, enter **`rg-eshoponweb-westeurope`**.
1. In the **Region** drop-down list, select **(Europe) West Europe**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, revert. The regions are correct, West US and East US.

```yaml
RESOURCE-GROUP: rg-eshoponweb-westus
RESOURCE-GROUP: rg-eshoponweb-westeurope
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, revert. The regions are correct, West US and East US.

@LuizMacedo LuizMacedo requested a review from Copilot September 12, 2025 20:10
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Copilot reviewed 16 out of 16 changed files in this pull request and generated 2 comments.


Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants