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.
| Product | Mindshare (%) |
|---|---|
| Microsoft Azure DevOps Server | 8.8% |
| Endevor | 12.3% |
| IBM Rational ClearCase | 11.8% |
| Other | 67.1% |
| Company Size | Count |
|---|---|
| Small Business | 9 |
| Midsize Enterprise | 3 |
| Large Enterprise | 7 |
| Company Size | Count |
|---|---|
| Small Business | 64 |
| Midsize Enterprise | 12 |
| Large Enterprise | 37 |
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 powerful IDE that supports building and deploying applications. However, there are challenges with offline functionality, integration with other systems, and stability on non-Windows platforms. Moreover, it supports various sectors by streamlining the software development processes, especially for teams working on digital transformation and business process automation.
What are the key features of Microsoft Azure DevOps Server?Azure DevOps Server finds use in industries such as industrial sectors, government digital transformation, and business process automation. Teams employ it for software development, leveraging integration with systems and automation tools daily. Its support for remote repository management and ALM management makes it a vital resource for project efficiency.
Bluegarden A/S, Tracasa, Rabobank Group, Borusan Otomotiv, Arelik, Alfa Bank
| Author info | Rating | Review Summary |
|---|---|---|
| Department Manager, Certification Project Management at Institute for Information Industry | 4.0 | We find Azure Board easy to use for IT project management, stable, and scalable. However, its high price limits account access, and inconsistent UI changes across versions are problematic. Overall, I rate it a 7/10. |
| dba at a comms service provider with 1,001-5,000 employees | 4.0 | I manage and optimize Azure SQL, Managed Instance, and SQL DB, using Azure DevOps for tracking work. Despite a past unresolved support issue, I rate Microsoft service 8/10, with Copilot being very useful. |
| Senior Technical Specialist at Intuitive Technology Partners | 4.5 | I am highly satisfied with Azure DevOps Server, Red Hat AMQ, and RHEL for our CI/CD and critical applications. The solutions offer fantastic performance, scalability, and savings, though price for expansion is a concern. Customer service for AKS was excellent. |
| Software Engeenir at Cardiff University / Prifysgol Caerdydd | 3.5 | I use Microsoft Azure DevOps Server mainly for hosting applications, valuing its ecosystem integration. However, I find its analytics weak, Azure Boards minimal, and documentation messy. Overall, I rate it a 7 out of 10. |
| System Admin Specialist at CECO Environmental | 4.5 | I find Microsoft Azure DevOps Server user-friendly, stable, and easy to set up for managing data. Support is excellent (9/10), though I'd appreciate quicker resolution. Overall, I rate it a nine out of ten. |
| Software Architect at Gritmind | 4.0 | I value Azure DevOps Server for its all-in-one project management, code, and delivery. However, its UI is unintuitive, and I find limitations in planning, advanced metrics, and GitHub Copilot integration, often requiring custom solutions. |
| Sourcing Purchasing Manager at Nexans autoelectric GmbH | 4.0 | I find Visual Studio Team System efficient for limited tasks in developing information systems, and it's globally accepted. However, it needs stability improvements and more innovation to enhance efficiency and aid both internal and external processes. |
| Senior Associate at a financial services firm with 51-200 employees | 4.5 | I use Visual Studio Team System as an IDE for CRM development and find it exceptionally powerful. However, its expensive subscriptions can be a challenge for smaller businesses, and stability issues occur on non-Windows platforms, which need improvement. |
| Founder at Druansh | 4.5 | Visual Studio Team System assists with ALM management and project requirement capture. It offers valuable version control and allows building, developing, testing, and deploying applications from a single platform. However, I believe its pricing could be improved. |
| Project Manager at Unimity Solutions | 4.5 | I use Visual Studio Team System for software development and find its fast performance to be its most valuable feature. However, I believe the product's stability could be improved. I haven't used or considered any other solutions or cloud providers. |
We are just a user for our IT project management.
Azure Board is helpful because it is easy to use and the board clearly shows the status of our project.
The disadvantage is the price is a problem. Because of the price, we cannot buy as many accounts as we want, so just some people in our team can use it.
There are technical problems. They always change the UI in different versions, so the UI is not the same across versions.
UI and integration to other systems may not be easy. For example, some shareware is built for a UNIX system, so it is not compatible with Microsoft Azure DevOps Server.
We have been using it for almost two years.
It is stable.
It is easy to scale.
Technical support sometimes is not free, but we just use the free part. We read the documentation on the Microsoft website.
Neutral
Many years ago, we used OnTime, which is also a project management software.
Microsoft Azure DevOps Server is better because it integrates with many other systems and software. There is also a Git system and a board system.
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.
With Azure, I deal with products such as Azure SQL, Azure Managed Instance, and SQL Managed Instance. It's one of the products Microsoft offers instead of a physical SQL Server machine. It's a Managed Instance with a SQL Server Agent and then Azure SQL DB, which is without the SQL Server Agent, in a few words.
I don't deal with Azure Database for PostgreSQL; it's only SQL Server. It's only Azure SQL; I don't deal with other database products or data solutions. I only work with SQL Server; I don't deal with other vendors either.
We have databases with a bunch of tables, and I'm doing support, maintenance, plus all the application support such as indexing, performance fine-tuning, and optimization. I spend the whole day on performance fine-tuning and optimization.
We use Microsoft Azure DevOps Server and Azure SQL, where we create stories and tasks. When tasks or stories are completed, they are marked as such.
I'm a user who deals with the stories and creates them when needed. I'm not the person handling that or acting as a Scrum Master. For me, it's the creation of the stories, which is how work is tracked. You prepare what you're going to work on in the next two weeks. Your manager creates stories and assigns them to you, and based on those stories, you work accordingly. During that time, there can be production issues that cause you to step away from working on your stories, but once you complete the production issue, you return to continue your work.
Positive
People are integrating source control systems such as Git in my team, but I don't do that personally.
I'm not involved with the pricing or licensing of Azure.
For Microsoft Azure DevOps Server, I would give it an eight. I work with Microsoft and understand what they are trying to do; it really helps.
A few days ago, I got signed up for Copilot, and I went through training classes; it's really a great tool. I heard from others using it more regularly, and they found it very useful. It's definitely a very good and useful tool, so I can't give less than eight, but for Copilot, I can give them a nine or ten.
I work for a consultancy company as a consultant, not as a full-time employee.
Overall rating: 8/10
The customer is not using OpenShift as they have a separate virtualization environment. For most of their applications that are microservices, they prefer Kubernetes.
I implemented AMQ using the Kubernetes container engine. I suggested the technique called high availability, which means cluster, to implement AMQ using the high availability cluster.
My current company was not using any products apart from AMQ. I suggested it to them, which is why they started using it. I also suggested it to the customer.
The feedback for Red Hat AMQ has been good. Based on this, we suggest it to our customers, and they are happy using that product. Our big customer, FedEx, which is one of the best and biggest giants in logistics and courier, started using it and they are happy with that.
The base operating system, RHEL 8 and 9, is being used across the infrastructure. The server and critical applications and data are running on Red Hat 8 and 9. We are performing proper maintenance of the OS and it is working fantastically. We have not received any issues or complaints.
Our domains include Human Gateway, pharmaceuticals, and automobile clients. The critical application is running on Microsoft Azure DevOps Server. When developers send code to us, we create the CI/CD pipeline and schedule jobs. The solution provides time savings and infrastructure savings.
Multiple virtual machines are not required when installing applications in containerization, which saves infrastructure costs. We receive notifications about CPU, memory, and disk space utilization from time to time.
We are currently satisfied with the solution and are still working with it. If we observe any gaps or improvements required, we will definitely provide feedback.
Price is a concern, though we are currently managing. When we expand our infrastructure, we may need to buy more licenses, which sometimes is not worthwhile from a price perspective. Once we have a proper discussion on that, we will provide feedback.
The project has been using Microsoft Azure DevOps Server for more than five years, since before I joined.
The performance is fantastic. We do not have any complaints. There is a customization option for the analytical part. We customize according to the needs and preferences of the customer at the customer level. We have not found any problems.
The solution is easy to scale.
When we faced issues with the AKS cluster, the solutions provided were excellent. We shared these solutions with the customer, who was satisfied. After our research, we found that the solutions shared by the support team were among the best available. I rate the service 9 points, deducting half a point because sometimes we get delayed replies.
Positive
We found Microsoft Azure DevOps Server to be suitable for us. We have not tried other vendors such as AWS, but we are satisfied with these Azure services.
We are using Azure Pipeline. The developers store their code in a particular repository to which we have access. When they request pipeline creation for upgrading existing applications, they send us an email. We update via email that the code is available, put it in a pipeline, and start the process. We communicate the results, whether the deployment was successful or if it failed, identifying the reasons. The developers receive notifications once the task is completed in the pipeline.
We monitor the cost optimization part carefully. We receive regular details from our L1 and L2 teams. Based on this information, we take appropriate action. We stop resources that are not required to be running on the Azure portal. We are managing this aspect successfully.
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.
The biggest advantage of Microsoft Azure DevOps Server for me is the integration with the rest of the ecosystem.
They could improve Microsoft Azure DevOps Server for analytics. It is quite hard to track within the software to track progress over time, burndown charts, and similar features. There is a significant lack of that functionality.
I have been working with Microsoft Azure DevOps Server for a year.
Rating stability on a scale from one to ten, I would give it seven or eight.
It is tough to fully assess because we have not had a need for massive scalability, but it is pretty good.
After gaining experience, the installation of Microsoft Azure DevOps Server becomes straightforward because you understand the process, but the documentation for much of the Microsoft material is quite messy.
Comparing Microsoft Azure DevOps Server to competitors in the market is not my responsibility. I use what is assigned to me, so I cannot provide a comparison.
I work for a pensions company and use Microsoft Azure DevOps Server as a user.
I work with Azure Pipelines, though they are very minimal. When pushing out to production, my experience includes basic Terraform scripts, which I use for versioning.
I am using Azure Boards for project management. My experience with Azure Boards is not helpful for planning or tracking. In comparison to the boards on GitHub and GitLab, they are quite minimal. It seems really stripped back, and the capabilities seem much weaker.
We host models in Azure, which can sometimes have issues, but it is relatively good. The biggest problem is models being in the right domain for us - EU servers - it is a real lack of them.
On a scale of 1-10, I would rate this solution a 7.
As a technical person in our company, we use Microsoft Azure DevOps Server to manage all work-related data for the end users in the office.
I find Microsoft Azure DevOps Server to be proper and user-friendly, making it easy to manage.
The initial setup of Microsoft Azure DevOps Server was straightforward, and I didn't face any issues or problems during implementation.
Microsoft Azure DevOps Server demonstrates good stability, which supports my assessment that it is a scalable solution.
Since I haven't used another solution, my ability to suggest improvements for Microsoft Azure DevOps Server is limited. From my experience, the operating and server handling aspects are very easy, so there isn't much need for improvement in those areas.
While the solution performs well overall, it would be beneficial if they provided quick links for immediate access to support when queries arise. The improvement needed is primarily in the speed of resolution.
I have three years of experience in Microsoft Azure, specifically with Microsoft Azure DevOps Server.
I would rate the technical support from Microsoft as a nine out of ten, where one represents the worst technical support and ten represents the best.
Positive
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.
Microsoft Azure DevOps Server is a go-to product because it has everything in one place for project management, delivery, code, and similar functionalities. This eliminates the need to have or buy multiple tools simultaneously for regular product delivery.
We use the wiki to store documentation and Azure tickets to run agile processes and scrum in Azure Boards for this purpose.
The project management and planning tools within Microsoft Azure DevOps Server accomplish their basic functions. The UI may not be the best, and the planning tools have some limitations. For simple tasks, it works adequately, but for more complex task planning such as roadmaps, we usually work outside of Microsoft Azure DevOps Server.
The primary use cases of Microsoft Azure DevOps Server include storing source code, using documentation as a wiki, and utilizing pipelines to deploy applications.
I manage products using these solutions on a regular basis.
I work with Microsoft accounts focusing on product development, depending on our clients with Azure products.
I work with Azure App Services, Kubernetes, storage, and Azure DevOps tools, including Azure Databricks and Azure Face API.
For analytics, we have built-in queries, but I often use the Microsoft Azure DevOps Server API to pull data from the system for custom reporting and insights.
We utilize Microsoft Azure DevOps Server repositories in our internal processes.
The UI itself is not always intuitive, often requiring extra steps. The entire UI appears to be designed from an engineer's standpoint, which can make it challenging to navigate without spending time learning the system.
Regarding metrics, we aim to measure delivery speed, but the Azure Pipelines functionality is not always comprehensive. For example, measuring delivery time from pull request creation to production deployment requires extra configuration steps that are not available out of the box. The DORA metrics tracking requires building a custom solution as it's not available in the Microsoft Azure DevOps Server suite by default.
A significant challenge is that GitHub Copilot is not integrated with Microsoft Azure DevOps Server directly. Microsoft recommends switching to GitHub repositories to use Copilot, which means losing the benefit of having everything in one place. This requires using two tools, enabling integration, and dealing with different UIs and workflows.
The Microsoft Azure DevOps Server team doesn't always address community requests promptly. Some simple requests remain unaddressed for up to five years, such as the ability to configure commit prefix behavior on pull request closure.
Certain elements are hardcoded in the planning tool. For instance, while user stories work and track progress correctly, custom item types such as technical debt or technical work do not calculate properly.
I have been using Azure products for approximately 15 years, starting from Azure Classic.
The entire service works very effectively in terms of stability.
I have limited experience with technical support from Microsoft in general, but I have some experience with Azure support. The problems I encountered with Azure support were resolved quickly. I would rate Azure support 8 out of 10.
Positive
I have used similar solutions including Jenkins, GitHub, GitLab, and TeamCity. In some cases, we use these solutions in parallel, with some projects using GitHub or GitLab while others use Microsoft Azure DevOps Server.
The pricing is a good choice.
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.
We can use the tool to perform limited tasks in developing information systems.
The product is efficient. It is an accepted tool globally.
The product must improve its stability. It must do more innovations. It could be made more efficient to provide the best responses. It will help us with internal and external processes.
I started using the solution this year.
The tool is stable. I rate the stability an eight out of ten.
The tool is scalable. I am the only user.
The initial setup is not complex. It’s moderately easy.
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.
We use the Visual Studio Team System as an IDE for our CRM development.
Visual Studio Team System is the most powerful IDE available in the market.
The tool's subscriptions are expensive for medium and small businesses. It works fine on Windows. However, it is not stable on other platforms.
I have been working with the system for 15 years.
I rate the product's stability an eight out of ten.
My company has five users for the product.
Visual Studio Team System's tech support is responsive.
Visual Studio Team System's deployment is straightforward and completed in a few hours. You need to select the options that you want to configure.
Visual Studio Team System can be deployed in-house.
The tool's licensing costs are yearly.
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.
The tool helps with ALM management and helps the team capture project requirements.
The product helps with version control. I can build, develop, test and deploy applications from a single platform.
The product should be priced better.
I have been using the product for three to four years.
The solution is stable and I would rate its stability a nine out of ten.
The tool is cloud-based and pretty scalable. I would rate its scalability a nine out of ten.
The tool's setup is straightforward. We need two to three admins to manage the tool's deployment and maintenance.
The solution's deployment can be done in-house if you have experienced people who can deploy it.
You can choose pricing from a variety of options. I would rate the product's pricing a six out of ten.
I would rate the overall product a nine out of ten.
I use the solution for software development.
The solution’s fast performance is its most valuable feature.
The stability of the product could be better.
I have been using the solution for less than a year.
I rate the stability an eight out of ten.
I rate the scalability a nine out of ten. In my team, ten people are using the solution.
The initial setup was straightforward.
It took us 20 minutes to deploy the solution. We need 50 people to deploy and maintain the solution.
I manage a group of developers who use the solution. I did some online research and then installed the solution in our organization. I would recommend the product to others. Overall, I rate the solution a nine out of ten.
