Ability to Trigger a Specific Stage in a Release Pipeline via az pipelines release create

[KouShIkkkkkkkk]

We are currently using the az pipelines release create command to automate our release pipeline triggers. However, this command always triggers the entire release pipeline, starting from the first stage. Our use case requires more granular control — specifically, the ability to trigger a specific stage in an existing release pipeline (using a specific artifact version), without executing the earlier stages.

Use Case

In our setup, we have a multi-stage release pipeline where each stage corresponds to a distinct environment (e.g., Dev, QA, UAT, Prod). We often need to:

Promote a specific artifact version directly to a downstream stage (e.g., UAT or Prod)

Avoid re-running earlier stages unnecessarily

Trigger stage-specific deployments through automation/scripts

Current Limitation
The current az pipelines release create command does not support:
Specifying a stage to start the release from
Targeting a stage in a previously created release

Feature Request

We would like to request support for either of the following in the Azure CLI:

1. An optional parameter (e.g., --stage or --target-stage) that allows users to specify the starting stage during release creation.

2. Or a new command/sub-command that allows triggering a specific stage of an existing release.

Workaround (not ideal)

Manually starting a stage from the Azure DevOps UI is the current workaround, but this breaks automation flows and increases manual overhead.

[yonzhan]

Thank you for opening this issue, we will look into it.

[KouShIkkkkkkkk]

Hi, any update on this feature?