We only use Microsoft Azure DevOps Server. Microsoft Azure DevOps Server can integrate with other systems such as CI and checking systems with analytics. The implementation is not so difficult, so it is fair. We installed it on our server. On a scale of 1-10, I rate Microsoft Azure DevOps Server a 7 out of 10.
I have left my previous company and am looking for new opportunities. When I find a new opportunity, I will deploy in that new environment. We are using Azure Vault for managing our secrets. The code is available to other employees and team members who are part of that particular team through GitHub. It is not necessary to wait for updates from developers as we receive codes regularly. If they want to test particular code, we directly use the pipeline for testing, and they receive notifications in their inbox. We aim to consume less time and involve fewer people while maintaining high work efficiency. The overall rating for this solution is 9.5 out of 10.
I have worked on Microsoft operating system, server operating system, Azure, and Microsoft InTune, which are solutions I have experience working with. The name of the solution is Microsoft Azure DevOps Server. On a scale of one to ten, I rate Microsoft Azure DevOps Server a nine.
I manage products using these solutions on a regular basis. I use Azure Pipelines daily, and we measure how fast we deliver things. I have given Microsoft Azure DevOps Server a rating of 8 out of 10.
The tool is useful for students. However, if we are looking for other opportunities, we can use a different solution that is more efficient, optimized, and easy to use. I am a beginner-level user. Overall, I rate the solution an eight out of ten.
Learn what your peers think about Microsoft Azure DevOps Server. Get advice and tips from experienced pros sharing their opinions. Updated: September 2025.
There are many updates in Visual Studio Team System. We have to use a lot of components, like, DevExpress, along with other platforms, like ACES Workflow and ABP IO. We are using WSO2 for integration which is also a good product having low prices, and I have been using it for more than five years now. I would recommend the solution to others planning to use it. So, I rate the overall tool a nine out of ten.
Before using the solution, it is good to have prior knowledge about how it works, how it can scale, and how it integrates with peer tools. There may be integrations which are not feasible in the solution's community version, so it is good to do your homework. I rate the solution a ten out of ten.
Process Manager at a marketing services firm with 201-500 employees
Real User
2021-09-03T09:39:37Z
Sep 3, 2021
If price is not a consideration, then my recommendation to others is that they go with the solution. The solution is cloud-based. I rate Visual Studio Team System as a seven or eight out of ten.
The features are fine for what it is. It works very well. It's designed for a specific niche, which is a very big niche. In summary, this is a good product that is straightforward, easy to use, and manages well. It's a fine product. I would rate this solution a nine out of ten.
My advice to anybody who is considering this solution is to first decide what they need out of it. The benefit of each solution is becoming multidimensional. For example, TFS can be used for managing code, managing software, and lifecycle development. People have to decide which dimension they need to use and then focus on it. Later, they can go to explore and use other dimensions. Otherwise, they will lose a lot of time trying to learn and to adapt to the solution. This is the biggest lesson that we learned from our implementation. Once we mastered its use in one area, we moved on to the next. I would rate this solution a seven out of ten.
Software Engineer at a financial services firm with 10,001+ employees
Real User
2020-02-12T08:38:13Z
Feb 12, 2020
The 2017 version is similar to 2015, they have added a few things. One difference is the setup experience, although it is not a groundbreaking change. I know that they have released a new version, 2019, that allows for sharing of what you see also remotely. You can work on code with your colleague who is developing somewhere else, remotely. When it comes to this solution, I am not really missing anything I needed from an IDE. I would rate this solution an eight out of ten.
My advice to others would be to go all the way with this solution. Don't try to find a cheaper solution. On a scale from one to ten, I rate Visual Studio Team System an eight and I'm looking forward to the new Blazers system.
.Net and MES Architect at a manufacturing company with 1,001-5,000 employees
Real User
2019-09-10T09:04:00Z
Sep 10, 2019
I like the performance management of this solution and my rating would be eight out of ten. The solution works for us but nowadays I would perhaps adviser others to use a cloud-based version like Microsoft DevOps. The biggest lesson I've learned is you can have all the tools but you still have to manage the communication between developers. Even with the tools you can easily run into some issues with several people who work on the same parts of the projects. So it is very important to organize your sources the best you can. But keep the communication channels open.
Microsoft Azure DevOps Server is a comprehensive platform for managing software development processes, offering tools for code management, lifecycle development, and project tracking, supporting remote repositories and continuous integration.Azure DevOps Server is known for its scalability, robust framework, and efficient version control. It enhances usability through features like campaign boards, sprint planning, and project status tracking graphics. Users appreciate its source control and...
We only use Microsoft Azure DevOps Server. Microsoft Azure DevOps Server can integrate with other systems such as CI and checking systems with analytics. The implementation is not so difficult, so it is fair. We installed it on our server. On a scale of 1-10, I rate Microsoft Azure DevOps Server a 7 out of 10.
I have left my previous company and am looking for new opportunities. When I find a new opportunity, I will deploy in that new environment. We are using Azure Vault for managing our secrets. The code is available to other employees and team members who are part of that particular team through GitHub. It is not necessary to wait for updates from developers as we receive codes regularly. If they want to test particular code, we directly use the pipeline for testing, and they receive notifications in their inbox. We aim to consume less time and involve fewer people while maintaining high work efficiency. The overall rating for this solution is 9.5 out of 10.
I have worked on Microsoft operating system, server operating system, Azure, and Microsoft InTune, which are solutions I have experience working with. The name of the solution is Microsoft Azure DevOps Server. On a scale of one to ten, I rate Microsoft Azure DevOps Server a nine.
I manage products using these solutions on a regular basis. I use Azure Pipelines daily, and we measure how fast we deliver things. I have given Microsoft Azure DevOps Server a rating of 8 out of 10.
The tool is useful for students. However, if we are looking for other opportunities, we can use a different solution that is more efficient, optimized, and easy to use. I am a beginner-level user. Overall, I rate the solution an eight out of ten.
I rate the product a nine out of ten. You need to be careful about the pricing. The solution can be expensive if you get an enterprise subscription.
There are many updates in Visual Studio Team System. We have to use a lot of components, like, DevExpress, along with other platforms, like ACES Workflow and ABP IO. We are using WSO2 for integration which is also a good product having low prices, and I have been using it for more than five years now. I would recommend the solution to others planning to use it. So, I rate the overall tool a nine out of ten.
Before using the solution, it is good to have prior knowledge about how it works, how it can scale, and how it integrates with peer tools. There may be integrations which are not feasible in the solution's community version, so it is good to do your homework. I rate the solution a ten out of ten.
If price is not a consideration, then my recommendation to others is that they go with the solution. The solution is cloud-based. I rate Visual Studio Team System as a seven or eight out of ten.
The features are fine for what it is. It works very well. It's designed for a specific niche, which is a very big niche. In summary, this is a good product that is straightforward, easy to use, and manages well. It's a fine product. I would rate this solution a nine out of ten.
My advice to anybody who is considering this solution is to first decide what they need out of it. The benefit of each solution is becoming multidimensional. For example, TFS can be used for managing code, managing software, and lifecycle development. People have to decide which dimension they need to use and then focus on it. Later, they can go to explore and use other dimensions. Otherwise, they will lose a lot of time trying to learn and to adapt to the solution. This is the biggest lesson that we learned from our implementation. Once we mastered its use in one area, we moved on to the next. I would rate this solution a seven out of ten.
The 2017 version is similar to 2015, they have added a few things. One difference is the setup experience, although it is not a groundbreaking change. I know that they have released a new version, 2019, that allows for sharing of what you see also remotely. You can work on code with your colleague who is developing somewhere else, remotely. When it comes to this solution, I am not really missing anything I needed from an IDE. I would rate this solution an eight out of ten.
My advice to others would be to go all the way with this solution. Don't try to find a cheaper solution. On a scale from one to ten, I rate Visual Studio Team System an eight and I'm looking forward to the new Blazers system.
I like the performance management of this solution and my rating would be eight out of ten. The solution works for us but nowadays I would perhaps adviser others to use a cloud-based version like Microsoft DevOps. The biggest lesson I've learned is you can have all the tools but you still have to manage the communication between developers. Even with the tools you can easily run into some issues with several people who work on the same parts of the projects. So it is very important to organize your sources the best you can. But keep the communication channels open.