


Chef and AWS CloudFormation compete in the domain of configuration and infrastructure management. Chef seems to possess an upper hand in versatility and multi-cloud integration, while AWS CloudFormation is preferable for AWS-specific tasks due to its ease of use and cost-effectiveness.
Features: Chef stands out in configuration management with support for large-scale environments, flexible integration options, and ease of recipe writing. It allows headless operations with direct database interaction and integrates well with various cloud platforms. AWS CloudFormation excels with infrastructure as code capabilities using YAML and JSON templates, providing automation and predefined templates for fast deployment. It is particularly efficient within AWS ecosystems.
Room for Improvement: Chef could enhance usability by simplifying complex functionalities and improving security features. Better documentation and support for containers would help. AWS CloudFormation might improve by enabling cross-account references and providing more intuitive interfaces. Its AWS-limited use is a significant drawback for multi-cloud environments.
Ease of Deployment and Customer Service: Chef offers hybrid deployment options, but vendor support can be inconsistent. Its flexibility contrasts with AWS CloudFormation's streamlined AWS-focused experience. AWS CloudFormation benefits from Amazon's robust support network, resulting in high user satisfaction in service access and problem resolution.
Pricing and ROI: Chef's costs are based on node usage, which can become complex with scaling, although its automation reduces manual labor. AWS CloudFormation incurs no inherent costs and charges only for deployed resources, simplifying cost management for AWS users. Both solutions achieve strong returns on investment by enhancing delivery efficiency, with AWS CloudFormation offering a more straightforward financial model.
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.
With Microsoft Intune, tasks such as device provisioning, policy deployment, application delivery, and compliance enforcement require less manual effort than in more traditional management models.
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.
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.
While this might be acceptable for some, it can be lengthy depending on the urgency of the issue.
Free support for AWS CloudFormation is not provided, and while some support is understandable due to its complexity, assistance for service-related issues should be accessible without a cost.
We usually work with the Chef teams and community support, who are always willing to assist.
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.
Splitting CloudFormation into multiple formations results in changes to resources like API gateway URLs and Cognito pools, which causes issues, especially when trying to maintain consistency across resources.
Adjusting capacity and functionality is a fundamental use.
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.
We have not experienced downtime, bugs, or glitches.
It appears Microsoft Intune undergoes changes without informing customers.
In my experience, Microsoft Intune is a stable platform as it is a cloud-based service, and updates are regularly delivered by Microsoft.
It has been reliable and efficient in all my deployments.
Data loss can occur when splitting or scaling applications due to changes in resources.
It's a service that has been around for years, and it handles large complex deployments and updates with very good consistency.
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.
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.
It presents challenges for users unfamiliar with coding, posing as a barrier to fully utilizing CloudFormation.
Creating microservices and connecting multiple APIs into a single API gateway can be challenging; documentation should address specific needs.
Managing the correct order of resource creation and some updates can be tricky, especially with interdependent resources.
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.
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.
AWS CloudFormation is free.
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.
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.
I can see the entire infrastructure and its connections through code.
Managing, maintaining, and deploying become easier as it allows the creation of the same resources on multiple accounts, making it efficient for infrastructure management.
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.
| Product | Mindshare (%) |
|---|---|
| Microsoft Intune | 6.9% |
| AWS CloudFormation | 3.4% |
| Chef | 3.4% |
| Other | 86.3% |


| Company Size | Count |
|---|---|
| Small Business | 124 |
| Midsize Enterprise | 51 |
| Large Enterprise | 166 |
| Company Size | Count |
|---|---|
| Small Business | 15 |
| Midsize Enterprise | 8 |
| Large Enterprise | 17 |
| Company Size | Count |
|---|---|
| Small Business | 3 |
| Midsize Enterprise | 7 |
| Large Enterprise | 19 |
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.
AWS CloudFormation provides a common language for you to model and provision AWS and third party application resources in your cloud environment. AWS CloudFormation allows you to use programming languages or a simple text file to model and provision, in an automated and secure manner, all the resources needed for your applications across all regions and accounts. This gives you a single source of truth for your AWS and third party resources.
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.
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.