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 important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"We have had less production issues since using Chef to automate our provisioning."
"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."
"Deployment has become quick and orchestration is now easy."
"It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"What I like the most about this product is that it's free and it's secure."
"Azure Pipeline and Azure Release are most valuable. I use Azure DevOps through pipeline and release."
"We can track everything from the requirements stage to the production stage."
"I really like the Microsoft DevOps survey."
"The most valuable features of Microsoft Azure DevOps are high-level protection. The protection is very important to the customers to prevent eavesdropping. eavesdropping is when a hacker tries to get into the solution. With this solution is it difficult for them to do it."
"It is good for monitoring purposes. We are using the build pipelines of Microsoft Azure. They are also valuable."
"What I like the most is the DevOps Boards. It's easy to create a hierarchical project structure, assign tasks to people, and to track their tasks."
"We use all the DevOps features and services, like reports, Boards, Pipelines, Artifactory, etc. The interface is interactive and intuitive. The platform visuals and workflow are straightforward in Azure DevOps."
"I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great."
"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."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"Support and pricing for Chef could be improved."
"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."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"The ability to integrate Microsoft Azure DevOps with other platforms and Microsoft products can be improved."
"We are facing a lot of issues in the development of containerized solutions. We are facing a lot of challenges in this area. They could make the process simpler."
"I would like to see DevOps have the ability to give us something with a compatibility or traceability matrix."
"Reporting across multiple projects could be improved."
"They have to add more features such as schedules and more flexibility in the platform."
"Its setup is quite complex."
"Some of the queries, the way they're built, need to be looked at. We need better query tools."
"Compared to JIRA, I think Azure DevOps is missing some management elements, like some reporting features. It would be helpful if some things were clearer when we're adding attributes. For instance, sometimes we want to add some categories or attributes, and it's not so easy."
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, BigFix, SaltStack and Microsoft Configuration Manager, 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.