Azure DevOps Reviews and Ratings

Rating: 8.1 out of 10

Score

8.1 out of 10

Community insights

TrustRadius Insights for Azure DevOps are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Customizable Scrum Board: Users have appreciated the scrum-like board in Azure DevOps for its high level of customization options, enabling them to tailor it according to their specific project requirements and team preferences. This flexibility allows teams to adapt the board layout, columns, and cards based on their unique Agile methodologies.

Efficient Test Cases Management: Many users have found the Test Cases storage feature in Azure DevOps beneficial for efficiently managing testing processes within their projects and streamlining test case organization and execution. By centralizing test cases within the platform, teams can easily track testing progress, link tests to user stories or features, and ensure comprehensive test coverage.

Seamless CI/CD Pipelines: Users highly value Azure DevOps for its exceptional ease in creating build and deploy pipelines, strong GitHub integration, robust support for continuous integration and continuous deployment processes, contributing to smoother development workflows. The seamless pipeline creation process includes built-in connectors for Azure services, simplifying pipeline setup and enabling automated deployments with minimal manual intervention.

Reviews

74 Reviews

Azure DevOps for Tech Team and LD Teams

Rating: 9 out of 10

Incentivized

January 28, 2026

Use Cases and Deployment Scope

We use Azure DevOps to track work from our Dev Team and manage projects in one shared place.<div>

</div><div>It helps solve problems like unclear progress, scattered updates across email or Slack, and difficulty tracking timelines. Teams can easily see what’s being worked on, what’s coming next, and when tasks are expected to be completed.</div><div>

</div><div>Operations, Marketing, and other teams use it to submit requests, follow delivery plans, and collaborate in one system. This improves visibility, reduces back-and-forth updates, and keeps everyone aligned on priorities and timelines.</div>

Pros

We have Release Notes from Dev of the current feature update or bug fixes. These notifications have added links to Azure DevOps to provide complete details of the new feature.
Delivery plan section is useful for strategic planning. It helps stakeholders see the big picture: what’s being delivered, by when, and what value it unlocks.
I am from the training team and Azure DevOps is used by our tech team mostly so details of the feature I want to train our people is in there. Helps with training content creation.

Cons

At first its overwhelming especially when you first log in you will only see projects created by our tech team then after you get into that projects there are boards, work items, queries etc so it can be a bit overwhelming.
For beginners and probably non-tech team it's hard to use.
Their knowledge base might need improvement as well

Likelihood to Recommend

I would say if you are a tech company or a software provider and you have other departments like Operations, Call Centers, Marketing, Finance then Azure DevOps is well suited for you because boards help teams and stakeholders see what’s being worked on, its status, and who’s responsible. For us in L&D we use Azure DevOps to understand more about the new feature release from our Tech Team.

Verified User

Supervisor in Information Technology (201-500 employees)

Vetted Review

1 year of experience

Mature product with helpful marketplace

Rating: 10 out of 10

Incentivized

January 28, 2026

Use Cases and Deployment Scope

We use Azure DevOps for our build and deployment pipelines. This includes building mobile applications for iOS and Android platforms and uploading these to the respective platform stores.

Pros

Is a mature CI/CD environment
Has many helpful marketplace applications
Is easy to maintain and work with

Cons

Yaml syntax can be hard to work with
Convertion of visual implementations converted to yaml is not always intuitive
Release pipelines are not automatically a part of the source repository, which means you have to export this for backup and versioning.

Likelihood to Recommend

It is easy to get started with creating your own pipelines, either from starter examples or from scratch. By the use of the mature marketplace functions, almost any functionality is available which means you do not need to implement your own methods/functionality for most tasks you can imagine. This is especially helpfull, when you are new to implementing build and release pipelines.

Verified User

Engineer in Information Technology (201-500 employees)

Vetted Review

5 years of experience

Azure DevOps FTW

Rating: 10 out of 10

Incentivized

January 25, 2026

Use Cases and Deployment Scope

We use Azure DevOps as the main place we run delivery across a mix of internal transformation work and programmes. It’s basically our main system for planning work, tracking progress, and keeping teams aligned. Not just developers either, the PMs, BAs and leads are all in there. The biggest problems it helps with are visibility and coordination. We’ve got multiple workstreams running at the same time, often across different teams and sometimes suppliers, and without a single tool things quickly turn into spreadsheets and status chasing. Azure DevOps gives us one place to see what’s actually happening, what’s blocked, and what’s coming next, even if it’s not perfect. Our use case is more delivery and programme focused than “pure” software engineering. We use Boards a lot for epics, features and stories, sprint planning, and basic reporting. Repos are used where we’re doing active development, but it’s not the main thing for us. It’s not always the most intuitive tool and we don’t use every feature, but it does a solid job of keeping work structured and giving leadership a view without loads of manual updates.

Pros

It’s very good at breaking big, messy programmes down into epics, features and stories so you can actually see what needs doing and in what order.
Sprint planning and backlog prioritisation work well once teams get into a rhythm, especially when you’re juggling multiple workstreams at the same time.
The ability to link work items together makes dependencies and blockers much more visible than trying to manage them in spreadsheets.
It scales well as programmes grow, so you don’t have to completely change tooling once a small project turns into something much bigger.

Cons

Customising workflows and fields is powerful but not very user-friendly, and small changes can feel more complex or risky than they need to be.
The learning curve for new users is quite steep, and it usually needs proper onboarding rather than people just picking it up as they go.
It's not as pretty or intuitive as tools like monday.com - GANTT and waterfall are espsecially hard as the tool isn't designed for this.

Likelihood to Recommend

Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.

Tim Kikke

Head of PMO in Information Technology at Kerv (501-1000 employees)

Vetted Review

5 years of experience

Verified on LinkedIn

Azure DevOps - good enough but can still be improved

Rating: 7 out of 10

Incentivized

January 20, 2026

Use Cases and Deployment Scope

Azure DevOps has been a central core component in our daily processes. We use it not just to hold the code we write, but also to have some automations during the code review process whether it is through the automated tasks that should run to validate work or if it is just by the automated replies from the bot. Azure DevOps can also be responsible for deploying our tools when the right pipeline is triggered - either manually or via some automated criteria.

Pros

Pipeline executions
Agentic code review comments
Code review process
Automated tasks
Build validation

Cons

The customization of Pull Request default messages
A manual trigger for the pipelines to only continue a pipeline when we explicitly want - instead of having something waiting for approval.
Dynamics on the arguments passed to a pipeline when manually running it

Likelihood to Recommend

Not being able to customize the default pull request message is quite annoying given its simplicity it looks like to be. Also, having just a timed “waiting for approval” stage doesn’t sound ideal to me. It would be nicer to have a stage that can be triggered manually at any time after all the previous stages were completed. I mean, why do we need to have the pipeline waiting for something that we’re not likely to run unless we really want?

Verified User

Engineer in Information Technology (10,001+ employees)

Vetted Review

3 years of experience

DevOps helps our dev team coordinate deploy and saves us money

Rating: 8 out of 10

Incentivized

May 19, 2025

Use Cases and Deployment Scope

We use Azure DevOps to coordinate our implementation of development changes and technical processes (configurations / setups) for Business Central. First we create a master document listing all the modifications / extensions from a functional standpoint (master), then have individual tasks with tech design and hours assigned. Each time code with Git is sync'd and merged between one or more developers for the monolith extension app, it is tracked with the task assigned. Finally, as each task is worked through the status is updated and sync'd with the time keeping system (F&O) with PowerAutomate. This gives insight into the progress vs. hours consumed vs. original estimate in real time.

Pros

Utilize Git as a repository to share work between multiple users
Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
Track status of each task
Integrate with Git to utilize branches, merging, approvals, history, etc.

Cons

Have better project management to also be used with functional implementation rather than just development
Have the ability to integrate with a customer facing interface to give visibility into the project status and components.
Smoother integration into time keeping systems such as F&O or Business Central for overall project management reporting / accounting

Likelihood to Recommend

DevOps is much more user friendly than Git itself. There is a more GUI-centric interface, tighter integration with the Azure / Entra architecture. For those of use in the Microsoft-sphere, it really is excellent for code-centric project management. I rate this as an 8 because it does not seem quite as well suited for fully functional / non-code project aspects in implementation. Nor does it have customer / end-user portal / front end for easy reporting and insight.

Chris Studebaker

Technical Architect in Engineering at Enavate (201-500 employees)

Vetted Review

Reseller

7 years of experience

Verified on LinkedIn

Azure DevOps Services for project management

Rating: 9 out of 10

Incentivized

May 19, 2025

Use Cases and Deployment Scope

Azure DevOps Services for me is a one stop solution for managing my project work. With managing what i emphasize on if regular creation and maintenance of user stories on how and where is project headed to, bugs maintenance, team retrospective, source control management for codes and last but not the least continuous integration and deponent of my code to production

Pros

Continuous integration
Continuous deployment
User stories creations
Bug tracking

Cons

Cost
Provide its Training
External tools integration

Likelihood to Recommend

It can be best suited for projects that jave extensive relying on Microsoft projects and it can seamlessly Integrate with Microsoft active directory.

Another work scenario suited best could be if the project is agile development, Azure DevOps Services gives a lot of tools and it's services that could proce efficient for agile projects such as boards, retrospectives etc.

Hitesh Gautam

Cloud engineer in Information Technology at Insight (1001-5000 employees)

Vetted Review

4 years of experience

View profile

Good for general software delivery

Rating: 8 out of 10

Incentivized

October 9, 2024

Use Cases and Deployment Scope

We use Azure DevOps Services to track our digital project from starting to finish. We need a platform to track all the epics, features, user stories, defects and other relevant task for general agile practice. We also need the platform to be integrate with our repository and pipeline so that we could automate the deployment.

Pros

Customization on fields under user stories
Repository and Peer review can be done easily

Cons

It's hard to track the overall progress of peer review on the new changes
Cannot manage piles of work before starting of development during the problem discovery stage

Likelihood to Recommend

It is suitable for organization looking to automate their software deployment and want a good integration for developer.

Not so well to track items from business' lens as the functionality is heavily IT driven.

Stanley Chan

Digital Product Owner in Product Management at Bupa ANZ (10,001+ employees)

Vetted Review

5 years of experience

Great tool for digital product management

Rating: 8 out of 10

Incentivized

October 1, 2024

Use Cases and Deployment Scope

We use Azure DevOps for all our digital projects. It helps with organizing features and work with the development team. We have an overview of the sprints and it helps knowing where we are and where we are going.

Pros

Sprint planning
Feature development
Visual representation of digital projects

Cons

New items not showing in board, unless you click on "More items"
The attachment tab is too far away from the details.
You always need to tag people so they get notified when you added comments. It would be nice that it notifies the owner of the item automatically.

Likelihood to Recommend

It's really great for organizing digital projects.

I like that you have an historic of everything in the work items.

I think it is less appropriate for business analysis. A white board like Miro is best suited in these cases.

Verified User

Strategist in Product Management (5001-10,000 employees)

Vetted Review

2 years of experience

Azure DevOps with SAFe

Rating: 10 out of 10

Incentivized

January 9, 2024

Use Cases and Deployment Scope

We are following SAFe practices by using Azure DevOps starting from PI planning to retrospective. We are using all features starting from Work items, Dashboards, Repo, CI/CD pipelines etc..

Pros

Product Management
Delivery Plans
CI/CD

Cons

Integrate GitHub with Azure DevOps and have just one product
Automatic set Start and Target Date for Delivery Plan based on user story sprint assignment

Likelihood to Recommend

For small enterprises to big, it applies to all for efficient and effective product management with full traceability in built.

Harsh Shukla

Release Train Engineer in Product Management at Emerson (10,001+ employees)

Vetted Review

17 years of experience

View profile

Agile application for best project management practices

Rating: 8 out of 10

Incentivized

August 3, 2023

Use Cases and Deployment Scope

The application has provided the most suitable agile tools for managing projects in the organization. It tracks closely the task development infrastructure to enhance best implementation practices. My team has been depending on this platform for the last one year and the results have come out with positive ROI. Azure DevOps Services helps each department in performance modelling.

Pros

Monitoring web development process.
Building workflow pipeline.
Customization of dashboards.

Cons

Our goals have been implemented positively.
I have not experienced any missing feature.

Likelihood to Recommend

Our main projects have been developed under the excellent operations of this product. Deployment and testing of new applications has been great step ahead since we deployed this tool. Integration with other Azure services has been successful with top-notch results that have promoted faster production growth. It is easy to learn how this product operates even when you are fresher.

Ruth Carson

Software Engineer in Information Technology at NeoXam Tuinisie (51-200 employees)

Vetted Review

2 years of experience

View profile

Loading Reviews List....

Home
,
DevOps
,
Azure DevOps
,
Reviews and Ratings