Azure DevOps Server Reviews & Insights

Score8.3 out of 10

294 Reviews and Ratings

Community insights

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

Pros

Efficient Task Management: Users have found Azure Boards fast and easy to use once a good structure is established, enabling quick creation or modification of task types. This reduces administrative overhead and facilitates the creation of numerous smaller tasks.

Simplified Setup Process: Reviewers appreciate Azure Repos for its simplicity in setup compared to other solutions, with most options readily available including user management. The out-of-the-box features streamline the onboarding process.

Powerful CI/CD Pipelines: The Pipelines tool within Azure stands out for its robust capabilities, allowing users to swiftly create pipelines, automate workflows, and easily track their progress effectively throughout the development cycle.

Azure DevOps Server Reviews

5 Reviews

Engineering

best for code, but still missing tools for CAD designers.

Rating: 9 out of 10

Incentivized

January 2, 2025

Use Cases and Deployment Scope

Azure DevOps Server makes integration between different areas with the agile process, in my case I use Kanban to guide a hardware design team and Azure lets me create several features for each part of our PCB design process, and I can manage how each person on the team is going on, review cases are much easier. I can link all tasks from the first requirement to the reports from the qualification tests. Each project has an epic structure that lets us navigate over all projects and create multiple teams in the same workspace. I can bring a lot of metrics showing who is delaying, effort by project, and much more info that helps my board to understand if the critical tasks are being managed as requested.

Pros

multiple team management
one server for all types of team connected
version control is easy
scripts to automate simple tasks

Cons

integration with CADs for hardware design
improve the link management for child/related/parent work items
template for several common work flow

Likelihood to Recommend

For an agile team, DevOps is great. Using scrum, Kanban fits perfectly into the project structure. The web interface lets anyone, anywhere, interact with work items.

The version control is great if you code, but if you design with CADs, it still lacks some link features that could help non-code documents.

Alternatives

Admin Tools for Jira

Jira has been growing in hardware design teams since is being integrated with CAD software. The best of Azure is that you can manage since level of access control to multiple types of teams. Another bonus is that Jira has more mobile features that let your team stay connected with your phones.

Ricardo Noronha

Hardware Design in Engineering at Autotrac (Telecommunications, 201-500 employees)

Vetted Review

10 years of experience

View profile

Azure DevOps Server- A Collaborative tool for productivity

Rating: 9 out of 10

Incentivized

June 14, 2022

Use Cases and Deployment Scope

Azure DevOps Server is a collaborative project management tool we used in one of our projects while working from home to collaborate among team members, it helped us to track bugs, commit codes, create user story, and various forms of reports related to project. It allows integration with our existing IDEs, version control like Git, setup the CI/CD pipelines for code testing, release and deployments.
Azure DevOps Server was very helpful to our teams while we started working remotely, helped in increasing the productivity and prototyping the projects for release without any delay. Best part of using this tool is reporting, we were able to create Kanbans dashboards for integrated reports.

Pros

Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.

Cons

Azure test plans can be improved to be more automated, existing generic templates can be added to create more test plan in different languages.

Likelihood to Recommend

In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing.
It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects.
Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate.

Alternatives

GitLab

Better bug and user story tracking feature.
Easy integration with multiple version controls and code repo like- Github and Bitbucket.
Managing ticket lifecycle is quite good, able to easily move through different stages.
Test plans is much better than that of alternative, was sufficient for our scenarios.
Visualisation of user and projects sprint give good insight to the project status, its timeline.

Verified User

Engineer in Engineering (Computer Software company, 10,001+ employees)

Vetted Review

1 year of experience

Engineering Based Toolset for Extreme Collaboration

Rating: 8 out of 10

Incentivized

June 8, 2022

Use Cases and Deployment Scope

One product to cover the most common engineering activities in tech irrespective of the domain. Whether the team is in medical tech, fintech, aerospace tech, or a business process outsourcing firm, this platform has all the common tools needed in an Agile workspace with extreme collaborations across DevOps, Product, and Engineering. This gives the best centralized toolset, especially if your organization is already a Microsoft-based firm.

Pros

Version control
Requirements definition
Secrets library management
Continuous integration and deployment

Cons

Wiki Markdown customization
Better Syntax Highlighter in Repository
Improvements in Requirements Definition Customization

Likelihood to Recommend

In my capacity as an architect, the platform gives me the ability to define the architecture within a wiki. I can include details including flow, UML, and ER diagrams in the User Story of Features being defined by the Product Owner, and my engineering team can link the repository pull requests to the story being developed. My Product Owners can now view the business definitions, software architecture, code written, and QA tests performed all on one central platform.

Alternatives

Amazon Web Services and Amazon WorkSpaces (VDI)

My organization already has an established Microsoft relationship which allowed us to move faster in procuring the product. The alternative would require my large organization to move at a snail's pace at procurement. This is not necessarily a hindrance for most other companies - but it was a large issue from my position.

Matthew Budram

Software Architect in Engineering at TFOB (Information Technology & Services, 51-200 employees)

Vetted Review

2 years of experience

View profile

Azure DevOps Server a great choice

Rating: 8 out of 10

Incentivized

December 3, 2019

Use Cases and Deployment Scope

Our IT department uses Azure DevOps Server to manage all our projects and for software development.

Pros

Ease to manage code.
Compatible with several services.
Version control.

Cons

Need more templates.
Can be confusing to use at first.
Reporting could be better.

Likelihood to Recommend

It is well suited for any IT team, provides a great way to manage and track projects. Great for code reviews and bug management.

Alternatives

GitHub

Verified User

Engineer in Engineering (Telecommunications company, 11-50 employees)

Vetted Review

1 year of experience

Team Foundation Server is a great tool for enterprise level development

Rating: 8 out of 10

Incentivized

December 10, 2015

Use Cases and Deployment Scope

Team Foundation Server is used by our company as the primary tool for managing our software development process and managing our software code. We use an Agile Scrum process for our development and take advantage of the Team Foundation Server Agile work flow template. We do very few customizations to the template for ease of use and to keep maintenance and administration to a minimum. We use the Backlog and Board every day in our standup meetings. Our team has members in the US and abroad and Team Foundation Server helps keep everyone on the same page. We also use Team Foundation Server for our code repository. All of our source code and automated tests are stored in Team Foundation Server.

Pros

Team Foundation Server's built in Agile work flow template provides us an excellent out-of-the-box framework to manage our software projects.
Team Foundation Server's source code repository is easy to use and has all of the expected features that a large software development organization needs.
The Web Portal has a responsive and very easy user interface that allows the Scrum Master to make updates to User Stories, Tasks, and Bugs while members are reporting their status each day.

Cons

Team Foundation Server integrates with an SQA test module called Microsoft Test Manager (MTM). The integration between MTM and Team Foundation Server is not always straight forward. Some things can be done with Test Cases in the Team Foundation Server UI while others can only be done in MTM UI and vice versa.
The Team Foundation Server web portal is good for performing some actions, while the native client app is better for other actions. It is not as efficient or effective to have to know and work with the two different approaches.

Likelihood to Recommend

I think Team Foundation Server is the best solution when Microsoft development technologies are being used. Microsoft is focused on integration of their own technologies versus those of their competitors. This is just something to consider for the selection process. Also, it is important to consider all of the features that you require of a system. Team Foundation Server can do it all, but each module in itself may not be the best solution on the market.

Verified User

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

Vetted Review

5 years of experience

Loading Reviews List....

Team Foundation Server is a great tool for enterprise level development

Rating: 8 out of 10

Incentivized

December 10, 2015

Use Cases and Deployment Scope

Pros

Team Foundation Server's built in Agile work flow template provides us an excellent out-of-the-box framework to manage our software projects.
Team Foundation Server's source code repository is easy to use and has all of the expected features that a large software development organization needs.
The Web Portal has a responsive and very easy user interface that allows the Scrum Master to make updates to User Stories, Tasks, and Bugs while members are reporting their status each day.

Cons

Team Foundation Server integrates with an SQA test module called Microsoft Test Manager (MTM). The integration between MTM and Team Foundation Server is not always straight forward. Some things can be done with Test Cases in the Team Foundation Server UI while others can only be done in MTM UI and vice versa.
The Team Foundation Server web portal is good for performing some actions, while the native client app is better for other actions. It is not as efficient or effective to have to know and work with the two different approaches.

Likelihood to Recommend

Verified User

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

Vetted Review

5 years of experience