We performed a comparison between Microsoft Azure Devops and Red Hat Ansible Automation Platform based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Overall, the two solutions are very comparable. They are both easy to deploy and they both have good features.
"You can have test cases in DevOps but not in JIRA. And, DevOps has advantages in terms of executing those test cases."
"It is a cloud-based system. So, it is stable and scalable."
"Most of the features are very valuable for us, especially the source code control and task management."
"All features are good. Pipelines feature is great, and Boards and Artifacts features are also really good. It is really good at what it does. It is very comprehensive, and it has some really great aspects to it. It is very easy. It is probably one of the easiest to use DevOps tools in the industry, and it is well integrated."
"The most valuable features of this solution are the CI/CD pipeline, and the testing automation."
"If someone is considering developing and deploying the infrastructure in this solution, then using this tool is perfect because it's fully integrated with the pipelines and with a server core repository."
"Great project management feature and Git-based repository."
"The most valuable feature is the ease of use and performance."
"The API for exposing all our infrastructure services is the most valuable feature."
"We can manage all the configuration consistency between all our servers."
"Having the Dashboard from an admin point of view, and seeing how all the projects and all the jobs lay out, is helpful."
"Ansible Tower provides a GUI, which is an enhancement, and a well-liked feature by operation teams."
"I like the fact that Ansible is agentless."
"The automation is the most valuable feature."
"It is quick to production. It has an API in the back which allows for integrations."
"I like being able to control multiple systems and push out updates quickly with just a couple of clicks of a button and commands. I like the automation because it is a time saver."
"I would like to see DevOps have the ability to give us something with a compatibility or traceability matrix."
"It is very difficult to integrate the product with third-party tools."
"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."
"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."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"At times, our development work encounters issues, particularly when executing numerous CI/CD processes."
"With an ecosystem that has been up and running for some time, you won't have the full-flexibility that you would have with a new ecosystem."
"This product would be improved if the helpdesk were included."
"In Community, there's a lot of effort towards testing, standardizing, and testing for module development to role development, which is why Molecule is now becoming real. Same thing with Zuul, which we are starting to implement. Zulu tests out modules from third-party sources, like ourselves, and verifies that the modules work before they are committed to the code. Currently, Ansible can't do this with all the modules out there."
"We are not using the Dashboard a lot because we have higher expectations from it. The default Dashboard from Tower doesn't give that much information. We really want to get down into more than if the job succeeded or what was the percentage of success. We want to get down to task-level success. If, in a job, there are ten tasks, we want to see this task was a success, and this was not, and how many were not. That's the kind of granularity we are looking for, that Tower does not give right now."
"What we need is model-driven, declarative software infrastructure management. However, things tend to break with new versions, requiring a lot of work to fix…The focus should be on improving the support for Ansible in the area of AI coding."
"There are some options not available in the community edition of the solution."
"For a couple of the API integrations, there has been a lack of documentation."
"We would like support for the post-integration of this product before cloud frameworks because right now their approach is to avoid using on-premises activities and move everything to the cloud."
"The support could be better."
"I have seen indications that the documentation needs improvement. They are providing a "How to Improve Your Documentation" presentation at this conference."
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
Microsoft Azure DevOps is ranked 1st in Release Automation with 127 reviews while Red Hat Ansible Automation Platform is ranked 3rd in Release Automation with 58 reviews. Microsoft Azure DevOps is rated 8.2, while Red Hat Ansible Automation Platform is rated 8.6. The top reviewer of Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". On the other hand, the top reviewer of Red Hat Ansible Automation Platform writes "Capable of broad integrations with easy-to-operate infrastructure and user controls". Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and Asana, whereas Red Hat Ansible Automation Platform is most compared with Red Hat Satellite, Microsoft Configuration Manager, VMware Aria Automation, Microsoft Intune and BMC TrueSight Server Automation. See our Microsoft Azure DevOps vs. Red Hat Ansible Automation Platform report.
See our list of best Release Automation vendors.
We monitor all Release Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.