Try our new research platform with insights from 80,000+ expert users
Software Architect at EML
Real User
Easy to implement, good CD pipeline, and very stable
Pros and Cons
  • "The initial setup is quick and easy."
  • "The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code."

What is our primary use case?

We normally use DevOps. On the application, everything has gone DevOps, however, we don't use the functions. All applications developed there have gone under Azure or AWS. We normally develop them to be able to not be dependent on anything, so if we want to deploy them in another environment, we can deploy them easily. If we want to use it in Azure, we use it in Azure. If we want AWS, we use it in AWS.

What is most valuable?

I like the CD pipeline. It's the most valuable feature for us. It's so easy to integrate into the CD/CI environment. I mostly love that one.

The initial setup is quick and easy.

What needs improvement?

The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code. 

If you want to use the DPR it's a bit harder due to the fact that it's only 30 days.

For how long have I used the solution?

We've been using the solution for a year and a half at this point.

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.
844,944 professionals have used our research since 2012.

What do I think about the stability of the solution?

The stability of the product has been good so far. I can't say that I've witnessed glitches. There aren't bugs. It doesn't crash or freeze. It's reliable, as far as I can tell.

What do I think about the scalability of the solution?

We don't have any issues with the scalability of the solution. If we need to, we're able to scale.

How are customer service and support?

We've never contacted Microsoft for technical assistance. 

We are Microsoft partners. We have several Azure experts on our development team, and we have a tech that came from the US and did the training for us. We have a very strong understanding of the product and therefore we don't need help with troubleshooting or anything of that nature.

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

We also currently use AWS, however, I prefer Microsoft's solution as it's a bit easier to use overall.

How was the initial setup?

We did not find the initial setup to be complex. The implementation is straight forward. 

Deployment is quick and typically only takes a few days or so.

We have ten people that handle maintenance. They are in different parts of the world. We have two in Australia, for example, and two in the USA.

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

The cost can get pretty high if you aren't paying attention to what you are doing.

What other advice do I have?

We're partners with Microsoft.

I'd highly recommend Microsoft, and I recommend it more than any other solution. Everything is very simple and straightforward. The only worry for some organizations may be the cost. You need to be really, really careful.

I'd rate the solution overall nine out of ten. I think it's really, really great. If the functions were a bit better, I'd give it a full ten out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner

PeerSpot user
reviewer1850940 - PeerSpot reviewer
Freelance at Self
Real User
Top 20
Great automation with version control and expands well
Pros and Cons
  • "The most valuable feature is automation with version control."
  • "It is essential that you get buy-in from the top management down to everyone in the pipeline."

What is our primary use case?

The main use of this solution are to combine software development and IT operations. Also, we use it for automation with version control and microservices. Automation is a core principle for achieving DevOps success and CI/CD is a critical component. 

The application of continuous delivery and DevOps to data analytics has been termed DataOps. DevOps focuses on the deployment of developed software, whether it is developed via Agile or other methodologies. ArchOps presents an extension for DevOps practice, starting from artifacts, instead of source code, for operational deployment.

How has it helped my organization?

This solution has offered lots of improvements. The most important improvement was to provide continuous delivery with high-quality software. It helps with version control with automation using CI/CD components. It also helps to develop software using the agile methodology. 

The ability of different disciplines (development, operations, and infosec) to achieve outcomes has been great. Increased focus on test automation and continuous integration methods are helpful. It helps release new features continuously into large-scale high-availability systems while maintaining a high-quality end-user experience.

What is most valuable?

The most valuable feature is automation with version control. 

DevOps initiatives can create cultural changes in companies by transforming the way operations, developers, and testers collaborate during the development and delivery processes. We can release new features continuously into large-scale high-availability systems while maintaining a high-quality end-user experience. 

Adopting DevOps will also help eliminate the old and monotonous way of agile activity among big IT teams like network, Storage Team, Linux/Unix, Windows, etc.

What needs improvement?

It’s commonly observed that you cannot just change a company’s culture on command. You can influence the culture, shift it, and while it can evolve over time, it’s nearly impossible to just instruct all employees to simply change the way they think and act about specific things. 

The culture of any organization starts at the top of the leadership hierarchy and trickles down throughout, filling every empty space. It is essential that you get buy-in from the top management down to everyone in the pipeline. 

In order to do this, all involved need to understand the advantages the shift is going to have on the organization and on the team members.

For how long have I used the solution?

I've been using the solution for the last two years.

What do I think about the scalability of the solution?

The scalability is very good.

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

We didn't use any solution before.

Which other solutions did I evaluate?

We also looked at AWS.

Disclosure: I am a real user, and this review is based on my own experience and opinions.

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.
844,944 professionals have used our research since 2012.
Derek Smith - PeerSpot reviewer
Development and Release Compliance Officer at a computer software company with 1,001-5,000 employees
Real User
A reliable ecosystem with the capability to expand as needed
Pros and Cons
  • "The solution is scalable."
  • "The interface is very bad."

What is our primary use case?

We produce multiple different software for different markets in different countries. It's really for everything you can possibly think of, from online games to financial systems, to payment gateways, to APIs, to service desks, back-office analysis tools, admin tools, et cetera. We use it for anything and everything really.

What is most valuable?

The solution is great due to the fact that it's kind of an entire ecosystem. I'd say the work items are probably the most valuable aspect.

The stability has been great.

The solution is scalable. 

What needs improvement?

The interface is very bad. It's an aspect that really needs to be worked on. It is going to probably get the developers to start abandoning work items.

Our initial setup was quite complex. 

The presence of Microsoft in the country is limited.

For how long have I used the solution?

I've used the solution since it came on the upgraded from Team Foundation Server - about ten years. We've used it for a very long time. 

What do I think about the stability of the solution?

The stability has always been really good. There aren't bugs or glitches and it doesn't crash or freeze.

What do I think about the scalability of the solution?

We've found the scalability to be good. We have about 2,000 users on it right now. We haven't had any issues with scaling as needed. 

How was the initial setup?

For us, the initial setup was extremely complex due to the multiple organizations we had on the go. We actually had to abandon our initial rollout and rethink the whole process though. 

I'm in compliance, and therefore cannot speak to what the maintenance process is like for the solution. 

What about the implementation team?

We had a combination of both in-house and vendor help with the setup process. We've got enterprise agreements with Microsoft, so they always give us resources to assist with our deployments. We already had TFS deployed, so it was an upgrade, really.

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

I don't deal with licensing. I can't speak to how much the solution costs.

What other advice do I have?

I'm just a customer and an end-user.

I'd advise new users to plan very carefully the way that they would like to set up projects. The model that you choose is extremely important and you might have to do a lot of rework if you don't get it right the first time.

I'd rate the solution an eight out of ten. It's Microsoft. It's backed by the mighty, mega Microsoft. You can't get fired for choosing the top product run by a top multinational company. The downside for us here is, in South Africa, there are only two points of presence. For the data, if it's fully hosted, we only have Capetown and Johannesburg. When it comes to back hall speeds for internet, it could be better if we had points of presence in all the major cities, however, I suppose it's too much investment for Microsoft to make.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.

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: I am a real user, and this review is based on my own experience and opinions.

PeerSpot user
Senior Soft Engineer at SECP
Real User
A user-friendly Azure DevOps server with a great user interface, but the testing environment could be better.
Pros and Cons
  • "It has a good GUI, and it's very user-friendly."
  • "The testing environment and different pipelining concepts can be improved."

What is our primary use case?

We are exploring this solution. There is not enough protection in the environment at the moment. It's been almost six months since we started the process of exploring the DevOps environment in Microsoft Azure DevOps.

We have a customized development methodology so that it is easily marked to our existing environment. Currently, we required that all these systems blend easily in this one environment. We can actually use all the large frameworks within DevOps properly and automate most of our support, starting from planning through support to deployment.

What is most valuable?

It has a good GUI, and it's very user-friendly. It is also a familiar environment as we are used to it. All our users are very comfortable working with it. I think the Azure methodology and all those DevOps features in the dashboard are very effective in our environment. 

It's very implementable in our environment compared to the other DevOps environments which we experienced. I won't name them, but this one part of DevOps we have found very easy in our environment because the infrastructure there is fairly supportive and very integrable to the current DevOps environment we use.

What needs improvement?

The testing environment and different pipelining concepts can be improved. It can also be more user-friendly. They can actually incorporate all those other features, current tools and have those mind maps.

They could add some good analytic features. I think they can be more enriched with some good reporting features. They can also improve the designing tools.

For how long have I used the solution?

We have been using Microsoft Azure DevOps for about six months. 

What do I think about the stability of the solution?

Microsoft Azure DevOps is a stable product. I feel it's stable enough for us at the moment. 

How was the initial setup?

The initial setup is not overly complex. It's fairly straightforward. Other than the Java environment variables which lack documentation, it's not complex and easy to follow.

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

The main agile features are very expensive.

What other advice do I have?

On a scale from one to ten, I would give Microsoft Azure DevOps a seven.

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: I am a real user, and this review is based on my own experience and opinions.

PeerSpot user
Ismail Kiswani - PeerSpot reviewer
Manager at Al-kiswani
Real User
Top 20
Good CI/CD pipeline and testing automation that is both stable and scalable
Pros and Cons
  • "The most valuable features of this solution are the CI/CD pipeline, and the testing automation."
  • "They have to add more features such as schedules and more flexibility in the platform."

What is our primary use case?

We are using this solution for CI/CD projects, for Scrum, Agile planning, testing, and business management system solutions. 

We are also using it for continuous integration, and continuous delivery of DevOps.

I am also using the Git Repositories, which is the main source control for me in the organization. We were using it on-premises and now planning to move it to the Cloud.

They are calling it repository and they are supporting an old protocol, which is a popular protocol called Git repository.

What is most valuable?

The most valuable features of this solution are the CI/CD pipeline, and the testing automation.

It's good that they are bringing more options to this environment, and to deploy to virtual machines.

What needs improvement?

The testing agents needs to be improved, they need to work on it.

They can enhance the areas related to continuous integration and build automation. They can add more technologies for the build.

The integration with the Azure infrastructure as a code and include more templates for infrastructure as a code in the continuous integration phase and the build phase.

They can add more flexibility to the continuous deployment.

Artifact management is also an area that needs some enhancements.

I think automation and integration with the CI/CD lifecycle it's good but it's using agents.

I am using a different tool for testing automation because I have not found any use cases on it. This feature is not covered. I'm using only testing and business management. I'm not using the testing automation feature that is provided by Azure DevOps.

I would like to see more integration with other platforms and more flexibility.

They have to add more features such as schedules and more flexibility in the platform. This will allow me to build my space and time based on the schedule and based on a calendar.

I would also like to see a release calendar so that I can plan my releases based on my sprints. 

This is required and it would give this solution more maturity. Between Scrum, Agile Planning, or Project planning with the build and deploy prophecies.

For how long have I used the solution?

I have been using Microsoft Azure DevOps for three years.

We are using the latest version of this solution.

What do I think about the stability of the solution?

It's a stable solution. We have not experienced any issues.

What do I think about the scalability of the solution?

It's a scalable product. We have more than 50 users in our organization using this solution.

I plan to continue using it in the future.

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

Previously, I used TeamCity, Jenkins, I used Chef, and many other technologies.

How was the initial setup?

The initial setup is straightforward, it's a cloud service, so it's plug and play.

What other advice do I have?

I would recommend Microsoft Azure DevOps for other users who are interested in using it.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.

PeerSpot user
reviewer1260639 - PeerSpot reviewer
Chief Digital Officer (CDO) at a financial services firm with 201-500 employees
Real User
Easy to use, stable, and helps speed up production
Pros and Cons
  • "Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting."
  • "Some of the queries, the way they're built, need to be looked at. We need better query tools."

What is our primary use case?

We primarily use the solution for our Agile teams, however, we started off using it with our executive suite. Our executive team now meets in sprints every day. Sometimes it's a short 15 minutes, other times it can be up to an hour. We have two-week sprints and daily scrums associated with it. We've also rolled that down from the executive. We've got seven formal Agile teams running throughout the organization across our businesses. We probably have at least 40% of our staff now trained in Agile and using DevOps to execute the projects.

How has it helped my organization?

As an Agile team, we're now able to move much faster than we could, even pre-COVID.

What is most valuable?

Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting. That in itself has had a huge effort on the number of meetings. In the past, you would almost wait a month before you could get all the executive teams together. Now, we've got meetings daily. Due to the regular meetings, we're utilizing daily scrums and two-week sprints, and we've been able to move a lot faster than we've ever had before as far as initiatives. 

Frankly, throughout this whole COVID situation, being able to respond the way we have to some of the changes that were going on has been amazing. I don't think that would have happened if we weren't an Agile team.

What needs improvement?

There are a lot of features that we could probably work with a bit differently as we learn more about the tool. Right now, we're just really using it from a task management perspective. We've only been using it a year. There may still be more to learn and unpack.

Some of the queries, the way they're built, need to be looked at. We need better query tools.

Being able to report back to boards, to regulators, and the activities and stuff would be helpful. The queries do require somebody else to actually write them. There should, however, be a way to make things a little simpler in that space. Right now it's on us to figure out how to get better at making queries effectively and in such a way we're just not reporting on tasks complete.  

We track the associated feature story. In many ways you can actually go back and see the story, and see the progress you've made on initiatives due to the fact that you can see all the decisions that have been made along the way. If there's a way that person could dig into that and pull more information or insights, that would be very helpful as it would assist us in improving future projects or even help us forecast on an existing project. 

For how long have I used the solution?

I use the solution daily. We launched it in the company in January. We've been using it across all our Agile teams here for 12 months here.

What do I think about the stability of the solution?

The stability of the solution is very good. I haven't had issues with bugs or glitches. It doesn't crash or freeze. It's a reliable solution.

What do I think about the scalability of the solution?

The solution's level of scalability is good. We're a smaller organization. We've only got 300 people in total, and out of those, probably 40% of our entire staff use the product. About 120 people probably are in there on a daily basis. That's everyone from executives down to programmers. It's extremely cross-functional across our organization.

How are customer service and technical support?

I haven't had to reach out to DevOps themselves personally, so I wouldn't have experience there. However, if we ran into any issues, my technology teams would contact them.

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

We didn't previously use a different solution. That's why we looked for an automation tool. We switched to DevOps mostly due to the fact that our development team was utilizing DevOps as part of their own Agile operations. A number of teams were also already sort of experienced. There are a number of individuals in the company who were experienced that way, and we had homegrown support in some ways when we launched it. It just made sense to go with DevOps as opposed to bringing in something new.

How was the initial setup?

The initial setup wasn't complex. It was pretty straightforward. We didn't run into any issues that complicated the process of implementation.

Which other solutions did I evaluate?

We did look at Jira briefly, however, it didn't look that different from DevOps and we knew many of our team members were already comfortable with this solution so we didn't pursue it.

What other advice do I have?

We're just Microsoft customers. We don't have any business relationship with the company.

I'm not sure which version of the solution we're using.

I'd strongly recommend the solution to other organizations. I can't see us ever reversing back now after being on this for a year.

Overall, I would rate the solution at an eight out of ten. It's relatively easy to use and it does what we need it to do.

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: I am a real user, and this review is based on my own experience and opinions.

PeerSpot user
reviewer1390839 - PeerSpot reviewer
Senior Project Manager at a marketing services firm with 10,001+ employees
Real User
Good traceability and dependency-tracking features
Pros and Cons
  • "There are a lot of helpful features available for tracking dependencies."
  • "Improving the metrics that are readily available on the dashboard would be very helpful."

What is most valuable?

The key thing I find benefits me is the ability to track right from the feature and determine what has happened. I have a direct link to the test and the metrics that are available.

There are a lot of helpful features available for tracking dependencies.

What needs improvement?

The dashboard could be improved. Although there is flexibility in configuring it, there are some metrics that we have to configure ourselves. Improving the metrics that are readily available on the dashboard would be very helpful.

I would like to see better integration with third-party solutions, where if they are part of the DevOps pipeline then the reporting could be made available on the dashboard.

Having some form of check modeling integrated into Azure would be useful.

For how long have I used the solution?

I have been using Azure DevOps for the past four years.

What do I think about the stability of the solution?

We have had no issues in terms of stability.

What do I think about the scalability of the solution?

The offerings in terms of scalability are good.

How are customer service and technical support?

We have not had to depend much on Microsoft support for DevOps and project management. However, I can say that the general support that we get for Azure is good.

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

I have some experience with Jira from Atlassian, although I have worked with Microsoft Team Foundation Server from the beginning.

How was the initial setup?

The initial setup was straightforward. While we were migrating, we had training from Microsoft, which was helpful.

Which other solutions did I evaluate?

I haven't really looked into other options.

What other advice do I have?

Overall, this is a good product and one that I recommend. The features it has have helped us, especially with tracking dependencies.

I would rate this solution an eight out of ten.

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 has a business relationship with this vendor other than being a customer: Partner

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.