Error 500 When Creating Azure DevOps Security Group with az devops security group create - Stack Overflow

I am trying to add Azure AD group in Azure DevOps using the az devops security group create command, bu

I am trying to add Azure AD group in Azure DevOps using the az devops security group create command, but I am encountering a 500 status code error. Here’s what I have attempted:

Command with Project Collection Valid Users:

az devops security group create --origin-id 'object ID from AD' --groups 'vssgp.wwwwww' --scope anization -- '/'

Command with a custom group name:

az devops security group create --origin-id 'object ID from AD' --groups 'vssgp.devlopergrp' --scope "anization" -- '/'

Result: Operation returned a 500 status code.

Since the AD Group is being added to the Azure devops for the first time, it doesn't have a descriptor.

I have verified that:

  • The Object ID from AD is correct.
  • The Azure DevOps CLI is authenticated and working for other commands.
  • The anization URL is valid.
  • The descriptor of the Project Collection Valid Users is correct
  • I have Project Collection Administrator Permission on Azure DevOps.

What could be causing this issue, and how can I successfully create the group?

I am trying to add Azure AD group in Azure DevOps using the az devops security group create command, but I am encountering a 500 status code error. Here’s what I have attempted:

Command with Project Collection Valid Users:

az devops security group create --origin-id 'object ID from AD' --groups 'vssgp.wwwwww' --scope anization -- 'https://dev.azure/my-/'

Command with a custom group name:

az devops security group create --origin-id 'object ID from AD' --groups 'vssgp.devlopergrp' --scope "anization" -- 'https://dev.azure/my-/'

Result: Operation returned a 500 status code.

Since the AD Group is being added to the Azure devops for the first time, it doesn't have a descriptor.

I have verified that:

  • The Object ID from AD is correct.
  • The Azure DevOps CLI is authenticated and working for other commands.
  • The anization URL is valid.
  • The descriptor of the Project Collection Valid Users is correct
  • I have Project Collection Administrator Permission on Azure DevOps.

What could be causing this issue, and how can I successfully create the group?

Share Improve this question edited Jan 17 at 15:56 Rui Jarimba 18.2k11 gold badges64 silver badges98 bronze badges asked Jan 17 at 15:51 Nyamat Allah Noorahmad MominNyamat Allah Noorahmad Momin 11 bronze badge 3
  • Any other details in the error message? – Rui Jarimba Commented Jan 17 at 15:57
  • No, only below error Operation returned a 500 status code. – Nyamat Allah Noorahmad Momin Commented Jan 18 at 16:14
  • Consider adding the --verbose and/or --debug options to your commands - see Be aware of globally available arguments. – Rui Jarimba Commented Jan 18 at 16:27
Add a comment  | 

2 Answers 2

Reset to default 0

I can reproduce the same 500 error when trying to add an AAD group to Project Collection Valid Users group. If you add an AAD group manually to this group, you will get the same 500 error in the UI.

According to the official doc, this group contains all users and groups added anywhere within the collection. You can't modify the membership of this group. That is why you get 500 error.

It's suggested that you add your AAD group to other groups at anization level, whether a built-in group or your custom group.

I am trying to add the Azure AD group in the Organization's Project Collection Valid User and I am able to add from the portal.

Adding the group:

Group added:

If I use the descriptor of the Project Collection Valid Users, I'm getting the below error.

发布者:admin,转转请注明出处:http://www.yc00.com/questions/1745356920a4624174.html

相关推荐

发表回复

评论列表(0条)

  • 暂无评论

联系我们

400-800-8888

在线咨询: QQ交谈

邮件:admin@example.com

工作时间:周一至周五,9:30-18:30,节假日休息

关注微信