Answers: <p>We figured this out. The deployment group was created by someone else and I had only been granted Reader and not User permissions for the group.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-12-30T16:33:40.063Z
Answers: 2021-12-30T16:33:40.063Z
Answers: Chris
Body: <p>I am trying to follow these instructions:
  <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/apps/cd/deploy-webdeploy-iis-deploygroups" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/azure/devops/pipelines/apps/cd/deploy-webdeploy-iis-deploygroups</a></p>
  <p>I get to step 6 under &quot;Define your CD release pipeline&quot; and get stuck. I have a Deployment group created and can see my Windows VM in the groups targets. DevOps says that the target is online. But when I'm in the pipeline editor and trying to select the deployment group for the IIS Deployment job, no deployment groups appear in the dropdown. When I type in the name of my deployment group it just says &quot;Deployment Group does not exist&quot;. Does anyone know why my deployment group is not detected?</p>
  
Tags: <azure-devops><azure-pipelines>
Title: Deployment group not showing in Azure DevOps release pipeline
UserDisplayName: Chris
ThreadText: # Deployment group not showing in Azure DevOps release pipeline
  
  (Asked by: username_0 on 2021-12-29)
  
  I am trying to follow these instructions:
  <https://docs.microsoft.com/en-us/azure/devops/pipelines/apps/cd/deploy-webdeploy-iis-deploygroups>
  
  I get to step 6 under "Define your CD release pipeline" and get stuck. I have a Deployment group created and can see my Windows VM in the groups targets. DevOps says that the target is online. But when I'm in the pipeline editor and trying to select the deployment group for the IIS Deployment job, no deployment groups appear in the dropdown. When I type in the name of my deployment group it just says "Deployment Group does not exist". Does anyone know why my deployment group is not detected?
  
  **Tags:** azure-devops, azure-pipelines
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2021-12-30. Score: 4 | Accepted answer
  
  We figured this out. The deployment group was created by someone else and I had only been granted Reader and not User permissions for the group.
  
  
  ---
  
  