

Chef and Microsoft Intune both compete in the IT management space, focusing on configuration management and device management, respectively. Chef seems to have the upper hand in terms of customization and handling large-scale infrastructures, while Intune excels in integration with Microsoft services and mobile device management.
Features: Chef is known for its robust configuration management capabilities and seamless integration with third-party tools. It offers provisioning, automation, and scalability, which are crucial for managing large-scale infrastructures using Ruby. Microsoft Intune provides comprehensive device management, integrating well with Microsoft 365 and Azure. It excels in mobile device management, particularly for Windows, and automates security and patching processes efficiently.
Room for Improvement: Chef could improve its user-friendliness and expand its integration capabilities, especially concerning modern technologies and containers. Resolving existing functionality issues could also enhance its offering. Intune needs to address its limitations in MacOS support, boost its security features, and improve integration with Apple devices, along with delivering more intuitive configurations.
Ease of Deployment and Customer Service: Chef is deployable across various cloud environments, leveraging community support, though it often lacks prompt vendor support. Intune operates primarily in public and hybrid clouds, benefiting from integration with Microsoft services but facing challenges in providing timely vendor support. Chef users frequently lean on community forums for assistance, while Intune users experience direct support delays, highlighting the need for both products to enhance support structures.
Pricing and ROI: Chef's pricing model can be complex due to per-node charges but offers ROI by saving time and reducing manual operations. Intune, typically packaged with other Microsoft solutions, presents competitive pricing within the Office 365 ecosystem. Both solutions are effective at saving time and resources, with Chef focusing on operational workload reduction and Intune providing cost-effective integration within the Microsoft suite.
The return has been far more hours saved than spent.
We have seen significant improvement in the time and the way we make changes to the infrastructure.
I have seen a return on investment with Chef because we definitely need fewer employees to manage infrastructure.
Everything we've gained from it makes my job easier day after day, and I see value in it as an engineer.
Microsoft Intune not only saves costs by reducing the number of personnel needed but also offers a comprehensive solution for managing laptops, applications, security, individual access, and enrollment.
Importantly, when someone leaves the company, it helps protect document access on their devices.
We usually work with the Chef teams and community support, who are always willing to assist.
When a support ticket is submitted, it directly reaches someone with Intune support expertise.
When I contacted Microsoft, they had the same expertise, if not more, which is phenomenal because I felt heard and my problem was solved.
Sometimes, the support provided is excellent, and the representative is knowledgeable, while other times, the service needs improvement.
We leverage both to achieve the best option possible for scaling.
Chef's scalability is evident as the public sector organization I work at serves a population of 5 million, and we have had no problems with scaling.
The scalability of Microsoft Intune is ten out of ten.
Ideally, we want to automatically segregate devices based on user properties like primary use, but currently, dynamic groups seem limited to device properties.
It supports organizations with 200 endpoints and those with more than 15,000 endpoints.
It is a good tool to work with, offering a strong developer experience and community support.
Chef is stable.
In my experience, Chef is quite stable most of the time.
We have not experienced downtime, bugs, or glitches.
It appears Microsoft Intune undergoes changes without informing customers.
Microsoft Intune has been very stable.
On support, I think there should be more focus on how we can achieve AI automations in answering questions for beginners and addressing deep concerns without general manual management.
To improve Chef, making an interface with another language such as Python or Java that is well understood, as capable as Ruby, and even more widely adopted would demystify it a bit.
The learning curve is steep due to Chef's Ruby-based DSL and the complex components of cookbooks and recipes, which can be challenging for new users, especially those without programming backgrounds.
Features like unlocking devices sometimes fail, and the support offered for other operating systems is insufficient.
There are communication issues, so you might start working with a feature without knowing if it will be deprecated six months from now.
Many third-party companies offer single-pane-of-glass reporting that shows you what your update environment looks like, how your patch is doing, application status, etc., but Intune's reporting is not intuitive.
Licensing looks reasonable compared to the manual work of managing whole data centers with even 10,000 servers.
My experience with pricing, setup cost, and licensing is that we sidestepped it by using Cinc because none of the functionality that is exclusive to the paid version was actually in use in the organization.
Introductory professional services, like a fast-track service, were included with our E5 membership, and there have been no additional costs.
The Intune suite and add-ons, such as batch management and remote help, are costly.
It costs approximately forty euros per user per month.
Security is a key aspect that Chef can automate, monitor new features that are available, and even do patches without you getting involved.
When you have infrastructure as code and you already have everything apart from the environment-specific config, which you can specify in variables, then it is not only more repeatable and reliable, it is faster.
Using Chef for automating infrastructure and applications in my organization has helped us reduce manual tasks by more than forty percent, thereby saving significant revenue for the client.
Intune excels in configuration and compliance management for Windows 10, ensuring devices receive timely updates and adhere to organizational standards.
Dynamic groups allow us to set conditions for automatic membership, eliminating the need for user intervention or manual review and ensuring a seamless workflow.
Windows Autopatch is the most valuable because it removes the burden of patch management.
| Product | Market Share (%) |
|---|---|
| Microsoft Intune | 6.9% |
| Chef | 3.4% |
| Other | 89.7% |


| Company Size | Count |
|---|---|
| Small Business | 3 |
| Midsize Enterprise | 7 |
| Large Enterprise | 19 |
| Company Size | Count |
|---|---|
| Small Business | 122 |
| Midsize Enterprise | 48 |
| Large Enterprise | 160 |
Chef, is the leader in DevOps, driving collaboration through code to automate infrastructure, security, compliance and applications. Chef provides a single path to production making it faster and safer to add value to applications and meet the demands of the customer. Deployed broadly in production by the Global 5000 and used by more than half of the Fortune 500, Chef develops 100 percent of its software as open source under the Apache 2.0 license with no restrictions on its use. Chef Enterprise Automation Stack™, a commercial distribution, is developed solely from that open source code and unifies security, compliance, infrastructure and application automation with observability. Chef provides an unequaled developer experience for the Coded Enterprise by enabling users to express infrastructure, security policies and the application lifecycle as code, modernizing development, packaging and delivery of any application to any platform. For more information, visit http://chef.io and follow @chef.
Microsoft Intune is a cloud-based service designed for device management, security, and compliance. It supports automation and facilitates endpoint management for Windows, iOS, and Android devices, ensuring data protection and efficient policy enforcement.
Microsoft Intune offers seamless integration with tools like Windows Autopilot to automate device setup and deployment. Integrated with Azure Active Directory, it enhances policy management while providing robust reporting and analytics tools for compliance tracking. Despite its intuitive interface aimed at simplifying navigation and device security management, there are challenges such as compatibility issues with Linux and Mac, limited policy support for Android, and demands for better third-party integration. It's widely used for both corporate-owned devices and BYOD scenarios in dynamic IT environments.
What are the key features of Microsoft Intune?In industries such as finance and healthcare, Microsoft Intune is implemented to ensure data protection and compliance with regulatory standards. Manufacturing sectors utilize Intune for managing a distributed workforce across global locations, while educational institutions employ it to secure and manage devices in learning environments supporting both students and faculty.
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.