From 1655bd830cd8ba1dc6a2d0bb5a4bb52eae4cb4f1 Mon Sep 17 00:00:00 2001
From: phil <22167066+philippesollaud@users.noreply.github.com>
Date: Thu, 8 Jan 2026 11:29:23 +0100
Subject: [PATCH] Modify build task to use arguments for configuration

Updated instructions to use 'arguments' input for build configuration.
---
 ...gure_Pipelines_to_Securely_Use_Variables_and_Parameters.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Instructions/Labs/APL2001_M07_L07_Configure_Pipelines_to_Securely_Use_Variables_and_Parameters.md b/Instructions/Labs/APL2001_M07_L07_Configure_Pipelines_to_Securely_Use_Variables_and_Parameters.md
index 316aaa0..ab622e2 100644
--- a/Instructions/Labs/APL2001_M07_L07_Configure_Pipelines_to_Securely_Use_Variables_and_Parameters.md
+++ b/Instructions/Labs/APL2001_M07_L07_Configure_Pipelines_to_Securely_Use_Variables_and_Parameters.md
@@ -145,12 +145,12 @@ In this task, you will secure the variables and parameters from your pipeline by
      - group: BuildConfigurations
    ```
 
-1. In the "Build" task, add the configuration parameter to the task to utilize the build configuration from the variable group.
+1. In the "Build" task, add the arguments input with the configuration parameter to the task to utilize the build configuration from the variable group.
 
     ```yaml
             command: 'build'
             projects: ${{ parameters.dotNetProjects }}
-            configuration: $(buildConfiguration)
+            arguments: '--configuration $(buildConfiguration)'
     ```
 
 1. Click on **Validate and save** to save the changes, then click on **Save**.