It's part of my new role as a DevOps engineer and the cloud engineer. We're migrating our on-premises applications to the cloud-based M365 platform, built on Microsoft Azure. That's the primary use case.
Software Engineer at Mercedes-Benz AG
Significantly improved project management, collaboration, and deployment processes, resulting in faster and more efficient development cycles
Pros and Cons
- "Detailed logs allow us to pinpoint the exact cause of any issues, making troubleshooting efficient and accurate."
- "There is only one key area of improvement for me. The new imaging thing is that there is DevOps, where security is important because it is always lasting. So, to integrate security in our DevOps, that would be nice."
What is our primary use case?
How has it helped my organization?
Azure DevOps supported our agile project's sprint planning and management. It introduced automation, which is still a little bit immature. But our previously manual tasks are now automated, and we've transitioned from deploying ITFAX applications to containerized deployments using images. These are just a few examples.
Moreover, Azure DevOps facilitated our team collaboration and tracking of work items in our projects. We've got the backlog, the boards, the item backlog items, you know, you can see what's approved by the product owner, what's on hold, what's in progress, what's developed and deployed to whichever environment, nine product or product and stuff like that.
So, it's been visible for all to see, from my manager to product owners, technical product owners, developers, and testers; every stakeholder has visibility.
Ever since we adopted Azure pipelines, we saw faster releases. Something that would take us two or three weeks to deploy; we can do it in a couple of hours now. So, the primary benefit is definitely faster development and deployment cycles.
It boils down to - increased customer satisfaction. Quicker releases to testing and production environments - that's the benefit, that's the impact.
What is most valuable?
After each commit, the code automatically goes to Azure DevOps. We can then manually trigger the pipeline if needed. Once the pipeline successfully passes all tests, it deploys the new container image to production, replacing the previous one.
While I'm just gonna stick to Docker, it has really helped developers to confidently commit whenever they feel the analytics are okay to work. On their machines, it records any environment, unlike the old way where we had to click on our machines and then involve the operational team, which sometimes didn't work. With containerization, we already know all the application dependencies needed on the image. It's just one, OS or environment independent.
Moreover, we've experienced the general benefits of Azure Test Plans. One major improvement is the automation of tests. Once automated tests pass, the code progresses to the next stage, minimizing human error inherent in manual testing. This automation extends to reporting as well, providing clear and readily available results. In terms of reducing human error and streamlining reporting, I'd rate Azure Test Plans a ten out of ten.
Additionally, detailed logs allow us to pinpoint the exact cause of any issues, making troubleshooting efficient and accurate. So, for both error reduction and insightful reporting, I highly recommend Microsoft Azure DevOps.
What needs improvement?
There is only one key area of improvement for me. The new imaging thing is that there is DevOps, where security is important because it is always lasting. So, to integrate security in our DevOps, that would be nice.
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.
For how long have I used the solution?
I have been using it for more than a year.
What do I think about the stability of the solution?
It is a stable solution. However, there is always room for improvement. I would rate the stability a nine out of ten.
What do I think about the scalability of the solution?
It is a scalable solution. There are over a hundred end users in my company. Every IT hub uses it.
How are customer service and support?
The customer service and support were quick to support. Usually, we don't need the support. We google our query and easily find the solution on official Microsoft page. So, we hardly need any support.
Which solution did I use previously and why did I switch?
In my previous jobs, yes, we did use different tools. We had a separate team for DevOps team. There was even a "deployment specialist" who dictated deployment times and windows, which could be quite restrictive. So, switching to Azure DevOps has been a massive improvement.
How was the initial setup?
The initial setup is easy. Once the code is committed and the developers sign off, we just go to Azure DevOps, click on "Pipelines," and run the pipeline. That's all, pretty straightforward.
What about the implementation team?
The deployment can be done in-house. However, I was not involved in the deployment process. I'm utilizing it, and so far, it's easy for me.
The pipeline itself can be managed by one person. But when it comes to the entire Software Development Lifecycle (SDLC), from data requirements gathered by the business analyst, system analysts, solution architects, and so on. That part is still manual, it's not automated, and you can't just throw technology at it and expect a one-person team to handle it.
However, for running the pipeline end-to-end, from CI to CD, Azure DevOps allows a single person to manage it. However, developing the application from concept to reality still involves a lot of stakeholders across Azure.
What other advice do I have?
Overall, I would rate the solution an eight out of ten. I would strongly recommend using this solution.
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.

Installation Engineer at CTCI
Ensures comprehensive software development, and facilitates collaboration, automation, and project management, though its initial setup can be complex
Pros and Cons
- "Azure Port is considered the most valuable feature."
- "When comparing with Jira, I find that the task management capabilities in Azure DevOps are not yet fully comprehensive and should be enhanced."
What is our primary use case?
As a software development team, we use Microsoft Azure DevOps extensively across various functions. We rely on its capabilities for source control, enabling us to efficiently manage our codebase and facilitate collaboration. Additionally, we leverage Azure DevOps for test management, including the creation and execution of test cases and test plans. Furthermore, we utilize its features for project planning, tracking work items, and generating weekly documents to ensure smooth progress tracking.
How has it helped my organization?
Azure DevOps has been instrumental in facilitating agile project management and collaboration within our team. We extensively utilize all the features offered by Azure DevOps, enabling us to seamlessly handle tasks such as test management, project management, software defect resolution, and source code management throughout the software development cycle.
We are leveraging the capabilities of Azure Repos for our source code management needs, finding them highly advantageous for our workflow.
Azure Pipelines have significantly improved our deployment process by enhancing automation. We utilize Azure Pipelines to standardize our build process, ensuring consistency in our artifacts and maintaining high-quality outputs. Additionally, it has enabled us to enhance our testing procedures, leading to more efficient issue detection and resolution.
Azure Test Plans have significantly influenced the quality of our releases. Acting as our test engine, they have played a crucial role in ensuring the quality of our software. Post-release, all identified defects are thoroughly addressed, and developers are requested to provide corresponding test cases to prevent recurrence of issues.
What is most valuable?
Azure Port is considered the most valuable feature.
What needs improvement?
When comparing with Jira, I find that the task management capabilities in Azure DevOps are not yet fully comprehensive and should be enhanced.
For how long have I used the solution?
We have been using it for three years.
What do I think about the stability of the solution?
It provides good stability. I would rate it eight out of ten.
What do I think about the scalability of the solution?
I would rate its scalability capabilities seven out of ten. Currently, approximately ten individuals utilize the platform. However, we plan to expand its usage in the future.
How was the initial setup?
The initial setup was fairly complex and time-consuming. I would rate it four out of ten. During the initial setup, we encountered the most difficulty with Microsoft's documentation. It proved to be quite lengthy and lacked clear guidance, which made the setup process challenging. Consequently, we had to explore various additional resources to ensure a smoother setup of Azure DevOps.
What about the implementation team?
For our initial deployment, we allocated one DevOps engineer who dedicated approximately one and a half months to complete the setup.
What's my experience with pricing, setup cost, and licensing?
The cost is quite affordable.
What other advice do I have?
The initialization process may pose some challenges, but I find that the investigation aspect is handled quite effectively. Overall, I believe it's well-suited for both general and specialized DevOps use cases. I would rate it seven out of ten.
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.
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.
Senior .NET Engineer at Advance Storage Products
Helpful in tracking issues and works extremely well in terms of the build time, but it is complicated and should provide the ability to write your own scripts
Pros and Cons
- "The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason."
- "They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server. I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script."
What is our primary use case?
We are using it for the source-code repository, automated bill process, very limited automated testing, and tracking trouble tickets or feature requests. We are using its latest version.
What is most valuable?
The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason.
What needs improvement?
They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server.
I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script.
For how long have I used the solution?
I have been using this solution for a total of four years.
What do I think about the stability of the solution?
From what we've used it for so far, I have not seen any problems.
What do I think about the scalability of the solution?
We're using perhaps 10% of what it is capable of doing. It is far more capable than what we are using right now. With further experimentation and training, I'll probably go from 10% utilization of its capabilities to about 50% or 60% in the next couple of months. We'll never use 100% of what it is capable of doing, but it should handle 95% of everything we need to do. We can always write our own plugins to handle the side things that we need.
Scalability is not really applicable with the code that we write, but the build times and things like that typically take under 15 seconds before we get our responses back. So, it works extremely well.
In terms of the number of users, there are six of us who are software developers. Some of the managers might also partially use the reporting capabilities.
How are customer service and technical support?
I haven't called them up.
Which solution did I use previously and why did I switch?
I've used JIRA and a number of different systems going back almost 20 years. We were doing our development using Microsoft tools, and it just made sense to use what they integrate with. Azure DevOps is the perfect environment because we're using Microsoft technology for other stuff. It is always going to have slight favoritism towards the other Microsoft tools.
How was the initial setup?
The basic setup works very quickly, but there are so many things and options.
What about the implementation team?
We did it ourselves, which is one of the problems. We don't know what we're doing.
What's my experience with pricing, setup cost, and licensing?
I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees.
What other advice do I have?
It is a really complicated product. All DevOps stuff is complicated. The advice that I would give to anybody doing DevOps is to have a goal in mind of what you want to do. Then the product will do what you wanted it to do.
I would rate Microsoft Azure DevOps a four out of ten because I don't know it enough to rate it.
Which deployment model are you using for this solution?
Private 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.
Program Solution Architect at a tech services company with 11-50 employees
Provides good backlog management, but doesn't have an ITSM tool
Pros and Cons
- "The solution's most valuable features are backlog management, build release pipeline, and testing."
- "Microsoft Azure DevOps doesn't have an ITSM tool compared to its competitors."
What is our primary use case?
I work in a consulting firm responsible for adding, managing, and deploying government projects. We are using Microsoft Azure DevOps in one of the projects for backlog management, test planning, test execution, sprint planning, bug fixes, and enhancement requests. We use the solution for anything related to development testing.
What is most valuable?
The solution's most valuable features are backlog management, build release pipeline, and testing. They're easy, intuitive, and increase productivity. Usually, if you don't use such a solution, you end up using Excel. Then, you won't have shared documents, and there'll be no single source of growth. Everybody will keep a different document somewhere, and you will spend a lot of effort reconciling the latest status.
Using Microsoft Azure DevOps makes it really easy for us. Anytime you can see how many bugs are open, you can directly get it out of the tool. The solution's reporting is really easy. You can create ad hoc reports based on management requirements. If you are sitting in a meeting and somebody asks you the number of chain requests, bugs, or enhancements, you can create quick queries and show them the status. I think this directly affects productivity.
What needs improvement?
Microsoft Azure DevOps doesn't have an ITSM tool compared to its competitors. We also use Jira for another project, and Jira supports ITSM or ticketing. Since Microsoft Azure DevOps doesn't have this feature, we have to depend on another solution for service request management for support tickets.
The solution should include ITSM tools and security. DevSecOps are third-party security plug-ins that you can integrate with DevOps. Azure DevOps itself doesn't have anything out of the box. Enabling security so that the solution automatically starts checking things would be a really handy feature.
For how long have I used the solution?
I have been using Microsoft Azure DevOps for three years.
What do I think about the stability of the solution?
We haven’t faced any issues with the solution’s stability.
I rate the solution a nine or ten out of ten for stability.
What do I think about the scalability of the solution?
Since it's a SaaS solution, we haven't faced any scalability or performance issues, and we haven't struggled when we had a lot of users. We have gone through a curve. We started with around ten users. At the peak of the project, we had almost 50 users. Since we are in maintenance, we have come down to 10 to 15 users.
We use 100% of Microsoft Azure DevOps for our project. Everything is within Azure DevOps. If anybody says that we need to work on a feature, the first thing we do is create a DevOps item. So, we don't do anything outside DevOps.
The tool provides the features, but we haven't been able to onboard end users. We are a consultancy firm that works with system integrators and also engages with the end client. We have been able to onboard the system integrators, and we are also using it.
However, the end users still prefer sending emails and documents. If you send them a link to run a test script, they won't do it. So, the end users still prefer the old ways, such as emails and documents.
I rate the solution's scalability a nine or ten out of ten.
How are customer service and support?
So far, we haven't faced any issues in terms of technical support. There is good documentation available if you are looking for support for configuration. So, you usually end up resolving your issues yourself. Since this tool is widely used, you can find help online. People are writing content about this solution, and Microsoft itself has good documentation.
How was the initial setup?
On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a nine out of ten. The solution's initial setup is pretty easy, and the rollout is pretty quick. You can enable it and then keep on modifying and updating it.
What about the implementation team?
It took us less than a week to deploy Azure DevOps. Since we were using a cloud environment, there was no infrastructure requirement. We went on Azure DevOps, created an organization, and then created a project. Inside the project, we selected the type of project.
There are different templates that you can follow, including the CMM-level approach or the basic approach. We selected one of the templates and copied the template. We made some modifications to the template for the project because that template is used for governing steps.
Then, we created depositories, which is pretty quick. In a week's time, we were up and running with backlog management. It took a couple of weeks to complete the automated build and deployment pipelines.
We needed one person to set up the project and one knowledgeable about the build and deployment pipelines. If you have a person who knows how to do the pipelines, you can also configure the project. So, one person is good enough to set up the entire project.
What was our ROI?
We have seen a return on investment with Microsoft Azure DevOps in terms of productivity because it really helps with the amount of time you need to consolidate reporting and planning. The status is always up to date, and the deployment is very streamlined. You can do the entire thing in Excel, but the overhead would be too much, and you would lose out on things. So, team synchronization and productivity are the return on investment with the solution.
I rate the solution’s return on investment a nine out of ten.
What's my experience with pricing, setup cost, and licensing?
The solution's pricing is pretty cheap. The best part of the Azure DevOps and SaaS model is that there's no upfront cost. The tool has a per-user license. It's free for five users, and there is a price above five users. The solution's deployment and licensing costs are very cheap compared to those of its competitors.
The solution's pricing is not fixed. The solution's testing license is $50 per user. It's $15 for normal users who use backlog management. We have two people from the test team and seven from the other team. This is in maintenance.
Since we had a big testing team, we had 15 people in testing and 30 people in backlog management during peak time. You can say it has a 70:30 ratio. Most of the cost is in testing, and the backlog management is really cheap.
On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a three out of ten.
Which other solutions did I evaluate?
Before choosing Microsoft Azure DevOps, we evaluated other options like Jira and HP ALM. Jira is good at ITSM and backlog management, but it is dependent on third-party tools for pipeline deployment.
It's too complex to do product management with HP ALM. It's a good ITSM tool, but the process it follows for product management is very stringent, which is not very flexible for sprint planning. There is too much overhead in HP ALM to do quick sprints.
What other advice do I have?
We are working with the SaaS (Software as a Service) version of the solution, which is on the cloud. Since Microsoft provides the latest upgrades and patches, it should be the latest version.
We start by creating backlog items. Whenever we get a requirement, we log it into Azure DevOps and plan the backlog. The backlog includes what features we need to develop and what tasks we need to assign to each developer. Each developer is part of the DevOps. Once you have created that backlog, we assign it to different developers based on a sprint.
Suppose we are going to run a four-week development cycle. So, we plan the development cycle, pick a few items from the backlog, assign them to that sprint, assign them to the developer, and then manage the execution of that development cycle. Once that's completed, we will transfer it to the test team so they can test it in Azure DevOps.
They have test scripts that are documented in Azure DevOps. They run tests, record videos, and capture screenshots in Azure DevOps. After the test verification, we deploy the solution. In addition to backlog management and product management, we use Azure DevOps for build and release deployment. We don't manually go and build the software.
Our code repository is also part of DevOps. As soon as we check in the new code, Azure DevOps automatically builds the solution and then deploys it in the development environment. Once it's confirmed, the same is deployed to quality and production. We use the solution to do everything end to end, other than ITSM.
Specifically, Azure DevOps is integrated with deployment for us. When we manually deploy a solution, it's prone to errors. We use Azure for website deployment and Azure DevOps for Apple app or Google app deployment.
As soon as the approval is done in Azure DevOps, apps are automatically published. It will publish an app on the Google Play Store, Apple Play Store, and Azure, which we use for web hosting. So, it is integrated with web hosting, Apple Store, and Google Play Store.
The solution does not really need any maintenance. Once you enable the testing solution, you can start creating your test plans and test scripts directly. Every time you do a deployment, you just need to run those test scripts, which is pretty easy. It's more about creating your test script than configuring the tool. Even if I do it in Excel, I need to spend time on that.
The solution's analytics and reporting are pretty easy. We use them very often on an ad hoc basis whenever we discuss and plan what to deploy and what the next steps are. It's pretty easy, and we haven't faced an issue where we weren't able to take out any reports just by doing it on an ad hoc basis. It's pretty easy, and you don't need to write code or anything.
The tool is pretty flexible and easy to use. I suggest starting with the cloud version because you can create your project easily. Since it's free for five users, organizations with budget constraints can start playing with limited users. I would say start with the cloud-based version and start playing with it. Once you get comfortable with it, you can expand it for other projects. The tool serves a wide variety of use cases.
The biggest key trend these days is fast deployments or quick releases. Given how competitive the market has become, you need to keep on adding features to your product. Azure DevOps supports the sprint methodology, which supports fast deployment.
On top of that, it supports automated build release deployment. That was a headache when I started working. Sometimes, you forget a file when deploying in production, and your system will go down. The solution's features support the latest fast or quick deployment trend.
Overall, I rate the solution a seven 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: I am a real user, and this review is based on my own experience and opinions.
Last updated: Jul 10, 2024
Flag as inappropriateFounder at Premium Consulting SAS
Can control the whole cycle, has good documentation, and is stable
Pros and Cons
- "The integration of the whole cycle is the main strength of the tool. If I want to control the cycle with other tools on the market, I would have to use several tools. However, this is not the case with Azure DevOps or TFS."
- "The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project."
How has it helped my organization?
We are a team of 12 consultants specializing in this solution. We have customers with approximately 200 users each, and we have been able to reduce our customers' deployment time by using Azure DevOps or TFS.
Additionally, our customers have been able to measure and improve their development process, by generating some KPI's as 'average defect fixing time', 'effort deviation', and 'velocity' among others, due to the continuous use of Azure DevOps.
What is most valuable?
The integration of the whole cycle is the main strength of the tool. If I want to control the cycle with other tools on the market, I would have to use several tools. However, this is not the case with Azure DevOps or TFS.
What needs improvement?
The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project.
Additionally, I would like to see more powerful dashboards that could be used instead of Power BI. Azure DevOps or TFS does not support graphics from hierarchy queries. It would be powerful to have because some customers don't have Power BI licenses.
For how long have I used the solution?
We have been working with Azure DevOps or TFS for the past 11 years.
What do I think about the stability of the solution?
It is totally stable.
How are customer service and support?
The documentation is good and thus, we have not had to contact technical support very often. However, when we have escalated an issue to technical support, they have been good.
How was the initial setup?
The initial setup can be straightforward if the consultant is knowledgeable.
What's my experience with pricing, setup cost, and licensing?
The pricing is very competitive because of the whole development cycle by Azure DevOps. You don't have to buy and integrate several different tools.
What other advice do I have?
Azure DevOps or TFS is a very good tool for development teams. It's easy to use. However, you would need the help of a consultant who has a lot of experience with the tool. This is because the tool let's you do things in many ways, but not all of them will be the right way to do it. It would be better to invest in the services of an experienced consultant.
Overall, I would rate TFS or Azure DevOps at nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Head Of Technology at Elogroup
Excellent integration; enables us to see all the steps in the lifecycle of our clients
Pros and Cons
- "Provides us with user histories."
- "Templates could be improved."
What is our primary use case?
The first time I used the solution was to create a build for an Oracle application called SOA. We generated all the features in Azure DevOps to create the build and then we created a workflow. We are partners of Microsoft and I'm head of technology.
How has it helped my organization?
We have the histories, and are able to estimate the efforts of each story. It means that I can measure it from each developer and I have the match from each developer. We can also check it from the lead time to see whether there are any problems in storage that may not be mature. It gives us control.
What is most valuable?
We use Gitch as a version control and the integration is very good. We are also using the features for the product backlog that's released every day so we have the user histories. We can track it from the histories to the code. You can see all the steps in the life cycle we use with our clients. We also like to use the estimate integration feature where you have two or three developers that estimate different efforts for each history. I think Azure is easy to integrate with any other type of solution to improve your delivery.
What needs improvement?
I think the templates could be improved. It's not easy making the jump from one project to another so we're now integrating using a different partner. I believe the price could be improved when scaling. It's a simple calculation, the number of users times $11, which is approximately the cost. But if you have a large number of users you should be able to reduce the per user cost the more you scale. I think it's something Microsoft could do for us.
For how long have I used the solution?
I've been using this solution for five years.
What do I think about the stability of the solution?
This is a very mature and stable solution.
What do I think about the scalability of the solution?
We have about 100 users; developers, engineers and admin. The platform doesn't require any maintenance but we have one DevOps engineer to support the DevOps for the applications that we integrate with the platform. There are two types of scalability, the first is scaling my team, moving from 100 to 200 users, which is easy to do. The second is structure but I haven't yet tested scalability in terms of increased structure.
How are customer service and technical support?
Actually, we don't have a lot of experience opening tickets with technical support. All tickets that we did open were dealt with quickly.
Which solution did I use previously and why did I switch?
I used IBM where I worked previously but didn't have a lot of experience with it.
How was the initial setup?
We had some initial difficulties, because the solution is not commonly used here. Jira and Microsoft are the most common solutions but it's not usual to use everything inside the platform. It was a cultural change that we implemented here in our team and to convince them was more difficult than to use the platform itself. We used an integrator for deployment but we don't do that in every case. In some of our deployments, hosting the most popular software development languages, like Java or .NET makes it easy to create the deployment mode. But when you have different platforms on development, it's more difficult to configure. We're on an SaaS platform, so deployment was very easy.
What's my experience with pricing, setup cost, and licensing?
We have 100 users and the cost is $11 per user. There's an additional cost if you want to use the integrated test plan. You have the option to just change your license and you can use the automated test integrator.
Which other solutions did I evaluate?
We looked at Jira Confluence and it was our second option. On Jira, we have our environment in Azure, and it was easier to adopt Azure DevOps instead of Confluence. Because Confluence is specifically for Azure DevOps, we can integrate it with everything that we are already using.
What other advice do I have?
It's very easy to start using this solution because the first five licenses are free. As a result, it's easy to track and compare with other solutions and it's easy to scale.
I would rate this solution a nine out of 10.
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
AWS Trainer at National Vocational and Technical Training Commission
Enhancing productivity and good simplicity with an all-in-one DevOps multitool
Pros and Cons
- "Azure DevOps is highly valued for being an all-in-one solution."
- "A notable improvement would be adding more notifications."
What is our primary use case?
Azure DevOps is primarily used as a DevOps tool rather than an AI tool. It is used for source code management, setting up repositories and pipelines, and it can handle a range of workflows from the DevOps stack.
How has it helped my organization?
The tool helps by being an all-in-one solution where I can store secrets, code, and pipelines. This comprehensive nature has made it valuable and helpful by improving customer productivity and allowing me to perform multiple tasks without needing additional solutions.
What is most valuable?
Azure DevOps is highly valued for being an all-in-one solution. It offers capabilities like source code management, secret storage, pipeline management, and more, making it comparable to a multitool that does not require integration with other solutions. I appreciate it for its scalability and ability to handle different workflows effectively.
What needs improvement?
A notable improvement would be adding more notifications. It would benefit from more seminars or events where Microsoft encourages other users to transition to Azure DevOps.
For how long have I used the solution?
I have been working with Microsoft Azure DevOps for around two years.
What do I think about the stability of the solution?
The stability of Azure DevOps is rated as stable and simple, with no complexity involved. I have not experienced any outages or downtimes in Azure DevOps.
What do I think about the scalability of the solution?
Azure DevOps is highly scalable and receives a rating of ten out of ten. It can handle various volumes of workflows, which makes it effective for different use cases.
How are customer service and support?
I have not communicated with technical support for Azure DevOps.
How would you rate customer service and support?
Neutral
How was the initial setup?
Azure DevOps does not have a complex setup process. It requires Microsoft Azure for the services used, and the product itself is simple to set up.
What's my experience with pricing, setup cost, and licensing?
The pricing of Azure DevOps is rated at five out of ten. It is mid-range pricing. It is considered to offer good value for money even if setting up an agent separately is required.
Which other solutions did I evaluate?
Our discussion mentioned Jenkins as a popular CI/CD product.
What other advice do I have?
Azure DevOps is a very powerful tool with almost every feature necessary for DevOps, so it is recommended to other users.
I'd rate the solution eight out of ten.
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: partner
Last updated: Oct 22, 2024
Flag as inappropriateDevOps specialist at Saudi Credit Information Co. J.S.C.
Maximized CI/CD efficiency with good documentation and management capabilities
Pros and Cons
- "This solution is stable."
- "Service monitoring should be improved."
What is our primary use case?
We are mostly using Microsoft Azure DevOps for the development dashboard and for CI/CD pipelines. We also use it mainly for Git repository management.
What is most valuable?
We are primarily using Microsoft Azure DevOps for its Git repository management and CI/CD pipelines.
What needs improvement?
Service monitoring should be improved. This feature is available for Azure DevOps in the cloud but not on-premise. It can be enhanced to be used with on-premise solutions.
For how long have I used the solution?
I have almost three years of experience working with Microsoft Azure DevOps.
What do I think about the stability of the solution?
This solution is stable. Its stability rating is eight out of ten.
How are customer service and support?
I have not contacted Microsoft technical support; I rely on the documentation.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I did not use a different solution before using Microsoft Azure DevOps.
How was the initial setup?
For me, the initial setup experience would be rated a seven out of ten.
What about the implementation team?
The deployment takes only a few minutes. That said, it depends on the size of the artifact. If the artifact size is large, it will take a bit more time. We did not use any third-party services; we handled it in-house.
What's my experience with pricing, setup cost, and licensing?
I have no idea about the pricing of Microsoft Azure DevOps.
Which other solutions did I evaluate?
I did not evaluate other options. We had to listen, as we were already using the solution.
What other advice do I have?
I recommend Microsoft Azure DevOps. It is user-friendly.
I'd rate the solution 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.
Last updated: Oct 16, 2024
Flag as inappropriate
Buyer's Guide
Download our free Microsoft Azure DevOps Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2025
Product Categories
Application Lifecycle Management (ALM) Suites Release Automation Enterprise Agile Planning ToolsPopular Comparisons
OpenText ALM / Quality Center
Polarion ALM
Rally Software
Nutanix Cloud Manager (NCM)
OpenText ALM Octane
Codebeamer
Jira Align
Jama Connect
PTC Integrity
IBM Engineering Lifecycle Management (ELM)
Digital.ai Agility
Planview AgilePlace
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?
- What are the main differences between Jira Align and Azure DevOps?
- When evaluating Application Lifecycle Management suites, what aspects do you think are the most important to look for?