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 most valuable feature is the language that it uses: Ruby."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"The most valuable feature is automation."
"The scalability of the product is quite nice."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"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 product is useful for automating processes."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting."
"It is easy to use. The shared repository is useful. Everything is in one environment."
"It is stable, and we have had no issues with it."
"Everything that's related to the pipeline has been very good."
"The product is easy to use and very stable."
"Technical support has been excellent. On that side, Microsoft is very good. The customer support of Microsoft has really improved this past year. On the cloud side also we are very satisfied because it offers very good support."
"In Microsoft Azure DevOps, you have a one shop to get everything."
"The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"The solution could improve in managing role-based access. This would be helpful."
"In the future, Chef could develop a docker container or docker images."
"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 is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"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."
"Non-functional testing such as security testing, log testing, and performance testing can be improved with a better visualization."
"The solution's roadmap and Gantt charts could be improved."
"I would like to automate notifications on sprint planning. When we are getting to the end of sprint planning, we would be automatically notified."
"The user management in the solution could improve."
"In comparison to JIRA, I believe DevOps has very poor reporting and metrics support."
"Reporting could be better. We would like to see how many applications are onboarded in DevOps and in which phase they are. We would like to know for how many applications we have done only the repository, but we have not yet done the build pipeline or deploy pipeline. Currently, there is no such report. We have to figure it out ourselves. There is no way to check how many applications are completing their build pipelines, how many applications are completing their deploy pipeline, how many are ready to use, and how many pipelines are working."
"I would like to see new features added."
"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."
Chef is ranked 15th in Release Automation with 18 reviews while Microsoft Azure DevOps is ranked 1st in Release Automation with 127 reviews. Chef is rated 8.0, while Microsoft Azure DevOps is rated 8.2. The top reviewer of Chef writes "Easy configuration management, optimization abilities, and complete infrastructure and application automation". On the other hand, 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". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Configuration Manager, SaltStack and BigFix, 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.