Currently, when configuring a pipeline stage with the option “Deploy to multiple Environments or Infrastructures”, the environment selection supports only Fixed Input and Runtime Input. Expression-based values using pipeline variables are not supported in this mode. This limitation makes it difficult to dynamically reuse pipelines across different deployment scenarios, as environments cannot be resolved through expressions derived from pipeline variables, inputs, or execution context. Ideally, the environment field should also support expression-based inputs, allowing teams to dynamically determine the target environment at runtime without duplicating stages or pipelines. Adding expression support would greatly improve pipeline flexibility and reusability, reduce configuration duplication, simplify maintenance, and enable more scalable deployment strategies for teams operating across multiple environments, accounts, or regions.
