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.
"Stable and scalable solution for work planning and code collaboration. It's fast, and it offers a good user experience."
"The solution is easy to implement and easy to use."
"We can eliminate some of the middleman processes."
"All of the features related to release management are very good."
"The product is easy to use...It is a stable solution."
"Some of the valuable features are the functionality and the wide range of capabilities."
"I like the tracking and that we can monitor our velocity."
"The simplicity and ease of use are two features that we have found to be most valuable."
"The automation is the most valuable feature."
"Ansible Galaxy is helpful for roles and Git Submodules: No dependency in managing playbooks. Also, fact caching in redis for host/role grp information speeds up execution. Finally, variable management is easy."
"It is very easy to use, and there is less room for error."
"We can manage all the configuration consistency between all our servers."
"The most valuable features of Red Hat Ansible Automation Platform are the agentless platform and writing the code is simple using the Yaml computer language."
"Feature-wise, the solution is a good open-source software offering broad support. Also, it's reliable."
"RBAC is great around Organizations and I can use that backend as our lab. Ingesting stuff into the JSON logs, into any sort of logging collector; it works with Splunk and there are other collectors as well. It supports Sumo and that helps, I can go create reports in Sumo Logic. Workflows are an interesting feature. I can collect a lot of templates and create a workflow out of them."
"The playbooks and the code the solution uses are quite useful."
"It would be very useful if it had better integration with Microsoft Word because we would like to be able to define the priority requirement document and add it to different stages of the backlog."
"Testing is very important. Microsoft Azure DevOps tests very well. However, DevOps teams need to be aware of what they are impacting when someone updates anything on the system."
"The test management section needs to be improved."
"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."
"They could provide clearer guidance on deployment practices for the product."
"Requirements management is an area that can be improved."
"The main issue that I have is the connection speed. Sometimes, the response is too slow. I am based in Taiwan, and I am not sure if it is because of broadband or something else. Its initial configuration is also a little bit difficult."
"The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code."
"For a couple of the API integrations, there has been a lack of documentation."
"Networking needs to be improved."
"There could be more stuff in the workflows. I hope that if I have ten templates with different services on it, workflow could auto-populate all the template-based services."
"The governance features could be improved."
"What I would like to see is a refined Dashboard to see, when I log in: Here are all my jobs, here are how many times they've executed; some kind graphical stitching-together of the workflows and jobs, and how they're connected. Also, those "failed hosts," what does that mean? We have a problem, a failed host can be anything. Is SSH the reason it failed? Is the job template why it failed? It doesn't really distinguish that."
"Accessibility. Ansible uses a CLI by default. Those accustomed to it can find their way and adopt the YAML files easily over time. But, some users are more comfortable using UIs..."
"The solution is slightly expensive, and its pricing could be improved."
"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."
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
Microsoft Azure DevOps is ranked 1st in Release Automation with 126 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 "Good support, helpful management capabilities, and great Kanban boards". 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.