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."I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"The most valuable feature is the language that it uses: Ruby."
"Deployment has become quick and orchestration is now easy."
"The product is useful for automating processes."
"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."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"We have had less production issues since using Chef to automate our provisioning."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace."
"All features are good. Pipelines feature is great, and Boards and Artifacts features are also really good. It is really good at what it does. It is very comprehensive, and it has some really great aspects to it. It is very easy. It is probably one of the easiest to use DevOps tools in the industry, and it is well integrated."
"The user interface is very friendly."
"You get a complete solution with Azure DevOps. You can do everything in one place, starting from requirement gathering until you release the product. It is a reliable, scalable, and handy product."
"It is a well-integrated product in terms of the development lifecycle."
"The product is easy to use and very stable."
"I think the most usable thing is that you can follow the whole progress of the development process. This makes it very useful for us."
"It is easy to use. The shared repository is useful. Everything is in one environment."
"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."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"It is an old technology."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"The agent on the server sometimes acts finicky."
"In the future, Chef could develop a docker container or docker images."
"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."
"Since we are heading to IoT, this product should consider anything related to this."
"Project management could be improved."
"When you compare with Jira, there is a lack of progress features."
"The portfolio is one area where DevOps has room for improvement. Built-in reporting and visualization also could be better. We're using Power BI and Tableau to compile more complex reports and dashboards. Azure DevOps has some out-of-the-box reporting capabilities, but they're very simple. It's usually okay on the team level, but if you have to run a complex report, it's difficult and insufficient, so we use Power BI as an extension."
"When comparing with Jira, I find that the task management capabilities in Azure DevOps are not yet fully comprehensive and should be enhanced."
"I would like to automate notifications on sprint planning. When we are getting to the end of sprint planning, we would be automatically notified."
"Being more technology-agnostic through ease of integration would be beneficial."
"Non-functional testing such as security testing, log testing, and performance testing can be improved with a better visualization."
"Improving the metrics that are readily available on the dashboard would be very helpful."
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.
