Microsoft Teams Reviews

• Collaboration
• Meetings
• Voice, video calls, and chats

It has allowed for collaboration during the COVID-19 situation (work from home).

• Calling
• Setting up teams
• Meetings
• File transfer

Whiteboard should be standard rather than an app.

Six months.

We use it for all communication between product development, product management, technical support, field teams, and other stakeholders. It is our primary vehicle for all communications. We have used it extensively to share content, such as spreadsheets, docs, PowerPoints, and other product related materials, for R&D and internal teams (e.g., the technical and field teams) as well as customer-facing documentation. With the recent COVID-19 forcing all our team members to work remotely, this solution has been an invaluable resource where we can easily set up virtual meetings (with or without video conferencing). 

We utilize the chat (with and without video calling) quite a bit as well as the ability to create content and store it. It is easy to share and collaborate, including built-in, edit-in-place, autosave features, without having to download, edit, save, or upload. We take advantage of the Wiki pages to schedule meetings through the calendar, which all but eliminates the need to use Outlook calendar. Teams is fully integrated with our teams, culture, and behaviors. It works as we work and is fairly flexible when configuring things that are team/program specific. 

If I could completely eliminate Outlook and only use Teams, that would help me immensely. Productivity would increase drastically and many of our team members would be more efficient in our day-to-day, as we would be living primarily in a single tool. I'm not a developer, but if Teams could be integrated with VS or Eclipse to easily share information in a chat panel, such as a task you are working on, roadblocks you may have run into, or if you need approval for something. 

This is not critical. It would be a nice feature to be able to have your own background, use a collage (if desired) when doing video calls, or use an animated emoji in place of your video during live chats (as a way to add more personal flavor to your personality).  

More than one year.

It is very stable when compared to Fuze and Skype for Business.

So far, it scales well.

Not applicable at this stage.

Yes, we have previously use Fuze as well as Rocket.Chat and Skype for Business. Fuze was unreliable. Skype for Business and Rocket.Chat lacked too many features.

As a large organization, we have used our fair share of tools, such as Skype for Business (S4B), Rocket.Chat, and most recently Fuze. Rocket.Chat is limited to chat only. Although you can share/attach docs, screenshots, and such, there isn't an easy way to organize the collection of data. If your team likes the ability to use a Wiki tool, there is nothing inherently built into Rocket.Chat for this. S4B is limited to video, chatting, and screen shares, lIke Rocket.Chat, for what it does, though it does it fairly well. However, as a tool for collaboration and communication with a team (large and small), S4B is too limited. Fuze, by far, is the worst tool. It was far too unreliable with calls (with or without video). Teams is a blend of Rocket.Chat, S4B, and a "working" version of Fuze.

Straightforward.

Vendor team.

Someone else handles it. I would estimate it has saved an average of at least one hour per day (for myself) as Fuze crashed too often, then I ended up reverting back to Skype for Business or GoToMeeting. 

Only Teams.

Mostly, how to use it and best practices (real world compared to what we are using today).

We primarily use the solution for projects in our company.

The conversation capabilities and document management are the solution's most valuable features.

The solution could use better calling functionality.

The solution should offer a way for people to virtually raise their hands in a meeting so that everyone can speak. There's a user voice for this already, but it would help if there was some sort of visual cue as well.

I've been using the solution for two years.

The solution is stable. We haven't had any serious technical problems.

The solution is quite scalable; you can easily add other programs to it.

I've never contacted technical support; I'm not even sure if it exists.

I have some experience on SharePoint, and all the products of the Office 365 lineup. Microsoft Teams combines most of the Office 365 products in one very convenient product. And you can combine every Office 365 app in Teams.

At the time, the initial setup was not really easy, but now it's pretty good. Deployment takes a while. For us, it's ongoing. It's a HI project that's continuous. You don't need anyone for maintenance because it's a cloud product. In terms of the adoption, all of the users assisted with deployment, and we have about 10 users.

We handled the implementation by ourselves with the team user adoption.

The solution is only available as a cloud deployment model; there's no on-premises version.

I use Teams every day for my daily workflow. My company is also rolling out some training on Teams. It's heavily used in our organization.

I'd advise others considering implementation to contact experts. They'll be able to show what you can do with Teams and you'll be able to develop new workflows. It offers a great way to collaborate together.

I'd rate the solution eight out of ten.

Our company is small, with only six people. I work out of my home, and one of my colleagues does as well. The two of us used this solution for instant messaging and bits and pieces like that. We didn't actually use the full service because we're not a big company. We don't have an instant messaging infrastructure, so we use Teams instead. My other colleagues did not use it because they are mobile and do not sit at a desk during the day.

We stopped using it because my coworker is on maternity leave and will be off for another year. However, when she returns, we will probably go back to using Teams.

Microsoft Teams gave our small group the ability to chat via instant messenger.

The most valuable feature for us was instant messaging. I did like the fact that you could start various teams so that if you wanted to instant message certain individuals, you could have the group chats going on in the background. But again, we were such a small company, we didn't actually use it. I think if it was a large company, fantastic because you've got large multiple groups feeding in. For a small company, no.

I liked the idea of being able to share, but we used Dropbox, so we found that we didn't need to share documents. It would have provided another layer, but our team is not large enough to warrant a group of individuals, multiple locations, all feeding into one document at different times. We didn't actually have a need for that.

I didn't know that Teams is part of Office 365, so I think that it should be better advertised with its features and capabilities. It would be helpful for it to be more visible and what the benefits of it are. Documentation on its capabilities and guidelines on its use would also be helpful.

This solution would be improved with more functionality built into the interface. If you compare Teams to Lync, Lync is just a little box in the corner and it pops up and alerts you if someone is trying to contact you. With teams, you have to physically go in and look to see what is going on. The interface could be improved so that we don't have to manually check for things such as who is online.

I used Microsoft Teams for about four months, but I no longer use it.

This is a stable solution.

There were only two of us in the company who were using this solution. As such, we never need to scale it.

In this company, we did not use another solution prior to Teams. This was a quick and easy solution for instant messaging that was part of Office 365.

In my previous company, which was larger, there was an instant messenger called Lync that we used constantly.

Once I knew to look for it, I searched for it and started it. The deployment took a couple of seconds.

I set it up on my own.

As an instant messenger, Teams is not as good as Lync. However, it was built into Office 365 so we used it. We were only using it as an instant messenger, essentially trying to fill a hole rather than use it to its full capacity, 

My advice for anybody researching this solution is to look on YouTube to get an idea of what it can do, and use it to its fullest capacity. That is what I did because it wasn't really clear what we could do with the product or how I could use it.

I would rate this solution a five out of ten.

What I like most about Microsoft Teams, is that we can pin applications on the top of the group. So I don't need to go to the browser to search for something or I don't need to go to an application on my desktop if I use cloud applications. 

We have had some problems uploading documents because of the GDPR status. So we must disable it to upload documents in Teams easily from users. If Microsoft Teams could do that, it would be great. There's a third part solution for this, but it can be too expensive for customers. So I would like to see an admin center added to this solution, so that I can block to upload the document for some users or for some groups. 

I have been using Microsoft Teams for two years now.

The solution is very scalable - we have more than 500 users at this stage.

I don't use support from Microsoft Teams, but I bought Microsoft Solution from my other Microsoft Support Team and I like the support Microsoft gives. It is very good.

The initial setup was really straightforward and easy.

I would like to see Outlook options added to this solution. But I recently saw some of the updates, and it seems that there is a way to get Outlook emails on Microsoft Teams. But I haven't experienced it yet. But more Outlook options would be nice. On a scale from one to ten, I will rate this solution an eight.

We are training an education company, so we primarily use the solution for this. We use it as a business communication tool among team members. 

In terms of administrating through Office 365, I like the administration panel. The configuration is easy and powerful. Its integration within Microsoft is very good.

There is a new Skype feature in Teams that is excellent.

The mobile application needs improvement. There are a lot of features on the web and desktop versions that aren't implemented yet on mobile.

It would be nice if more education features were added in future releases.

I've been using the solution for about a year or so.

The solution is very stable; we haven't had any issues.

The solution is very easy to scale.

We have never contacted technical support.

We previously used Microsoft's Yammer, but we've since switched to Teams.

The initial setup was straightforward. We simply enabled it and downloaded the software, then sent the link to everyone, so deployment was very quick. Since we have 6,000 people in the company, we deploy it in batches to teams. The deployment isn't finished quite yet.

We are handling the implementation ourselves.

We use the solution for free since we are an education company. If we need to deploy the solution to our conference rooms we would need to pay, but we don't need to do that right now.

We use the mobile, desktop and web versions of the solution and we use the cloud deployment model. We're partners with Microsoft.

In terms of advice, I'd recommend others carefully plan the project before implementing the solution. Figure out how you can test it and make other people comfortable with using the product before they receive it. Microsoft actually provides very good guides that can help.

I'd rate the solution ten out of ten.

The features in this solution are better than Skype for Business.

The group chat is very good.

In the next release, I would like to have the interface modernized and brought more up to date.

This is a stable solution.

Scalability and adding licenses is a straightforward process. We have had no issues at all.

We have a hundred or more people using this solution. They are all end-users.

We have an enterprise agreement with premium support for this solution. We haven't had an issue but we're covered in case we do. I would not be able to judge the quality of support for a normal user.

We were using Skype for Business, but Microsoft has stopped supporting it. In 2020, they will only provide new features for Teams, and not Skype for Business, which is why we switched.

The initial setup of this solution is straightforward.

The helpdesk configured this solution for the users.

We are satisfied with the price of this solution. We have an enterprise agreement.

This is a solution that I recommend. Neither myself nor the end-users have had issues since we began using this solution.

I would rate this solution a nine out of ten.

We use Teams for onboarding. It helps with worker coordination.

You can add Teams to a conversation. You can create reports, project plans, or many other things based on Microsoft solutions. It has improved communication between teams and within each team.

There are many functionalities we can work with.

I think they can improve all those segments for channel bulking. Also, some functionalities which migrated from Skype for Business to Teams, is not supported by Teams. We had used them in Skype for Business.

I think it would be better if we had some improved planning on Teams.

I think it's quite stable.

The product is scalable, but the organizations that I helped are around 1,000 users. Some organizations that are supported by our company have 1,000 or more people.

One administrator helped us with our experience of Office 365 and administered this solution. I think three would be enough to manage the solution.

Microsoft's support is okay.

There are no products that I can say have all of Teams' possibilities. There are separate products to maintain for all the functions I need, which I can now do in one product.

The initial set up is really easy. You can download a file setup from their portal as long as you are authorized to use it. One user took around five minutes to set up.

It is the standard license which is part of many Office packets.

Just set up and enjoy. It is no problem to use this product.

I would rate this product as eight out of ten.

We primarily use the solution for communication within our function teams. We use it for project organization, etc.

The chat functionality is the solution's most valuable feature.

We occasionally have issues with synchronization between different dates. This aspect of stability needs improvement.

The solution could be better integrated with SharePoint and have better workflows especially for writing drafts for review and release. 

The solution is largely stable, but we do face issues around synchronization between different devices.

The scalability is good. It's not a problem to put more users onto the solution. We do plan to increase usage, but we'll take some time before doing so.

We previously used Skype occasionally for team communication.

The initial setup was easy. The company-wide deployment took several months.

We had an internal team handle the implementation.

I'd recommend the solution.

I'd rate the solution 7.5 out of ten.

We are primarily using the product for collaboration and planning. We create tasks in the Planner, we can track the status of all the different tasks we have created and we can share the progress we achieve on these tasks between coworkers. It helps us measure progress and to collaborate.

The most valuable feature for us is the Teams Planner module. This is a module where we enter projects and tasks that we want to track. We also use the Chats module and find that useful as well to work in conjunction with this tool.

One of the places where this product can improve is in file sharing. Using the Planner, it should be easier to link to external files. As the product is set up now, you are obliged to use links to files that will be stored in SharePoint. You cannot integrate files in a node. One of the reasons why we prefer using Trello at this point is because you can add links to the files on each card (project) as you want. It is more open and less limited.

The possibility to attach any kind of content to any card created in Planner is the reason why we didn't stop using Trello completely. With Teams, the constraint regarding the files means we have to separately log on SharePoint and to upload files on to OneDrive to share them. The added complexity means we are losing time over something that should be easier. If this feature could be enhanced so file attachment is easy, I think I would prefer to use Teams instead of Trello.

One functionality that could add value to the product would be better logging of histories. For example, when you've got a conference call and you're using Teams, it would be useful to have a record of the participants in the call. If you have a conference call where there are five participants, the product should be able to record this information as a history of the project without having to ask separately for introductions. Currently, the product is not able to track this information and it doesn't seem that Teams offers the possibility to track the history of the calls that have been completed. 

Another feature that would be useful is the ability to create a VCF (Virtual Contact File) directly from an appointment, through the calendar, or through a phone call. It could be great if you just could right-click on the name of the contact and create a VCF file. Later, you will be able to import the contact into Outlook, for example. It could be a very useful time-saver. 

I have never noticed any stability issues with Teams, so I think it's good. I don't think there is any need for improvement in that way except to maintain the level of stability as the product develops.

To be honest, we have never explored the possibilities for further expanding the capabilities of the program. I'm quite sure we can explore the addition of features and functionality that do a lot of interesting things. But because it is a bit clumsy to use the file attachments, which is really a basic task I try to avoid using it and I favor the use of Trello instead of Teams. Because we do not currently use it more, we don't do much exploration into scaling it. I don't think there is any real problem with scaling the number of users. But again, we have not been pushing the limitations or the product to scale its use.

We use Teams in the same way that we are using Trello but we lean toward using Trello because of the ability to attach files. So Trello is what we were using before and it is really still what we are using now. We have not migrated to Teams fully although we are using it for some projects and exploring the possibilities.

The product is still developing and may integrate better with Office 365 applications, but there is still a little bit missing in the functionality besides just the file attachments. I think it is possible to improve the interface. A lot of things I would expect to be able to do are currently impossible. I would like to be able to interact with objects better. For example, if you go in the call component and you look at your contacts, you don't have the capability to do much to interact with the contact object. You can launch a conversation and you can make a phone call but you cannot manage the contact object and I wish able to.

For example, you cannot right-click in order to copy the contact to collect the basic information. To be able to create a VCF file would be perfect. But even without going so far, there is a lot of little interaction that would be interesting to be able to do that we cannot. Currently, the product limitations are keeping us from migrating to expanding its use.

On a scale from one to ten where one is the worst and ten is the best, I would rate Teams as a seven as of now. But the quality of the product is rising from month-to-month. There is a lot of improvement. Microsoft is still developing it in a smart way. But at the moment it is not a complete solution.