Answers: <p>You could apply tags to the targets (e.g. Active) and use that as a filter in the stage tasks.</p>
  
Answers: CC BY-SA 4.0
Answers: 2023-10-13T18:32:22.333Z
Answers: Yeah, ended up doing exactly that, adding Online tags to the currently online machines before every deployment
Answers: Exhodus
Answers: CC BY-SA 4.0
Answers: 2023-10-05T16:53:37.407Z
Answers: 2023-10-05T16:53:37.407Z
Answers: geeky_girl
Body: <p>I'm currently using Azure DevOps for CI/CD and have set up a deployment group with multiple target machines. Some of these machines are scheduled to go offline during the night . However, I've noticed that when even one of these machines is offline, my release pipeline fails to deploy to the entire group, including the online machines. The error message I receive is: &quot;Deployment Group deployment configuration settings are not met.&quot;</p>
  <p>My goal is to have the release pipeline deploy successfully to the online machines, even if some machines in the deployment group are offline.</p>
  <p>Is there a configuration setting or workaround in Azure DevOps to handle this scenario?
  How can I ensure that the pipeline continues to deploy to online machines without being halted by offline ones?
  Any insights or solutions would be greatly appreciated. Thank you!</p>
  
Tags: <azure-devops>
Title: Azure DevOps Release Pipeline Fails on Partially Offline Deployment Group
UserDisplayName: Exhodus
ThreadText: # Azure DevOps Release Pipeline Fails on Partially Offline Deployment Group
  
  (Asked by: username_0 on 2023-10-02)
  
  I'm currently using Azure DevOps for CI/CD and have set up a deployment group with multiple target machines. Some of these machines are scheduled to go offline during the night . However, I've noticed that when even one of these machines is offline, my release pipeline fails to deploy to the entire group, including the online machines. The error message I receive is: "Deployment Group deployment configuration settings are not met."
  
  My goal is to have the release pipeline deploy successfully to the online machines, even if some machines in the deployment group are offline.
  
  Is there a configuration setting or workaround in Azure DevOps to handle this scenario?
  How can I ensure that the pipeline continues to deploy to online machines without being halted by offline ones?
  Any insights or solutions would be greatly appreciated. Thank you!
  
  **Tags:** azure-devops
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-10-05. Score: 0 | Accepted answer
  
  You could apply tags to the targets (e.g. Active) and use that as a filter in the stage tasks.
  
  > **Comments:**
  > **username_0**: Yeah, ended up doing exactly that, adding Online tags to the currently online machines before every deployment  
  
  ---
  
  