The best part of Azure DevOps Server is its integrated source control, work item tracking, and CI/CD capabilities. It simplifies development, deployment, and collaboration while providing full control through an on-premises environment. Review collected by and hosted on G2.com.

Azure DevOps Server is a powerful platform, but some areas could be improved. The user interface feels dated compared to the cloud version (Azure DevOps Services). Troubleshooting build and release pipeline failures can be time-consuming because error messages are not always clear. Upgrading and maintaining the server requires significant effort, and integrations with newer tools and SDKs can sometimes be challenging. Performance can also degrade as the number of projects and pipelines grows. Better diagnostics, simplified administration, and more modern pipeline management would improve the overall experience. Review collected by and hosted on G2.com.

Choose Azure DevOps Server if you are bound by legal regulations or operate in an air-gapped environment. Otherwise, Azure DevOps Services (Cloud) is the superior choice for agility, cost-efficiency, and access to the latest DevOps innovations. Review collected by and hosted on G2.com.

With the rise of hybrid and remote work, granting secure access to an internal server usually requires VPNs or complex Reverse Proxies. This adds a layer of friction for developers that the Cloud version (accessible via secure web login) simply doesn't have. Review collected by and hosted on G2.com.

What I like most is how ADO brings our entire SDLC under one roof, end to end. We start with business requirements, break them into user stories, track sprints and calls, and link commits and PRs right back to the work items—without juggling five different tools. The boards feel clean and not fussy, the backlog is easy to groom, and pulling a report for a review doesn’t take a full afternoon. I’m in it most workdays, and it genuinely feels like the place where the team’s work lives: docs, code, tests, and status, all moving in one lane.

Getting it set up for daily use was pretty smooth once the initial project structure and permissions were in place. Repos for dev and test code sit side by side, version control is solid, and PR workflows with reviews and policies help keep the quality bar steady. Test Plans and Suites are straightforward to manage—we tag cases, run them, and connect failures back to bugs so triage isn’t a guessing game. Pipelines have also been great for scheduling API tests across environments; parameter passing is simple, and artifacts land where we expect them, which makes handoffs quick and clean.

Integration-wise, it plays nicely with our stack. The IDE hooks are fine, webhooks to our chat work well, service connections reach the places we deploy, and the reporting plus dashboards give us the at-a-glance view that keeps the team aligned. Support and docs are decent too; when we get stuck, there’s usually an answer or a workaround without waiting forever. It’s a big set of features, but it stays usable, and I don’t feel like I’m fighting the tool just to get normal daily work done. Review collected by and hosted on G2.com.

My main concern is pipeline agent security. With self-hosted agents, it’s possible for them to end up with broader permissions than intended if you don’t lock things down tightly. It can also be easy for secrets to leak into logs, or for a workspace to retain sensitive files if cleanup isn’t strict. Service account scopes and network access require careful hardening, and every so often we catch a misconfiguration that makes me a bit nervous until it’s corrected. It’s not a dealbreaker, but it’s the area I find myself double-checking more often than anything else. Review collected by and hosted on G2.com.

On-premise deployment gives us complete control over code repositories and pipelines. The build automation and test management work reliably, making CI/CD execution smooth. Review collected by and hosted on G2.com.

Upgrading the self-hosted server requires significant maintenance overhead. The UI/UX feels dated compared to Azure DevOps Services, and extension setup can be rigid. Review collected by and hosted on G2.com.

For me, “all in one” really means CI/CD in a single place: building a deployment pipeline, along with support for story grooming, epic management, and release management. Review collected by and hosted on G2.com.

The refresh rate is a little slow. Sometimes updates don’t show in real time, so I have to refresh to see other people’s changes. Also, if someone else changes something after I’ve opened the tab, I’m not able to save my data. Review collected by and hosted on G2.com.

I had the chance to use Azure devops server when I was using it for EV charging stations and home automation development and validaiton phases. I like how Azure Devops server provides a centralized platform for development tracking, creating test cases and structuring test plans. Review collected by and hosted on G2.com.

There is one limitation which I noticed and used to bother me is that setting up and configuring Devops derver can be time consuming, especially for complex long projects. Creating detailed test plans with connecting trees and structuring test cases takes effort. Navigating between boards and pipelines feels a bit time taking. Review collected by and hosted on G2.com.

It is a good system for managing PBIs and tickets for software development. It has comprehensive parameters for each ticket type and has a whole host of integrations that make life easier and keep roadmaps in sync. Review collected by and hosted on G2.com.

I moved to ADO from Jira and I really didnt like it at first, the UI is harder to use and the fact you cant have multiple users editing at once is a right pain. Review collected by and hosted on G2.com.

What I like best about Azure DevOps Server is its flexibility and how well it integrates into the development lifecycle. DevOps platform with features like version control, CI/CD pipelines, tracking all under one roof, makes our project to be managed easily. I use it daily for code management and automated deployments. It is easy to implement and built to scale at enterprise level. This has helped improve collaborations across teams. And also, customer support is easy and quick to resolve issues. Review collected by and hosted on G2.com.

What I dislike about Azure DevOps Server is that it can get little complex when setting up advanced pipelines and managing permissions. These things sometimes feel difficult and needs extra effort to configure correctly. Sometimes performance can be slow when large repositories is handled. And different integrations require more configurations and more time. Review collected by and hosted on G2.com.

Azure DevOps Server gives us a solid, centralized place to manage our code with good version control and team collaboration. Since I mainly use the repo feature, I appreciate how easy it is to organize branches, review changes, track history, and keep everything in one secure internal system. Review collected by and hosted on G2.com.

While the repo feature is reliable, the Boards and Test Plan experience can feel a bit dated and less efficient than I would prefer. Review collected by and hosted on G2.com.

- Integrated toolset - Allows project management, build automation, version control

- Helps in collaborating features -Allows multiple team members to work together, review on a senior level and final sign off

- Offers built-in reporting and insightful analytics

- Workflows can be customised

- Version Control: With support for Git and Team Foundation Version Control (TFVC), teams can manage their source code effectively, ensuring that changes are tracked and managed properly Review collected by and hosted on G2.com.

Cost -The licensing cost is quite significant

Integration with Third party apps - Might have some limitations in integrating with third party apps

Can be a challenge on large scale projects Review collected by and hosted on G2.com.