Chef vs Microsoft Azure DevOps comparison

You must select at least 2 products to compare!
Chef Logo
Read 18 Chef reviews
615 views|413 comparisons
95% willing to recommend
Microsoft Logo
19,149 views|14,580 comparisons
95% willing to recommend
Comparison Buyer's Guide
Executive Summary

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.
To learn more, read our detailed Chef vs. Microsoft Azure DevOps Report (Updated: May 2024).
771,740 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them.""It is a well thought out product which integrates well with what developers and customers are looking for.""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 valuable feature is the language that it uses: Ruby.""Chef can be scaled as needed. The Chef server itself can scale but it depends on the available resources. You can upgrade specific resources to meet the demand. Similarly, with clients, you can add as many clients as you need. Again, this depends on the server resources. If the server has enough resources, it can handle the number of servers required to manage the infrastructure. Chef can be scaled to meet the needs of the infrastructure being managed.""The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools.""Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good.""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."

More Chef Pros →

"The installation is very straightforward.""It's a great product for the CI/CD process.""Some of the most valuable features are the ease of use and the ability to monitor a lot of things. It has a lot of applications and facilities that meet all the developers' requirements. For example, we can use application insights to get an idea of our application's performance. Since it's cloud-based, it's really good for collaboration and working as a team.""Great project management feature and Git-based repository.""It's graphical representation and tools are easy to use.""The reports have been most valuable. We have created some dashboards allowing us to be able to check our teams, their progress, and mission plans.""I like the entire tool because it is a one-stop-solution for DevOps.""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."

More Microsoft Azure DevOps Pros →

"Since we are heading to IoT, this product should consider anything related to this.""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.""There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based.""In the future, Chef could develop a docker container or docker images.""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.""There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work.""The solution could improve in managing role-based access. This would be helpful."

More Chef Cons →

"The tutorials for building pipelines are an area that is a bit technical for a beginner.""Project management could be improved.""We are currently in the process of moving all of our on-prem to the cloud platform. We are trying to make that move and host the majority of our DevOps services in the cloud because the cloud is where most of the things are going nowadays. However, the process of this transfer is not straightforward, and it could be a lot easier. Microsoft hasn't provided the maturity for migration tools. It could be a lot easier in that respect. I want to see them continue to advance the API capabilities. They could add some more robust functionality to the administrative layer within ADO services. There are a lot of configuration elements that you need to take care of at the organization level and the project configuration level from an administrative capacity. When you're dealing with process templates and things of that nature, you have to do them all manually. Being able to automate some of that using scripts or API functionality would be really nice.""When we don't have some permissions, we have to research how to get them.""There are certain features, and reporting that can only be used in PowerBI, but not directly in DevOps.""There could more integration with other platforms.""The interface is very bad.""I think that they have some menus there that are not very well placed."

More Microsoft Azure DevOps Cons →

Pricing and Cost Advice
  • "When we're rolling out a new server, we're not using the AWS Marketplace AMI, we're using our own AMI, but we are paying them a licensing fee."
  • "The price per node is a little weird. It doesn't scale along with your organization. If you're truly utilizing Chef to its fullest, then the number of nodes which are being utilized in any particular day might scale or change based on your Auto Scaling groups. How do you keep track of that or audit it? Then, how do you appropriately license it? It's difficult."
  • "The price is always a problem. It is high. There is room for improvement. I do like purchasing on the AWS Marketplace, but I would like the ability to negotiate and have some flexibility in the pricing on it."
  • "Purchasing the solution from AWS Marketplace was a good experience. AWS's pricing is pretty in line with the product's regular pricing. Though instance-wise, AWS is not the cheapest in the market."
  • "We are able to save in development time, deployment time, and it makes it easier to manage the environments."
  • "We are using the free, open source version of the software, which we are happy with at this time."
  • "I wasn't involved in the purchasing, but I am pretty sure that we are happy with the current pricing and licensing since it never comes up."
  • "Pricing for Chef is high."
  • More Chef Pricing and Cost Advice →

  • "It's a good tool, quite rich, it has a lot of features, and quite a lot of analytical capabilities which are built on top of it so that you can see how your projects are going and all that stuff. It's a good tool."
  • "There is a licensing fee of $6/user per month."
  • "The price is cheaper than Jira and some of the other competing tools."
  • "It is the least expensive product in this class."
  • "I find that the pricing is good, and it is competitive with the other vendors in the market."
  • "Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects."
  • "It is a subscription model and I only pay for what I use."
  • "The price of this solution is fair."
  • More Microsoft Azure DevOps Pricing and Cost Advice →

    Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
    771,740 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.
    Top Answer:Chef does not support the containerized things of Chef products. In the future, Chef could develop a docker container or docker images.
    Top Answer:Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalable… more »
    Top Answer:TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very… more »
    Top Answer:We can track everything from the requirements stage to the production stage.
    out of 32 in Release Automation
    Average Words per Review
    out of 32 in Release Automation
    Average Words per Review
    Also Known As
    Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
    Learn More

    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 and follow @chef.

    Microsoft Azure DevOps is a cloud service that enables developers to collaborate on code development projects and create and deploy applications quicker than ever before. The service helps unite developers, project managers, and software development experts through a collaborative experience while using the application. For the users' convenience, Azure DevOps offers the user cloud services through Azure DevOps Services or an on-premises service using Azure DevOps Server. In addition, it supports integration with additional services and adding extensions, including the ability for the user to create their own custom extensions. 

    Azure DevOps provides a variety of unified features that can be accessed through their web browser or IDE client, such as:

    • Azure Pipelines - Develop and deploy services to support ongoing application integration and delivery. Azure pipelines, which work with almost every project type and most languages, will automatically test code projects in order to make them available to others.

    • Azure Artifacts - Share packages and integrate package sharing between teams. Packages include NuGet, npm, and Maven, in addition to other private and public sources. Developers can now share and consume packages with other developers from different public registries.

    • Azure Repos - Offers source control of your code through Team Foundation Version Control (TFVC) or Git repositories. Developers can now keep track of any changes that are made in their code over the course of their project.

    • Azure Test Plans - Offers continuous and manual/exploratory app testing through several tools. Test Suites, or a collection of Test Cases, are grouped together in a container called a Test Plan.

    • Azure Boards - Provides a suite of Agile tools to track work, support planning, code defects, and general issues while using Kanban and Scrum software. Teams are in need of tools that are flexible and will help them grow. Azure Boards is a service that helps developers manage their software projects. 

    Benefits of Microsoft Azure DevOps

    Microsoft Azure DevOps offers many benefits, including:

    • A quick setup and easy deployment
    • An elastic scale
    • Exceptional security
    • No-maintenance operations
    • Effortless collaboration through domains
    • The ability to create and deploy products faster than traditional software

    Reviews from Real Users

    Microsoft Azure DevOps stands out among its competitors for a variety of reasons. Two major ones are its ability to forecast how long each task will take and the ability for users to follow the entire development process.

    PeerSpot viewers note the effectiveness of this solution. An executive chief operating officer for a cloud provider notes, “We can forecast tasks and the number of hours a task will take and can compare it with how long a task actually takes.” 

    Carlos H., a product and system director at SPCM, writes, “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.”

    Sample Customers
    Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
    Alaska Airlines, Iberia Airlines, Columbia, Skype
    Top Industries
    Computer Software Company30%
    Comms Service Provider20%
    Non Tech Company10%
    Legal Firm10%
    Financial Services Firm21%
    Computer Software Company13%
    Manufacturing Company7%
    Computer Software Company23%
    Financial Services Firm15%
    Energy/Utilities Company11%
    Manufacturing Company8%
    Computer Software Company13%
    Manufacturing Company11%
    Financial Services Firm11%
    Company Size
    Small Business5%
    Midsize Enterprise35%
    Large Enterprise60%
    Small Business19%
    Midsize Enterprise11%
    Large Enterprise69%
    Small Business31%
    Midsize Enterprise18%
    Large Enterprise51%
    Small Business18%
    Midsize Enterprise14%
    Large Enterprise68%
    Buyer's Guide
    Chef vs. Microsoft Azure DevOps
    May 2024
    Find out what your peers are saying about Chef vs. Microsoft Azure DevOps and other solutions. Updated: May 2024.
    771,740 professionals have used our research since 2012.

    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.