Skip to content
Open
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions docs/pipelines/security/inputs.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Securely use variables and parameters
description: Find out how to safely accept input from pipeline users in Azure Pipelines.
ms.date: 08/15/2025
ms.date: 05/12/2026
monikerRange: "<=azure-devops"
#customer intent: As an Azure Pipeline administrator, I want to understand how to securely accept user input so I can avoid security risks from variable and parameter usage in my pipelines.
ms.topic: best-practice
Expand Down Expand Up @@ -121,12 +121,18 @@ Pipelines can reference tasks executed within the pipeline. Some tasks include a

Applying the **Enable shell tasks arguments validation** setting validates `argument` parameters for built-in shell tasks to check for inputs that can inject commands into scripts. The check ensures that the shell correctly executes characters like semicolons, quotes, and parentheses in the following pipeline tasks:

- PowerShell
- PowerShell

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@copilot apply changes based on this feedback

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Fixed in 68bc6e3 — changed argument to arguments (plural) on line 122 so it matches the surrounding text and the actual task input name.

- BatchScript
- Bash
- Bash
- Ssh
- AzureFileCopy
- WindowsMachineFileCopy
- PowerShellOnTargetMachines
- SqlAzureDacpacDeployment
- SqlDacpacDeploymentOnMachineGroup
- AzureCLI
- AzurePowerShell
- ServiceFabricPowerShell

You can apply **Enable shell tasks arguments validation** at the organization level under **Organization Settings** > **Pipelines** > **Settings** or at the project level under **Project settings** > **Pipelines** > **Settings**. If the organization-level setting is enabled, it applies to all projects in the organization and can't be turned off at the project level.

Expand Down