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 a cloud-based system. So, it is stable and scalable."
"The most valuable feature is the complete integration between test cases, pipelines, and issue management."
"The work items option is incredibly flexible."
"The most valuable feature is the ease of use and performance."
"We are able to generate many different types of reports from Azure."
"In Microsoft Azure DevOps, you have a one shop to get everything."
"The most valuable feature of the solution is task management."
"It is good for monitoring purposes. We are using the build pipelines of Microsoft Azure. They are also valuable."
"The initial setup is straightforward."
"It is very easy to use, and there is less room for error."
"The API for exposing all our infrastructure services is the most valuable feature."
"I like the inventory management. It's a very nice, simple, concise way to keep all that data together. And the API allows us to use it even for things that are not Ansible."
"Ansible Tower offers use a UI where we can see all the pushes that have gone into the server."
"One of the most valuable features is that Ansible is agentless. It does not have dependencies, other than Python, which is very generic in terms of dependencies for all systems and for any environment. Being agentless, Ansible is very convenient for everything."
"Ansible provides great reliability when coupled with a versioning system (git). It helps providing predictability to the network by knowing exactly what's being pushed after validating it in production."
"It has improved our organization through provisioning and security hardening. When we do get a new VM, we have been able to bring on a provisioned machine in less than a day. This morning alone, I provisioned two machines within an hour. I am talking about hardening, installing antivirus software on it, and creating user accounts because the Playbooks were predesigned. From the time we got the servers to the actual hand-off, it takes less than an hour. We are talking about having the servers actually authenticate Red Hat Satellites and run the yum updates. All of that can be done within an hour."
"I have not been able to use the integration with automation features, such as test management automation, with a framework that is written in Java."
"It is not that intuitive. Sometimes, it is hard to find some of the functions. I would like to have an old-fashioned menu structure to be able to easily find things. Its environment setup is not very good. They should improve the way it is set up for different screens and make it easier to find functionalities and maintain team members."
"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."
"I think that the integration is to some extent, immature."
"It should be able to handle the different types. There is ecosystems engineering, and there is software applications engineering. There is a need to bring these teams together, but the disciplines don't integrate very well, and so it won't work."
"The solution's roadmap and Gantt charts could be improved."
"The solution should have fewer updates."
"Something that could be improved is the initial setup with the integration of ReadyAPI."
"It can use some more credential types. I've found that when I go looking for a certain credential type, such as private keys, they're not really there."
"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."
"The user interface on the Ansible Tower product could be better, but it is functional."
"I have seen indications that the documentation needs improvement. They are providing a "How to Improve Your Documentation" presentation at this conference."
"On the Dashboard, when you view a template run, it shows all the output. There is a search filter, but it would be nice to able to select one server in that run and then see all that output from just that one server, instead of having to do the search on that one server and find the results."
"The solution should add a nice self-service portal."
"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 area which I feel can be improved is the custom modules. For example, there are something like 106 official modules available in the Ansible library. A year ago, that number was somewhere around 58. While Ansible is improving day by day, this can be improved more. For instance, when you need to configure in the cloud, you need to write up a module for that."
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.