We performed a comparison between Chef and Microsoft Azure DevOps based on real PeerSpot user reviews.
Find out in this report how the two Release Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The product is useful for automating processes."
"We have had less production issues since using Chef to automate our provisioning."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"Chef recipes are easy to write and move across different servers and environments."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them."
"The solution is scalable."
"The build and release management features are valuable."
"Microsoft Azure DevOps has helped the developers a lot and we are deploying process changes very frequently and simultaneously. A lot of my team members that are developers are updating the code in parallel using Git. Additionally, Microsoft Azure DevOps is providing a very good approval mechanism. Overall it is benefiting by creating efficiency in production deployment and applications, our new releases are running well. The security of secured is good."
"It's a pretty problem-free solution."
"It is stable, and we have had no issues with it."
"They have been lately adding features to the services on a regular basis. Every two weeks, they are adding functionality to Azure DevOps Services to match it with what Azure DevOps Server or on-prem would offer. So, we continue to get more robust functionality. My favorite right now is that they are starting to open up the API availability within Azure DevOps Services. Another thing that I like about Azure DevOps is that you can use it with any of the products that are on the market. You can integrate it with Jenkins and other open-source products to complete that fully functional CI, CD, CT, CM, and CS pipeline. It continues to enhance."
"The creation of test plans is valuable and I like the reporting features."
"The CI/CD pipeline setup is more user-friendly. You can manage various stages, and there are over 400+ plugins available for each stage."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"The time that it takes in terms of integration. Cloud integration is comparatively easy, but when it comes to two-link based integrations - like trying to integrate it with any monitoring tools, or maybe some other ticketing tools - it takes longer. That is because most of the out-of-the-box integration of the APIs needs some revisiting."
"I would like to see more security features for Chef and more automation."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"The tutorials for building pipelines are an area that is a bit technical for a beginner."
"Improving the metrics that are readily available on the dashboard would be very helpful."
"Being more technology-agnostic through ease of integration would be beneficial."
"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."
"Integration and plugins for other tools could better. Like if you want to integrate the DevOps with other tools that are in the market. This could be for the engineering tools to check code quality, application security tools, and DevOps dashboard tools."
"Its price can also be reduced. It would be great if they are a little bit more competitive in terms of pricing because many open-source products are currently available in the market."
"The documentation isn't straightforward."
"Project management could be improved."
Chef is ranked 15th in Release Automation with 18 reviews while Microsoft Azure DevOps is ranked 1st in Release Automation with 126 reviews. Chef is rated 8.0, while Microsoft Azure DevOps is rated 8.2. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of Microsoft Azure DevOps writes "Good support, helpful management capabilities, and great Kanban boards". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Configuration Manager, SaltStack and CFEngine Enterprise, whereas Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and ServiceNow Strategic Portfolio Management. See our Chef vs. Microsoft Azure DevOps 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.
