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.
"It is stable, and we have had no issues with it."
"The most valuable aspect of Azure DevOps for me is its robust version control functionality, which is critical for our workflow."
"DevOps is easy to use because we can arrange each task in a project and follow up with the testing, development, and business teams. We manage everything through this."
"It's graphical representation and tools are easy to use."
"Microsoft has good integration with its other products, such as Office, Teams, et cetera."
"Monitoring 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."
"There are a lot of helpful features available for tracking dependencies."
"The biggest thing I liked about Ansible is the check mode so that we can verify, after we've pushed, that the config there is actually what we intended."
"The initial setup is straightforward."
"It is all modular-based. If there is not a module for it today, someone will write it."
"The initial setup is easy and takes a few hours to complete."
"The most valuable features of the solution are automation and patching."
"Ansible Tower provides a GUI, which is an enhancement, and a well-liked feature by operation teams."
"I like the agentless feature. This means we don't install any agent in worker nodes."
"The automation is the most valuable feature."
"They do very frequent releases, there's a complete change in UI kind of stuff. Sometimes it feels like they change it too often."
"Templates could be improved."
"While reporting in Azure DevOps is a robust capability, there's always room for enhancement, particularly in providing more granular reports."
"Azure DevOps is set up more for development and less for testing. If it is set up correctly, everyone can use it better, but it was set up from a development point of view, which means it is lacking in what I need from a testing perspective. Just like any other tool, it depends on how it is configured. I am not happy with the way it is set up. It is configured more from a development side, and it doesn't necessarily cater to all the other areas that probably need to use it, such as testing data, etc."
"The test management section needs to be improved."
"Its setup is quite complex."
"The tutorials for building pipelines are an area that is a bit technical for a beginner."
"The installation time of this solution depends on the environment it is being implemented in. We had a couple of projects that took around two weeks of implementation. This included the whole integration of the DevOps and everything together."
"There are some options not available in the community edition of the solution."
"The job workflow needs to be worked on. It's not really clear to how you actually link things together. What they probably could do is provide an example workflow on how to stitch things together. I think that would be very helpful."
"When you set up Playbooks, I may have one version of the Playbook, but another member of the team may have a different vision, and we will not know which version is correct. We want to have one central repository for managing the different versions of Playbooks, so we can have better collaboration among team members. This is our use case for using Git version control."
"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..."
"One problem that I'm facing right now is the mismatch between the new version of Python and Ansible. Sometimes it's Python 2, and sometimes it's Python 3. When things get a bit dicey, I wish that Ansible would solve this issue by itself. I don't want to have to specify if it is Python 3 or version 2."
"If we have a problem with some file and we need to get Red Hat to analyze the issue and the file is 100GBs, we'll have an issue since we need to provide a log file for them to analyze. If it is around 12GB or 13GB, we can easily upload it to the Red Hat portal. With more than 100GBs, it will fail. I heard it should cover up to 250GB for an upload, however, I find it fails. Therefore, Red Hat needs to provide a way to handle this."
"The documentation for the installation step of deployment, OpenStack, etc., and these things have to be a bit more detailed."
"Ansible has just been upgraded, and the only issue that we are seeing at the moment is that the user interface can be slow. We're currently investigating the refresh period with Red Hat when you click a job and run a job. It seems that the buffer no longer runs in real-time. We haven't discovered whether that's partially an issue with our environment, but Red Hat has come back and said that they're working on a couple of bugs in the background. We've upgraded to that version in the last six months, and that's the only issue that we've seen."
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
Microsoft Azure DevOps is ranked 1st in Release Automation with 124 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.
