Azure DevOps Services Reviews & Insights

Score7.8 out of 10

479 Reviews and Ratings

Community insights

TrustRadius Insights for Azure DevOps Services 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.

Azure DevOps Services Reviews

9 Reviews

Engineering

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 (Computer Software, 201-500 employees)

Vetted Review

Reseller

7 years of experience

Verified on LinkedIn

Your Code, Project and Team, safe in one place

Rating: 9 out of 10

Incentivized

August 3, 2021

Use Cases and Deployment Scope

Azure DevOps offers a wide variety of tools for a CI/CD environment and it's really useful. We are moving from a static build model to an automated one and so VSTS has the tools we need to continue growing in the future. We started using VSTS, now Azure DevOps, as a code repository only and that's the main use within our organization.

Pros

Private repositories
User management
Security
Extensions

Cons

Some integration with 3rd party tools or services could be better
Has a lot of options, but sometimes are hard to find
Non standard build/test workflows could be problematic

Likelihood to Recommend

Azure DevOps Services is a great service. Its function as a code repository is great, and its integration with Visual Studio and Visual Studio Code lets you work in a natural way from these tools. MS Teams integration exists as far as we test it requires an Azure subscription, so it does not apply to the free 5 user tier.

We have been using it for at least 5 years and it's rock-solid in its function and always adds new options and features. We started using it because of its free 5 user private repositories function. Now GitHub does the same (and it's also from Microsoft) but Azure DevOps Services offers more options and tools, so we will stick with this service.

Verified User

Project Manager in Engineering (Entertainment company, 51-200 employees)

Vetted Review

5 years of experience

DevOps is one of the key solutions to all of your successful development projects

Rating: 10 out of 10

Incentivized

October 14, 2019

Use Cases and Deployment Scope

Azure DevOps is being used by our development department. It addresses the problem of not having a central source code storage location with team collaboration. It is used to store and collaborate on development projects. All team members are checking in/out their source code and pipelines/team collaboration is in use.

Pros

Ease of use/integration with Visual Studio.
Very responsive and easy to maintain a site.
Has full Git capabilities.
Capability to store unlimited numbers of projects.

Cons

The price/license per user could be a little less than many of the open-source type source code platforms on the market.
Ease of integration with other development IDE's than Visual Studio.

Likelihood to Recommend

No matter how many developers you have within the company, a robust source code control/DevOps pipeline is a must. When a new software development project is needed it can be initiated within DevOps by any team member/manager. The project can be tracked from start to finish with alerts and message ability directly in the product. The QA team can also monitor and provide feedback directly within the product.

Verified User

Manager in Engineering (Information Technology and Services company, 1001-5000 employees)

Vetted Review

5 years of experience

Get Quick Pipelines Up and Running with Azure DevOps

Rating: 10 out of 10

Incentivized

October 10, 2019

Use Cases and Deployment Scope

Azure DevOps is a common tool used by technical teams. In my capacity I used Azure DevOps to create a Chef Cookbook pipeline for delivering tested code. In doing this, I used it in conjunction with the built in version control system provided by Azure DevOps, but it also integrates well with Github and other systems.I also helped others set up pipelines and implement the use of Azure DevOps in this capacity as well.

Pros

Usability: The usability of Azure DevOps is great! Being a new user, it was easy to pick up and go with this tool with very little requirement to seek external documentation.
Integration: This tool integrates well with other systems (ie. Github, Chef, etc).
Built in activities: Azure DevOps has a ton of prebuilt activities that allow you to basically build whatever you need without writing any extensive code.

Cons

While usability is great, it did take me a few times to find "hidden areas" (like the visual designer link for creating pipelines). Having these in more defined noticeable areas will only improve on the already great usability.
As with other Microsoft tools, the Microsoft login get's a little crazy when you have multiple accounts. In my case, I have several accounts (personal, university, and work) and getting into Azure DevOps with the appropriate account could sometimes be an act of futility.

Likelihood to Recommend

Azure DevOps is well suited for any platform you are running. In my case, it was a great Chef cookbook pipeline solution that required no overhead or setup, cost nothing, and worked great. It works well with on-prem systems, systems in Azure, systems in AWS, and even systems in Google Cloud. Honestly, it's a really great multi-platform tool in my opinion.

Verified User

Engineer in Engineering (Information Services company, 501-1000 employees)

Vetted Review

2 years of experience

A fully featured DevOps suite

Rating: 9 out of 10

Incentivized

May 16, 2019

Use Cases and Deployment Scope

We're implementing entire product workflows with Azure DevOps: building, testing, staging and deploying. It's the perfect companion for Visual Studio and Git, so everyone just loves using it. It's a dream come true not having to switch to different front-ends to get our job done throughout the day, while keeping an amazing user experience.

Pros

Unified environment for all DevOps tasks and procedures
Amazing User Experience within a beautiful UI
Great marketplace extensions collection

Cons

Code merging has room for improvement
Such a broad set of features can become confusing for the novice user

Likelihood to Recommend

It's a great way to normalize DevOps wokflows, allowing you to replace lots of different tools and get the job done with a unified package. Testing support is second to none. If you're just focusing on development with version control, than Visual Studio packed with Git will probably cover all your needs.

Maria Sousa

Managing Engineer in Engineering at Carrilho Engineering (Telecommunications, 11-50 employees)

Vetted Review

2 years of experience

View profile

VSTS makes building and releasing applications a breeze

Rating: 8 out of 10

Incentivized

April 12, 2018

Use Cases and Deployment Scope

The team I work on uses Microsoft Visual Studio Team (VSTS) for code storage and versioning, as well as utilizing their build and release systems. This resolves multiple issues including removing the need for us to manage a local repository and helps automate the process of building and releasing new versions of our application by leveraging automatic processes triggered when branch is pushed to the remote server.

Pros

Code repository
Automatic Build & Release

Cons

User management

Likelihood to Recommend

VSTS is well suited for just about any coding project that can be built and deployed on a Windows platform. Building platform-specific languages is not as easy to build on their cloud server, but private agents can also be set up on target systems to allow for building in just about any environment.

Devin Rodriguez

Application Developer in Engineering at IGT (Gambling & Casinos, 10,001+ employees)

Vetted Review

1 year of experience

View profile

New guy on the VSTS block.

Rating: 8 out of 10

Incentivized

October 17, 2017

Use Cases and Deployment Scope

We are moving our entire code base from on-prem TFS to Visual Studio Team System(VSTS) with GIT repositories. We are taking the opportunity to move to a complete continuous integration solution. We also feel that moving to GIT will improve code quality with the way that branches are lightweight and how code reviews are a fundamental part of the way you do things in GIT.

Pros

Integration with Visual Studio
Option to use GIT or TFS repositories.
Plugins galore.

Cons

I think the documentation lags too far behind the actual product.
Troubleshooting could be easier.
There are some glaring pieces missing or are just obscure to use. The way you publish a built website is pretty bizarre.

Likelihood to Recommend

I think it is a great place for a Microsoft shop to move to. If you are already on a TFS based system, there are a lot of tools to move your code base to Visual Studio Team System. I think it is overkill fone-mane man band. Just use GIT and set up build agents locally if that is the case.

Clay Horste

Software Developer III in Engineering at Opus Solutions (Events Services, 51-200 employees)

Vetted Review

1 year of experience

View profile

VSTS - a polished project management tool

Rating: 10 out of 10

Incentivized

October 6, 2017

Use Cases and Deployment Scope

Microsoft Visual Studio Team System was used to manage projects by my team for easy access to the health status of the entire project. It was used for issue tracking, version control, build status and statistics, code analysis and planning delivery.

Pros

It shows the health status of the entire software development pipeline with easy access to information.
Work items templates are customizable as needed.
The work items can be moved around from one type to another easily if needed.

Cons

255 character path limitation.
Dependency on the internet means source control needs to be off when offline.
Agile support is not good and hard to maintain.

Likelihood to Recommend

We can create customizable dashboards and they are very easy to create. Work items are customizable too so that no relevant information is left out. We can also get Excel reports from it for the overall health status of the pipeline.

Verified User

Engineer in Engineering (Information Technology and Services company, 5001-10,000 employees)

Vetted Review

1 year of experience

A Solid Tracking and Deployment System

Rating: 7 out of 10

Incentivized

September 12, 2017

Use Cases and Deployment Scope

VSTS is used across the organization for the full breadth of its features. It is used for bug and feature tracking, continuous integration builds, deploys, and automated testing. Every portion of development uses it, developers, quality assurance, product owners, etc. Everyone is in the system multiple times throughout the day to manage their workflows.

Pros

Integration of version control/pull requests to bug tracking.
Multiple views of team work - lists, kanban boards, etc
Supports the full product lifecycle from planning to deployment

Cons

The website has a tendency to log out, and the sign-in is a popup that bypasses password managers.
All instances look the same. If you need to use multiple versions, it can be hard to tell which you are in.
The security/permission system is strange and is not simply the sum of your roles.

Likelihood to Recommend

VSTS is good for any feature tracking. The build and deploys are platform independent, but as this is a Microsoft product the integrations are better for Microsoft products. If you are using entirely non-Microsoft, this is probably not the best tool for you. If you are a pure or mostly Microsoft shop, this will give you many integrations out of the box that you would need to install or build for a competing product.

Christopher Belanger

Senior Software Engineer in Engineering at Amadeus Hospitality (Hospitality, 5001-10,000 employees)

Vetted Review

1 year of experience

View profile

Loading Reviews List....

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

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

Chris Studebaker

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

Vetted Review

Reseller

7 years of experience

Verified on LinkedIn