We performed a comparison between Chef and Microsoft Intune based on real PeerSpot user reviews.
Find out in this report how the two Configuration Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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 important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"The most valuable feature is the language that it uses: Ruby."
"The product is useful for automating processes."
"The scalability of the product is quite nice."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"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."
"The Autopilot feature is fantastic. It is a Microsoft product, so it deals best with Microsoft operating systems, but it can integrate with iOS, Mac OS, Linux, and Android."
"I can reach devices or computers over the internet. I don't need to worry about the network connectivity between the offices. I can manage any device. That is the most important part."
"It works well if you have a Microsoft environment."
"The ability to wipe data from and reset devices is one of the most important and valuable features. If a device is reported stolen, we can freeze it or wipe the data from it, preventing data leakage."
"The ability to switch between Affinity and non-Affinity enrollment is great."
"We can manage and standardize security across your environment, identify problems, receive alerts, and so on. That's its purpose, and that's also why it's so good."
"It's very informative when there is an error. It allows us to backtrace where the error is and resolve that ourselves. It's a bit of a Swiss Army penknife. We find that it fixes most issues."
"We have one MDM that works with Windows, iOS, and Android."
"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."
"Support and pricing for Chef could be improved."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"I would like to see more security features for Chef and more automation."
"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 solution could improve in managing role-based access. This would be helpful."
"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."
"When Microsoft Intune is used with different android devices it does not always work as it is supposed to."
"They should improve its compatibility with other operating systems such as iOS and Linux. It supports Linux but they still need to work on the iOS part."
"The reports that are generated aren't so great. They don't give a lot of meaning so far, but that could be down to user knowledge than the actual reporting side of things. I'm not a big user of it, but I was a bigger user of MaaS360, and we used to be able to run weekly and monthly reports. In the case of any deviations. we'd get a warning immediately. That's not so easy to do or to get in place for Intune. This could be just a user issue, but when I compare both, that's the only thing that's lacking for me."
"The configuration and pricing can be improved."
"There are items that require improvements. One is the controls from iOS."
"In future releases, I would like to see better integration with Apple products."
"Microsoft Intune lags market leaders, such as Apperian, in its MAM capabilities."
"The reporting could be improved, as it's pretty poor compared to other products of this type."
Chef is ranked 16th in Configuration Management with 18 reviews while Microsoft Intune is ranked 3rd in Configuration Management with 164 reviews. Chef is rated 8.0, while Microsoft Intune is rated 8.0. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of Microsoft Intune writes "We can manage all aspects of our devices from a single console, easy to scale, and quick to deploy". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and SaltStack, whereas Microsoft Intune is most compared with Jamf Pro, VMware Workspace ONE, ManageEngine Endpoint Central, SOTI MobiControl and Microsoft Entra ID. See our Chef vs. Microsoft Intune report.
See our list of best Configuration Management vendors.
We monitor all Configuration Management 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.
