Last Updated on August 7, 2025 by Arnav Sharma
Azure DevOps offers multiple access levels, with each one designed to meet the varying needs of users within an organization. The two most common access levels are “Stakeholder” and “Basic.”
Here’s a breakdown of their differences:
Stakeholder Access Level
- Purpose: The Stakeholder access level is designed for users who need to view and interact with Azure DevOps but don’t need access to the core set of developer-related features. This is often suitable for project managers, business analysts, and other non-technical team members.
Cost: Stakeholder access level is free.
Features:
- Boards: Stakeholders can create and edit work items. They can also view boards, backlogs, sprints, and queries.
- Dashboards: View dashboards to get insights into project progress.
- Wiki: Stakeholders can read project wikis but cannot edit them.
- Pipelines: View the status of builds and releases.
Limitations:
- Cannot access Repos (Version control) features.
- Cannot execute tests or view test results.
- No access to Artifacts (Package feeds).
- Limited access to other Azure DevOps features that are more developer-centric.
Basic Access Level
- Purpose: The Basic access level is meant for users who are more involved in the software development process and need access to developer-centric features like repositories, CI/CD, etc.
- Cost: Unlike the Stakeholder access, the Basic access level comes with a cost, but Microsoft often provides a number of free Basic licenses depending on your subscription type.
Features:
- Boards: Full access to create, edit, and manage work items, boards, backlogs, sprints, and queries.
- Repos: Access to version control features. Users can clone, fetch, push, and create pull requests.
- Pipelines: Use CI/CD features. Set up builds, releases, and view their statuses.
- Wiki: Can both read and edit wikis.
- Artifacts: Can access and manage package feeds.
- Test Plans: Available as an additional purchase. Allows for comprehensive test planning and execution.
Limitations:
- Some advanced features, like Test Plans, might require additional purchases.
DevOps Pricing Calculator:
Azure DevOps Services Pricing | Microsoft Azure
To update the Billing:

I help organisations secure their cloud infrastructure and stay ahead of evolving cyber threats. Microsoft MVP and Certified Trainer, author of Mastering Azure Security, and founder of arnav.au — a platform for practical Cloud, Cybersecurity, DevOps and AI content.
Frequently Asked Questions
Stakeholder access is designed for non-technical team members like project managers and business analysts who need to view and interact with work items and dashboards but don't require developer features. Basic access is meant for developers and those involved in the software development process who need full access to repositories, CI/CD pipelines, and version control features.
Yes, Stakeholder access is completely free, while Basic access comes with a cost. However, Microsoft typically provides a certain number of free Basic licenses depending on your subscription type, so you may not need to pay for all Basic users.
No, Stakeholders cannot access the Repos (version control) features. This limitation is intentional, as Stakeholder access is designed for non-developers who don't need to interact with code repositories, clone projects, or create pull requests.
Stakeholders can read and view project wikis but cannot edit or modify them. In contrast, Basic users have full read and write access to wikis, allowing them to create, edit, and manage wiki content.
Stakeholders can view the status of builds and releases to get insights into project progress, but they cannot set up, configure, or execute CI/CD pipelines. Basic users have full access to use CI/CD features, including setting up builds, releases, and managing pipeline configurations.