We use all the DevOps features and services, like reports, Boards, Pipelines, Artifactory, etc. The interface is interactive and intuitive. The platform visuals and workflow are straightforward in Azure DevOps.
Chief Technical Officer
The platform visuals and workflow are straightforward
Pros and Cons
- "We use all the DevOps features and services, like reports, Boards, Pipelines, Artifactory, etc. The interface is interactive and intuitive. The platform visuals and workflow are straightforward in Azure DevOps."
What is most valuable?
For how long have I used the solution?
We've been using Azure DevOps for three years.
What do I think about the stability of the solution?
DevOps' stability is great. No problems.
What do I think about the scalability of the solution?
The infrastructure is good so far, and expanding our user base isn't a problem. Microsoft takes care of the infrastructure.
Buyer's Guide
Microsoft Azure DevOps
October 2024
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
What's my experience with pricing, setup cost, and licensing?
We are billed for a single license, no matter how many users.
What other advice do I have?
I rate Azure DevOps eight out of 10.
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.
Consultant at a computer software company with 11-50 employees
Reliable, easy to setup, and feature-rich but there should be better integration with GitHub
Pros and Cons
- "I definitely like the pipelines and the ease of management once you're in an enterprise."
- "Definitely, there should be more integration between GitHub and Azure DevOps."
What is our primary use case?
I work as a DevOps Engineer. I use this solution as an end-user.
What is most valuable?
I definitely like the pipelines and the ease of management once you're in an enterprise.
The controlling security, the ease of access, the free plans, and the developer plans.
I also like the licensing structure in general.
What needs improvement?
I would like there to be more seamless integration with GitHub.
Azure DevOps seems to be targeted towards enterprises and GitHub is the ugly sister, so to speak, that you come about in the enterprise.
There is no real interaction between the products, which is a real shame since they are both developed by Microsoft.
Definitely, there should be more integration between GitHub and Azure DevOps.
For how long have I used the solution?
I have been working with Microsoft Azure DevOps for a couple of years, ever since they changed their name from Visual Studio Team Services.
What do I think about the stability of the solution?
Microsoft Azure DevOps is definitely stable.
Which solution did I use previously and why did I switch?
I have experience with Azure Bicep and Paraform.
How was the initial setup?
The initial setup is quite easy.
What's my experience with pricing, setup cost, and licensing?
The licensing structure is good.
What other advice do I have?
Definitely, I would recommend this solution. I would still look into your team goals and what tools you already know.
GitHub is more community-driven, with more modules that are easy to access.
Azure DevOps is more integrated with Azure as a platform, and that is important to consider when you consider DevOps in general or Azure DevOps.
I would rate this solution a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Microsoft Azure DevOps
October 2024
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
Director of R&D and Testing at a recreational facilities/services company with 1,001-5,000 employees
Good monitoring, good support, and good stability
Pros and Cons
- "Monitoring is most valuable."
- "Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials."
What is our primary use case?
We are using it for managing the teams and planning the screens and scope of work. We are also using it for building pipelines for automation of builds.
What is most valuable?
Monitoring is most valuable.
What needs improvement?
Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials.
What do I think about the stability of the solution?
It is stable.
How are customer service and technical support?
Their technical support is pretty good.
What about the implementation team?
Our IT department installs this solution.
What other advice do I have?
Before using this solution, I would advise getting somebody who really knows how to use this solution and learning about how to do customizations based on your organization's needs.
I would rate Microsoft Azure DevOps an eight 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.
Lead solution architect at a recreational facilities/services company with 10,001+ employees
Easy to use and very stable
Pros and Cons
- "The product is easy to use and very stable."
- "The ability to integrate Microsoft Azure DevOps with other platforms and Microsoft products can be improved."
What is our primary use case?
Broadly speaking, we use the product for .net websites, APIs, data integration, migration, data analysis, job orders, and workflows.
What needs improvement?
The ability to integrate Microsoft Azure DevOps with other platforms and Microsoft products can be improved.
For how long have I used the solution?
We have been using Microsoft Azure DevOps for more than seven years.
What do I think about the stability of the solution?
The product is easy to use and very stable.
What do I think about the scalability of the solution?
The product is scalable.
How are customer service and technical support?
We feel our experience with technical support to be straightforward. They have responded to our requests for help or support in good time and make themselves available for questions.
How was the initial setup?
The installation of Microsoft Azure DevOps is straightforward. The steps are already in place and one only need follow them. We were able to handle this by ourselves.
The product is deployed to the cloud and we have five developers responsible for this.
What other advice do I have?
We are using the latest version of the product.
Our organization has five people who are using it.
We plan to continue to use Microsoft Azure DevOps because our development or our environment is one of Microsoft's.
My advice to someone considering implementing the product is that it is good. I work in a Microsoft school so this is the environment with which everyone is acquainted.
I would rate this solution a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
DevOps Manager at a tech services company with 51-200 employees
A DevOps solution with a great pipeline feature
Pros and Cons
- "Everything that's related to the pipeline has been very good."
- "I'd like to have something better for the test plan."
What is our primary use case?
We use Microsoft Azure DevOps to store our code, manage our code, and publish it.
How has it helped my organization?
Before we used Azure DevOps, our team used to promote the code manually. What they did was publish, copy the files and paste them on the server or run lines of code to get our services in production. That takes a lot of time. With the pipeline we're using, that time was reduced by ten times. We're ten times faster now.
What is most valuable?
Everything that's related to the pipeline has been very good. We're using this to promote our code and to secure it. The library and all the stuff that we can manage inside the pipeline is helping us a lot.
What needs improvement?
I'd like to have something better for the test plan. The test plan seems to be really manual even now. There's a lot of stuff to do there, and it could be improved.
Sometimes, it's also difficult for us to handle all the connections with iOS. iOS connections are really very difficult. We're using a different product, which is part of Microsoft, called App Center. But sharing from Azure DevOps to App Center has been difficult. They should try to improve things related to iOS development or iOS production.
For how long have I used the solution?
I've been using Microsoft Azure DevOps for the last five years.
What do I think about the stability of the solution?
I wouldn't complain about stability. Sometimes we have a couple of maintenance windows, which is okay. We actually had a couple of problems, but I don't remember. I would say that it's under normal standards. I wouldn't complain about it.
What do I think about the scalability of the solution?
Microsoft Azure DevOps is scalable. It was easy to grow.
How are customer service and technical support?
If I ever raised any kind of a question to technical support, it was pretty good. I have asked a couple of questions in the technical area. They helped me, and it was good and pretty fast.
Which solution did I use previously and why did I switch?
We used to use another solution, but I don't remember which one. We switched because of a big contract that our company had with Azure. We were going to have our servers with Azure, and it looked like they reviewed the pricing and made the change.
How was the initial setup?
The initial setup was really easy. I didn't even manage this before, but I'm the one who is running this now, and it's pretty easy. Something that made me a little bit confused was all the permissions you have to give to teams and people. Sometimes it's kind of tricky, but it's understandable.
Lately, the deployment's taking a little bit longer than before. I don't know what happened. I'll say that before our deployments took us maybe a couple of minutes. I didn't even measure that, but now it sometimes takes up to 40 minutes or an average of 30 minutes for each deployment.
What about the implementation team?
I implemented Microsoft Azure DevOps by myself.
What other advice do I have?
I would advise potential Microsoft Azure DevOps users to start exploring the free options, which are pretty good. I use it myself as an independent. As soon as you start using it, you'll know that you have to pay because it's a good tool that we can have to manage our code.
On a scale from one to ten, I would give Microsoft Azure DevOps an nine.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Technical Content Writer at a computer software company with 51-200 employees
High performance, easy to use, and reliable
Pros and Cons
- "The most valuable feature is the ease of use and performance."
- "There could more integration with other platforms."
What is our primary use case?
The solution can be used for immutable infrastructure or for microservices.
What is most valuable?
The most valuable feature is the ease of use and performance.
What needs improvement?
There could more integration with other platforms.
For how long have I used the solution?
I have been using this solution for approximately two years.
What do I think about the stability of the solution?
I have found the stability good.
What do I think about the scalability of the solution?
We have approximately 20 people using the solution in my organization.
How are customer service and technical support?
The technical support from Microsoft is really good.
What's my experience with pricing, setup cost, and licensing?
We purchase the solution on an annual basis.
Which other solutions did I evaluate?
I have evaluated AWS.
What other advice do I have?
I would recommend this solution.
I rate Microsoft Azure DevOps 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.
Project Manager at a computer software company with 11-50 employees
Straightforward to set up with good test cases but need more project tracking features
Pros and Cons
- "The pricing seems to be reasonable."
- "I would like to see a bit more project tracking."
What is our primary use case?
I'm using it for specifications of the requirements, for example, or a user for research specifications. I'm also using it to build up test cases right now.
What is most valuable?
Overall, the solution is pretty good. It fulfills most of our requirements.
The stories and test cases on offer are great.
The initial setup was pretty self-explanatory. It was straightforward.
The pricing seems to be reasonable.
What needs improvement?
The solution needs to add the capability for building live documents.
I would like to see a bit more project tracking. There should be more Kanban views. There maybe should be a few more reports. If the reporting was increased a bit, it would make it so that you can check a bit more information around the progress of the project. That would help with project management and progression.
For how long have I used the solution?
I've been using the solution about twice a week for the last few months. It hasn't been that long and it's not a daily occurrence. In total, it's maybe only been two or three months.
What do I think about the stability of the solution?
So far, I've found the solution to be quite stable. There are no bugs or glitches. It doesn't crash or freeze. It's quite reliable.
What do I think about the scalability of the solution?
We have about 3 people using the product currently in my company, and about 30 customers.
How are customer service and technical support?
I've never had to contact technical support. We haven't faced any issues that would require us to. Therefore, I have not idea how they would be. I can't speak to how knowledgeable or responsive they are. At this point, I have no insights to share.
Which solution did I use previously and why did I switch?
I have worked with other DevOps tools previously. I've worked with Jira and Polarion in the past. I haven't necessarily worked with them together or consecutively. It all depends on individual project requirements.
That said, I am not using Polarion anymore.
How was the initial setup?
The initial setup was not overly complex. It was pretty straightforward. A company should have too much trouble with it.
What's my experience with pricing, setup cost, and licensing?
The pricing of the solution seems to be pretty good. It doesn't strike me as being too high.
What other advice do I have?
I'm just a customer and end-user. I don't have a business relationship with Microsoft.
Overall, I would rate the solution at a seven out of ten. It's been okay so far. We're satisfied with the solution overall.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
API | SOA | Integration | Application | Internet of Things Solution Architect at a computer software company with 10,001+ employees
Great all-round functionality with a very good project management feature
Pros and Cons
- "Great project management feature and Git-based repository."
- "The UI could be improved."
What is our primary use case?
We provide this solution to our clients. The company we're currently assisting has had a lot of issues using Jenkins and decided to move the CI/CD pipelines to Azure DevOps. I'm a solution architect and we are partners with Microsoft.
What is most valuable?
The solution offers great features including the project management feature and the Git-based repository. There is also the Azure pipelines and release artifact so you have all the functionality in one tool. It's also a relatively cheap solution.
What needs improvement?
The only area that requires improvement is the interface.
What do I think about the stability of the solution?
Stability is good.
What do I think about the scalability of the solution?
Scalability is good.
How are customer service and support?
The technical support is good.
How was the initial setup?
The initial setup is easy. We had a team of three engineers dealing with implementation.
What's my experience with pricing, setup cost, and licensing?
Licensing costs are very reasonable compared to other solutions. It's a good price.
What other advice do I have?
My only advice would be to go for the cloud version of DevOps, it's a better product.
I rate the solution eight out of 10.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free Microsoft Azure DevOps Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2024
Product Categories
Application Lifecycle Management (ALM) Suites Release Automation Enterprise Agile Planning ToolsPopular Comparisons
Red Hat Ansible Automation Platform
OpenText ALM / Quality Center
ServiceNow Strategic Portfolio Management
OpenText ALM Octane
Rally Software
Polarion ALM
Jira Align
Nutanix Cloud Manager (NCM)
Codebeamer
Jama Connect
PTC Integrity
Buyer's Guide
Download our free Microsoft Azure DevOps Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What Is The Biggest Difference Between JIRA And Microsoft Azure DevOps?
- Which is better - Jira or Microsoft Azure DevOps?
- Which is better - TFS or Azure DevOps?
- What is the biggest difference between Micro Focus ALM Octane and Microsoft Azure DevOps?
- Has anyone tried integrating Azure DevOps with HP ALM?
- MS Azure DevOps vs Jira for test planning and management - which one is the better solution?
- How does Microsoft Azure DevOps compare with GitLab?
- What are your use cases for Microsoft Azure DevOps?
- When evaluating Application Lifecycle Management suites, what aspects do you think are the most important to look for?
- Looking for suggestions - we need a test management and defect tracking tool which can be integrated with an automation tool.