AZ-400 ยท Identity, access and permissions
Azure DevOps groups and access levels
Security groups and inheritance, Stakeholder/Basic/Basic+Test Plans access levels, project and team design, area and iteration paths, organization settings.
Key points
- Security groups set Allow, Deny or Not set, inherited down scopes; at the same scope Deny generally wins.
- Access levels (Stakeholder, Basic, Basic + Test Plans, Visual Studio subscriber): web features, billing.
- Stakeholder: free, limited.
- Project Administrators: teams, area and iteration paths, service endpoints.
- Project Collection Administrators: projects, policies, pools.
Practice questions
Which access level can be assigned to an unlimited number of users at no charge, with limited features?
- Stakeholder
- Basic
- Basic + Test Plans
- Project Administrators
Show answer
Answer: A. Stakeholder
Stakeholder is free and limited, meant for people who need a restricted set of features such as viewing work items and dashboards. Basic and Basic + Test Plans are paid or subscription-backed.
In a private project, which things can a Stakeholder do?
- View builds
- Act on release approvals assigned to them
- Change the State field of cards on a board
- Create and edit build pipelines
- Author release pipelines
Show answer
Answer: A. View builds, B. Act on release approvals assigned to them, C. Change the State field of cards on a board
Stakeholders can view builds, view releases and act on approvals assigned to them, and change the State of cards on boards. They cannot create or edit build pipelines or author release pipelines.
If one group Allows a permission and another group the user belongs to Denies it at the same scope, the Allow wins.
Show answer
Answer: False
False. At the same scope a Deny generally takes precedence over an Allow, while Not set neither grants nor denies.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
