Try our new research platform with insights from 80,000+ expert users
Eli Harush - PeerSpot reviewer
Customer Solution Manager at DXC
Real User
It's a good tool for managing the CI/CD process
Pros and Cons
  • "It's a great product for the CI/CD process."
  • "Compared to JIRA, I think Azure DevOps is missing some management elements, like some reporting features. It would be helpful if some things were clearer when we're adding attributes. For instance, sometimes we want to add some categories or attributes, and it's not so easy."

What is our primary use case?

We manage the full scope of all our projects on Azure DevOps, including all of our kits, bags, and user storage. DevOps encompasses the CI/CD process of every build as well as the customer requirements, QA, and deployment.

What needs improvement?

Compared to JIRA, I think Azure DevOps is missing some management elements, like some reporting features. It would be helpful if some things were clearer when we're adding attributes. For instance, sometimes we want to add some categories or attributes, and it's not so easy.

For how long have I used the solution?

I've been using DevOps for approximately four years.

What do I think about the stability of the solution?

Azure DevOps is mostly stable.

Buyer's Guide
Microsoft Azure DevOps
March 2025
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
856,873 professionals have used our research since 2012.

How are customer service and support?

We've used Microsoft support but for .NET Core or Azure DevOps.

How was the initial setup?

Installing Azure DevOps is pretty straightforward at the installation or admin stage. Deployment time depends on the service on my side, so it's mostly very fast.

What other advice do I have?

It's a great product for the CI/CD process, but DevOps lacks some features for project management, guide, user story, etc., so it's far from perfect. Compared to monday.com, JIRA, or others, they have some work to do.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
PeerSpot user
Practice Director, Global Infrastructure Services at a computer software company with 10,001+ employees
Real User
Good for the purpose it is designed for and can be easily used by developers, but needs better reporting
Pros and Cons
  • "It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
  • "Reporting could be better. We would like to see how many applications are onboarded in DevOps and in which phase they are. We would like to know for how many applications we have done only the repository, but we have not yet done the build pipeline or deploy pipeline. Currently, there is no such report. We have to figure it out ourselves. There is no way to check how many applications are completing their build pipelines, how many applications are completing their deploy pipeline, how many are ready to use, and how many pipelines are working."

What is our primary use case?

It is for all the DevOps functions, such as managing the deployment of the code to the production environment. 

What is most valuable?

It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues.

What needs improvement?

Reporting could be better. We would like to see how many applications are onboarded in DevOps and in which phase they are. We would like to know for how many applications only the repository is done, but we have not yet done the build pipeline or deploy pipeline. Currently, there is no such report. We have to figure it out ourselves. There is no way to check how many applications are completing their build pipelines, how many applications are completing their deploy pipeline, how many are ready to use, and how many pipelines are working.

For how long have I used the solution?

I have been using this solution for more than two years.

What do I think about the stability of the solution?

It is stable. It is also good performance-wise. There are no issues.

What do I think about the scalability of the solution?

We have more than 800 developers who are using this solution, and this is only a portion of the company. Across the company, there are many groups, and we have more than 2,00,000 employees. We are using DevOps across many customer projects and environments, and more than 50% of our projects are on DevOps.

How are customer service and support?

Their support is good.

How was the initial setup?

It is a cloud solution, and there is no installation. You just start using it.

We have one or two admins per project for deployment and maintenance.

What other advice do I have?

I would definitely recommend this solution to others. They can go ahead and use it.

I would rate it a seven out of 10.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
PeerSpot user
Buyer's Guide
Microsoft Azure DevOps
March 2025
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
856,873 professionals have used our research since 2012.
Carlos Arturo Quiroga Quiroga - PeerSpot reviewer
Digital Architecture Corporate Leader at Banco Pichincha
Real User
It integrates well with other tools in the software development process, like quality testing, documentation, and agile development.
Pros and Cons
  • "Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development."
  • "I think Azure DevOps could improve the traceability or business intelligence about the execution of DevOps processes."

What is our primary use case?

We have separate DevOps processes for different teams. We're implementing agile processes, so we have cells for each product, and each cell has its own DevOps process. This means we have a DevOps process in GitHub, GitLab, and another tool. We have lots of costs and can't share experience between teams.

The idea was to unify everything in one product to ensure that we standardize DevOps practices on the same tool to have better knowledge and expertise and focus on a specific tool.

How has it helped my organization?

We had a lack of governance over DevOps processes, so we had some quality issues in the end when we released the software products. DevOps has helped to resolve those issues.

What is most valuable?

Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development. 

What needs improvement?

I think Azure DevOps could improve the traceability or business intelligence about the execution of DevOps processes. 

For how long have I used the solution?

I've been using DevOps for three years.

What do I think about the scalability of the solution?

Azure DevOps is scalable. 

How was the initial setup?

We have good people with a lot of experience in DevOps, so it's not complex for us. The most significant difficulty in adopting the tool was changing our past processes to move to the standardization model we defined with Microsoft DevOps.

What's my experience with pricing, setup cost, and licensing?

We have a yearly agreement with Microsoft to cover the different companies.

What other advice do I have?

I rate Azure DevOps nine out of 10. I would give it a perfect 10 if Microsoft offered personalized support. Sometimes we call Microsoft with requests, and it would be nice to have personalized processes with our specialized services.

We have two different approaches for products. One is to support products that we provide our customers. The other is creating a digital transformation strategy for new products. We are using DevOps in the latest products, and in the future, we are going to grow with support for products we have produced in the digital transformation. This is part of our roadmap to implement DevOps in all the processes in every technological area of our companies.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Product Owner at Day Insurance
Real User
The software covers the whole development cycle, from requirements analysis to deployment
Pros and Cons
  • "Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace."
  • "Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."

What is our primary use case?

We use Azure DevOps for the entire lifecycle of software development, starting with requirements analysis. After that, we use it to continue the process of development and deployment.

What is most valuable?

Azure DevOps is user-friendly. The UI and the UX are perfect. Their software covers the whole development cycle, from requirements analysis to deployment. In particular, it's helpful in the requirements analysis phase. You can apply your methodology or Agile framework from the beginning. After choosing the framework, like Agile or Scrum, Azure DevOps provides many features, like user stories, tasks, managing boards, and those kinds of things.

Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace. 

This makes up for any possible deficiency in Azure DevOps features. If you want some capability that Azure DevOps doesn't provide, you can develop your plugin or customize any part of it. The options for customization make it worthwhile for any software development.

What needs improvement?

Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it.

For how long have I used the solution?

I've been working with DevOps for about five years.

What do I think about the stability of the solution?

DevOps is totally stable. And if there are any problems, Microsoft patches them as soon as possible.

What do I think about the scalability of the solution?

When you enter into Microsoft ecosystem, you can scale any part of the product in this ecosystem. For example, you can connect Azure DevOps to Microsoft SharePoint for knowledge or document management. You can connect Azure DevOps to OneDrive for storage. You can connect it with Skype for chatting or Outlook. 

How are customer service and support?

We don't use support from Microsoft. We mostly solve problems by searching for solutions on sites like GitHub and that kind of thing. 

Which solution did I use previously and why did I switch?

I've used Atlassian products like Jira, Confluence, and HipChat, but I prefer Azure DevOps and the Microsoft ecosystem.

How was the initial setup?

It is effortless to set up DevOps. All Microsoft products are user-friendly and easy to install. If you run into any obstacles, you can use Microsoft library or MSDN for any further help that you need. Microsoft provides a lot of wizards that you can use to solve your problem.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer1045596 - PeerSpot reviewer
Project Manager at a government with 10,001+ employees
Real User
Difficult to customize and limited in terms of project management, but is stable and easy to set up
Pros and Cons
  • "I found the Kanban board to be the most useful for my needs."
  • "In comparison to JIRA, I believe DevOps has very poor reporting and metrics support."

What is our primary use case?

We have a number of use cases. One of them is development, which includes several development teams that use source code control and testing support, as well as the entire software development toolset. I only use the front end, which is the project task management part.

How has it helped my organization?

I don't have any metrics on that. I can only give you anecdotal evidence. 

One of the benefits of using a Kanban board is that it keeps track of how long tasks take. People would hold onto tasks for three or four weeks before we started using the Kanban board. However, once we began using the Kanban board, it became more visible. 

We also realized that we needed to divide the tasks into smaller sections, and the tasks lasted an average of a week. As a result, the throughput and velocity increased simply because the Kanban board made them more visible.

What is most valuable?

I found the Kanban board to be the most useful for my needs.

I'm a project manager. I've been working with non-technical teams and training them on agile methodologies. Using a Kanban board is usually the most straightforward way to get a non-technical team started with an online task tracking tool.

What needs improvement?

In comparison to JIRA, I believe DevOps has very poor reporting and metrics support. They've done very little work, and they could benefit greatly from improved reporting and metrics.

Essentially, I would like to see more reporting support.

For how long have I used the solution?

This solution was already in place when I started. I'm not sure when it was first put in place.

I started with the company in May of 2018, and have been using Microsoft Azure DevOps ever since.

We are using the most recent version.

What do I think about the stability of the solution?

Microsoft Azure DevOps is a stable solution.

What do I think about the scalability of the solution?

It is difficult to customize DevOps. It's similar to a product that has had features added to it rather than being completely redesigned. As a result, it has limitations in terms of scalability and customization.

The most successful users are software developers and technical software managers.

How are customer service and support?

I believe it is quite minimal. Microsoft, in my opinion, does not provide adequate support. My solutions are mostly found online. 

With JIRA, you could call someone, and they had a large community of users who could answer your questions. They also had a support department that provided assistance. Microsoft has a lot of information online, but you have to find it, look around its various websites. It is not well supported.

Which solution did I use previously and why did I switch?

I used to work as an engineering manager, a scrum master, and as part of a technical team. JIRA is my preferred tool for this. 

JIRA is a more robust and mature tool. However, as you are aware, JIRA is more modular and requires integration with other parts. DevOps, on the other hand, has everything in one, it combines source code control, release management, and task tracking.

How was the initial setup?

The initial setup is fairly straightforward. It's one of its advantages over JIRA. It is easier to set up because it is a simple product, whereas JIRA is more complex, more mature and complete, and more difficult to set up.

We have two or three technicians who deploy and maintain this solution.

What other advice do I have?

You would really have to do a comparison, and you would need some training. 

It really depends on your project management and reporting requirements. DevOps is simple to use, but it is severely limited in terms of project management. JIRA is complete, but it's a lot more complicated.

I only use it for project management and the tools associated with project management. I know it's popular among those who use it for source code control and release management. It appears to be more satisfactory for that purpose.

I would rate Microsoft Azure DevOps a five out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Test Advisory, Management & Implementation at a energy/utilities company with 51-200 employees
Real User
A complete package with good stability and scalability
Pros and Cons
  • "In Microsoft Azure DevOps, you have a one shop to get everything."
  • "If they could build up requirement traceability metrics, then it would be great."

What is our primary use case?

The purpose is for development and testing from the vendor side. Our company works as a vendor, client, and implementation partner. The vendor provides the product, and we make sure that it's implemented correctly for the client. The vendor uses it for the development and tracking of the requirement and the test cases, executions, and building storage.

My access to these tools is very limited because the DevOps pipeline and DevOps is mainly used by the engineering team of development, but the QA is also part of it. Once those people are established, then we are the extended hands or extended part of that for usage. Once they have the stories and features, they start the test cases and link on it. From that point, we just take it forward and once they have a code pull, then we would pull it and build it and deploy it into some QA enrollment.

There are around 20 people using DevOps in my company.

What is most valuable?

The best tool would be Azure DevOps. There are other tools with AWS and Google, but since Microsoft has solutions for everything, it's easier because it's all their tools. We may be using different tools in order to achieve all those things because they may not have an operating system or a pipeline, so maybe we are using some of the bill tools. In order to achieve DevOps, you may be using a set of different tools and connecting it. In Microsoft Azure DevOps, you have a one shop to get everything.

What needs improvement?

There isn't a requirement traceability matrix format. In ALM, we have a centralized repository of all the requirements in one place. But in DevOps, it works like a product requirement. In ALM we have the centralized repository of requirements where you can go and see the requirement coverage and discovery and so forth. But in DevOps, it has stories and test cases. Once that project is over, nobody is going back into that requirement. It's a good tool for development activity, tracking and getting all those metrics. If they can build up a requirement traceability matrix, then it would be great.

What do I think about the stability of the solution?

I haven't seen any issues with stability.

What do I think about the scalability of the solution?

The scalability of DevOps is good.

How are customer service and support?

We haven't had any issues with technical support. Whatever issues we've had, they were solved.

How was the initial setup?

I didn't see any complexity in the setup because everything is from Microsoft. The development tools and operation tools are coming from one shop, Microsoft, so it's easy to connect, plug in, and establish all those things. For Google Cloud or AWS, it's different because they use different tools in order to achieve what Microsoft is trying to achieve. For example, the CI/CD Pipeline.

Even in ALM or in the DevOps tool, it's initially a one-time setup.

What's my experience with pricing, setup cost, and licensing?

I don't know the pricing of DevOps. It would be much cheaper than ALM because ALM came out as a software product initially. Now they are moving into a cloud and subscription model. In that case, Microsoft is coming from Azure and the cloud and DevOps and software as a service, so it would be much cheaper, but the catch would be that they are trying to get money on all sides, like an operating system, Microsoft Office, or Microsoft Azure DevOps. 

The good part is that it's a complete package, but at the same time, once you've gone with them, you don't have much leverage to split out into some other activities because everything is interconnected and entwined by that time, and it would be like a monopoly. It won't be good if you try to split out at a later point in time because everything is connected—all our Microsoft products like operating systems, OfficeSuite, MS Teams, Azure DevOps, etc.

What other advice do I have?

I would rate this solution 9 out of 10.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Associate Software Development Engineer at Publicis Sapient
Real User
Good for collaboration and has useful application insights
Pros and Cons
  • "Some of the most valuable features are the ease of use and the ability to monitor a lot of things. It has a lot of applications and facilities that meet all the developers' requirements. For example, we can use application insights to get an idea of our application's performance. Since it's cloud-based, it's really good for collaboration and working as a team."
  • "I can't think of anything I would like to improve, since I don't have complete knowledge of the platform yet. I'm sure that as I gain more experience, I will understand it better. The price could maybe be cheaper, but I'm sure I'll have more ideas as to improvements and additional features once I've used it more."

What is our primary use case?

Our primary use case of Azure is to host our web application. We used Azure SQL databases for our project and found it useful to host our web application and make use of all Azure's facilities, such as function apps, API management services, etc. This solution is cloud deployed. 

What is most valuable?

Some of the most valuable features are the ease of use and the ability to monitor a lot of things. It has a lot of applications and facilities that meet all the developers' requirements. For example, we can use application insights to get an idea of our application's performance. Since it's cloud-based, it's really good for collaboration and working as a team. 

What needs improvement?

I can't think of anything I would like to improve, since I don't have complete knowledge of the platform yet. I'm sure that as I gain more experience, I will understand it better. The price could maybe be cheaper, but I'm sure I'll have more ideas as to improvements and additional features once I've used it more. 

For how long have I used the solution?

I have been using this solution for about two months. 

What do I think about the stability of the solution?

This solution is stable. From what I have used it for, it has been pretty efficient. 

What do I think about the scalability of the solution?

This solution is scalable. Most of my team uses Azure DevOps and other Azure facilities, so there are quite a lot of users. 

How are customer service and support?

I haven't felt the need to contact support. I'm not sure if any of my friends or colleagues have, but one thing about Microsoft is the documentation is extremely good. So we barely falter anywhere because if we thoroughly follow the documentation, it's pretty easy to follow the process through. 

How was the initial setup?

The installation is straightforward since it's cloud-based. You can do it yourself. For deployment, we were a team of about 20 people. 

What about the implementation team?

We implemented through an in-house team. 

What's my experience with pricing, setup cost, and licensing?

This product could maybe be cheaper. My organization handled licensing, so I'm not aware of which subscription they have. 

What other advice do I have?

I rate this product an eight-and-a-half or nine out of ten. I have partial knowledge about it, since I haven't really explored everything in proper elaborate detail, but I would definitely recommend Microsoft Azure DevOps to others considering implementation. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer933660 - PeerSpot reviewer
Vice President at a energy/utilities company with 10,001+ employees
Real User
A very stable and scalable solution which seamlessly integrates all ends of the process
Pros and Cons
  • "The solution is good for everything, including end-to-end planning and its deployment and testing."
  • "The solution should have fewer updates."

What is our primary use case?

I do not recall which version we are using. 

The solution is good for everything, including end-to-end planning and its deployment and testing. 

What is most valuable?

I like that the solution is stable and that all ends of the process are integrated seamlessly into the tool. These are the solution's greatest strengths. 

What needs improvement?

The solution should have fewer updates. We need the updates for July. Microsoft tools are sometimes too feature heavy and offer more features than the person actually needs to use. This is why I did not rate it as a ten out ten. 

While the installation did seem to be pretty straightforward, I believe it took awhile, even though I am not aware of the specifics involved. We initially found ourselves struggling with this process.

For how long have I used the solution?

I have been using Microsoft Azure DevOps for around two years. 

What do I think about the stability of the solution?

The solution is very stable. 

What do I think about the scalability of the solution?

The solution is very scalable. 

How are customer service and support?

I feel the technical support to be fine. We have not encountered any issues in this regard. 

Which solution did I use previously and why did I switch?

Prior to Microsoft Azure DevOps, we were using Jira and, before this, KFS. 

How was the initial setup?

While the installation did seem to be pretty straightforward, I believe it took awhile, even though I am not aware of the specifics involved. We struggled with this initially.

What about the implementation team?

The installation was undertaken by a consultant. 

There was a team of, perhaps, five engineers involved. 

What's my experience with pricing, setup cost, and licensing?

I am not aware of any licensing subscriptions for the solution. 

What other advice do I have?

I would very much recommend the solution to others. 

I don't see the need for more integration with other platforms, as the solution is already pretty well integrated, at least, that is, for our needs. 

I rate Microsoft Azure DevOps as a nine or ten out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Download our free Microsoft Azure DevOps Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free Microsoft Azure DevOps Report and get advice and tips from experienced pros sharing their opinions.