Azure DevOps group rules.

Schifter, Gabriela 75 Reputation points
2024-04-16T19:52:58.84+00:00

We are encountering an issue in Azure DevOps where some users are getting downgraded to ‘Stakeholder’ even though they are in ‘Basic’ groups. We have rerun the ‘group rules’ but this did not resolve the issue. Several that have reported the issue were working fine yesterday but encountered this issue today. We are wondering if anything has changed in Azure DevOps that would be causing this issue. We can manually change them to ‘Direct’ but that is a manual process and not good in the long run as licensing will no longer be automatically cleaned up. Please let us know if you have any thoughts on this or if any other customers are reporting this issue

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,080 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Marcin Policht 10,845 Reputation points MVP
    2024-04-16T20:12:45.0333333+00:00

    Basic and Stakeholder are access levels - not groups.

    If you are implementing them through Group Rules, then this should be applied automatically the first time a user signs in to Azure DevOps. You might want to review your existing Group Rules.

    I haven't experienced the behavior you are describing. Considering that this is a one-time assignment, it might make sense to simply go through this manually (depending on the size of your environment).


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    0 comments No comments