Microsoft Teams combines video conferencing software with team collaboration tools. The communications platform allows MS Office users to conduct conference calls and share files via SharePoint, and join or initiate a group chat.
$4.80
per month per user
Progress Chef
Score 6.5 out of 10
N/A
Chef IT infrastructure automation suites were developed by Chef Software in Seattle and acquired by Progress Software in September 2020. The Chef Enterprise Automation Stack is an integrated suite of automation technologies presented as a solution for delivering change quickly, repeatedly, and securely over every application's lifecycle. The Chef Effortless Infrastructure Suit is an integrated suite of automation technologies to codify infrastructure, security, and compliance, as well as…
N/A
Pricing
Microsoft Teams
Progress Chef
Editions & Modules
Microsoft Teams Essentials
$4.80
per month per user
Microsoft Teams Enterprise
$5.25
per month (paid yearly) per user
Microsoft Teams Enterprise
$5.25
per month per user
Microsoft 365 Business Basic
$7.20
per month per user
Microsoft 365 Business Standard
$15
per month per user
No answers on this topic
Offerings
Pricing Offerings
Microsoft Teams
Progress Chef
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Discounts are available for non profit organizations.
—
More Pricing Information
Community Pulse
Microsoft Teams
Progress Chef
Features
Microsoft Teams
Progress Chef
Project Management
Comparison of Project Management features of Product A and Product B
Microsoft Teams
8.0
236 Ratings
3% above category average
Progress Chef
-
Ratings
Task Management
7.9175 Ratings
00 Ratings
Gantt Charts
7.792 Ratings
00 Ratings
Scheduling
8.0203 Ratings
00 Ratings
Workflow Automation
8.2122 Ratings
00 Ratings
Mobile Access
8.1224 Ratings
00 Ratings
Search
7.4207 Ratings
00 Ratings
Visual planning tools
8.4138 Ratings
00 Ratings
Communication
Comparison of Communication features of Product A and Product B
Microsoft Teams
8.0
245 Ratings
0% below category average
Progress Chef
-
Ratings
Chat
9.0244 Ratings
00 Ratings
Notifications
8.3243 Ratings
00 Ratings
Discussions
8.6230 Ratings
00 Ratings
Surveys
8.1141 Ratings
00 Ratings
Internal knowledgebase
8.5152 Ratings
00 Ratings
Integrates with GoToMeeting
6.547 Ratings
00 Ratings
Integrates with Gmail and Google Hangouts
5.743 Ratings
00 Ratings
Integrates with Outlook
9.1155 Ratings
00 Ratings
File Sharing & Management
Comparison of File Sharing & Management features of Product A and Product B
It's amazing as a daily driver for team communication, and document search/store. Also, if you're doing a lot of LONG meetings and have trouble remembering details, the AI summarization is amazing and convenient. It just works. I'm not saying I always do this, of course, but if I need to 'skim' instead of really digging into every detail from a meeting, the AI-generated summary is generally good enough that I can get away with it.
Chef is a fantastic tool for automating software deployments that aren't able to be containerized. It's more developer-oriented than its other competitors and thus allows you to do more with it. The Chef Infra Server software is rock-solid and has been extremely stable in our experience. I would definitely recommend its use if you're looking for an automation framework. And it also offers InSpec which is a very good tool for testing your infrastructure to ensure it deployed as intended.
The webinars feature has some missing functionally such as the ability for all users to use the Q&A feature (only those with a Microsoft Teams account can use it now), the ability to upload documents for attendees to easily access and download, and the ability for presenters and organizers to easily chat amongst themselves throughout the webinar.
The "Channels" organization hierarchy could be more clear. If you have several channels set up, it can get clunky and hard to find the specific channel you are looking for.
The MS Planner tool lacks functionality and organization. You cannot assign more than one person to a task and it's confusing when you try to share tasks with people - it would be nice if they were automatically added to someone's calendar.
Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.
Microsoft Teams is included with our Office 365 subscription and we have no intention of migrating off of Office 365 and Microsoft products. Since Microsoft Teams is included for free with our Office 365 subscription, and since we enjoy all the features, benefits, and functionality, there is no question that our team will continue to use the product
If you have the full Microsoft Office suite, it works really well because it's integrated well within its ecosystem, but if not, it can be annoying because it tries to open a shared file in the web versions of the file equivalents. The web version is also a bit slow, and the login is very difficult to handle if you have multiple Microsoft or Outlook accounts.
The suite of tools is very powerful. The ability to create custom modules allows for unlimited potential for managing all aspects of a system. However, there is pretty significant learning curve with the toolset. It currently takes approx 3-4 months for new engineers to feel comfortable with our implementation
It loads quick enough for basically all our systems. Because we have this for local dev environments, speed isn't really a big issue here. Yes, depending on the system, sometimes it does take a relatively long time, but it's not an issue for me. One thing that is annoying is that if I want to make a small change to a cookbook and re-run the Chef client, I can't just make the change in the cache and run it. I have to do the whole process of updating the server.
The overall support provided by Microsoft for Microsoft Teams has been quite good but there is still some room for improvements. Microsoft needs to proactively work on fixing the open bugs in order to provide a seamless experience to the users. But over the service and experience provided by the Microsoft team have been quite satisfactory.
Support for Chef is easily available for fee or through the open source community as most the issues you will face will have been addressed through the Chef developer community forums. The documentation for Chef is moderate to great and easily readable.
Microsoft Teams offers a much more integrated experience between their chat and video call function compared to Google Chat and Slack. Both other tools are much better for internal communications are they have simpler UI without other features. Whereas Microsoft Teams can be used for more critical conversations, particularly between external companies, and has been very useful in sales conversations which is what we chose it for when speaking to companies that work exclusively through Microsoft.
We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet seems like it has fallen off the pace of the competition and lacked the strong community offered by Chef. We chose Chef because of the strong support by the company and the dynamic and deep community support.
Honestly, this tool is worth every penny. Yes, it's not free and you pay for the quality of services and the license. But the ROI and the benefits are all there. Also, the renewal, negotiation, and contract terms are all very well explained by our Microsoft account manager, and she's a charm.
I used Skype for Business to take calls, hold conferences, and provide remote assistance to users. Microsoft Teams, on the other hand, is superior to Skype for Business in my opinion. My job entails a lot of screen sharing.
The entire professional services team was great to work with. The curriculum was tailored to our specific use cases. The group we worked with were very responsive, listened to our feedback, was very easy to schedule and accommodate. I cannot say enough good things about our professional services experience
Personally, I would say that by using Microsoft Teams, it upped my collaboration with my colleagues by around 50% or around more than half of what I usually did prior to using it.
I had 100% show rate and attendance on all of my meetings in the past 6 months.
If I may add, I also have been chattier & collaborative towards my colleagues in past 3 months particularly the month of December when we had huge traffic at work. I would estimate this behavior to have been increased by around 60% than what I usually incur during normal operating days.
Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.