title: Handling mulitiple servers in a Azure DevOps release pipeline stage
body: <p>I have a question on Azure DevOps Release pipelines. My pipeline workflow is multi-stage where the build triggers the QA stage which then triggers the UAT stage which then triggers the PROD stage.</p>
  <p>I use pipeline variables to manage each stage and require pre-approval on the UAT and PROD stages so that a change does not instantly get deployed to every stage sequentially.</p>
  <p>My question is how to handle the case where I have multiple servers in an environment. I see that each environment should be treated as a stage but right now, I am treating each server in an environment as a stage where the tasks are run in parallel. This works for the first stage (QA), but becomes ugly for UAT since each server then requires pre-approval instead of the environment.</p>
  <p>I have pipeline variables that specify paths for files to be dropped on servers as well. At a server per stage level, this works but not for multiple servers in a stage.</p>
  <p>My pipeline currently looks like the picture below with UAT1 and UAT2 each requiring approval. How do I handle multiple servers for the QA and UAT stages, and later PROD?</p>
  <p><a href="https://i.stack.imgur.com/sBiJI.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/sBiJI.png" alt="enter image description here" /></a></p>