Microsoft Teams Reviews

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.

I think we're use Microsoft Teams for almost everything when it comes to communications. When I call my colleagues, I no longer using the phone. Because I use Teams so much, I picked up the phone the other day and it was strange — It was like it was the first time I picked up the phone. I use Teams as a phone. Even on my smartphone, I call people using Teams.

We're using Teams to call people to set meetings, record meetings, share documents — all communication now goes through Teams. We create groups to share our documents and update them live. It is really very practical and collaborative.

It is improving our means of communication and I think in the future will encourage users to communicate better because it is fun to use and powerful.

The features that I like the most are the features we have now. I like every aspect of it. It is easy to use. It's on your phone, so it is mobile. You can respond without answering if you have a call or message. You can send emoticons so people know you have gotten their message. This type of response is very quick and doesn't leave the other party waiting. Those features are just like what you might do in WhatsApp or Messenger on Facebook. It is very familiar to anyone using those products.

One thing that we are looking to deploy — and we are testing it now — is to send and track kudos. We want to implement this new feature on a worldwide basis to thank team members for being good participants. 

We work directly with Microsoft to provide feedback on the product and what we would like to see as improvements. I discover a new feature every day, so they're really working to develop it very quickly. 

I would like also to have a feature where we create a worldwide group to act as a social media hub. The difference between that and groups is that it would be separate from all the other groups. I don't want it included in my Teams because I will use it in a different way. I can see the activity of other teams or individuals who are not on my teams. Because I'm using the product extensively and have many teams, I think it is an important addition to be able to organize groups in different ways — and I have put in that request with IS. 

I've heard some people complain and say, "Oh it's not working with me," but I never had any issue with Teams. I use it all the time and it is stable. It opens immediately when I open my computer, it's on my phone and it sends me notifications. 

I have calls with people on it. Sometimes I even record video calls. The only time I have had any issues is when the network is not working well — maybe in high load times — but this happens with every means of communication like WhatsApp or other solutions that depend on the network. It isn't a problem with the package it is a problem with the network.

Our company has about 14,000 employees, but we are not all using the intranet. We are an industrial company and we have people working in manufacturing and they don't have access to computers all the time. 

As far as scalability, we would like to have the ability to use the product off-site. That is, we want to be able to have remote people use Teams with us internally. This is the only thing I've heard that's posing a problem with scaling. 

I have not directly had any experience with the Microsoft technical support team for Teams because we have an IS (Internet Services) group. If we open a ticket, the IS department is the group who will contact support.

Before we tried using Teams, we were using Skype. Now we are only using Teams because it is a more complete and business-oriented tool. 

I was not directly involved in the deployment. 

Our implementation was done by our own IS team.

My advice to people who are considering this solution is that you have to be patient at the beginning. People might think it is too complicated or that it looks too complicated at the beginning. As a first time user, I remember feeling like I didn't understand anything. You have to be patient and play around with it until you become familiar with the different features. For example, there are channels within a group. If you are added to several groups and you start getting alerts, you may not know which channel it is or which group. It is a lot for a first time user to digest. It is not as straightforward as WhatsApp when it comes to groups.

What we have seen is that when we communicate our requests to Microsoft, we are getting back responses with the features we have asked for. There are many features that we request and we discover they are available in just a few days. Either many companies are making the same requests or Microsoft is answering our request, but the product is evolving quickly. 

On a scale from one to ten, when one is the worst and ten is the best, I would rate Microsoft Teams as an eight. While I like the product a lot and I use it all the time, there is room for improvement.

We mainly use this solution for project collaboration. It could be, for example, when we are developing a new product or taking a new product to market. We use it for designing, publishing and marketing assets, so basically team collaboration where we are working on a project. It helps with communication in the team and it allows us to share different documents or content with each other.

We used Skype for business in the past and we had a reasonable audio and visual experience when communicating with teams, if you have a scheduled meeting, for example. But now, with Microsoft Teams, we are able to communicate in real-time and share documents in real-time. And that is a really big improvement for us. The solution has a lot of capabilities in one application. Whereas in the past we had to use multiple applications. That, I would say, would be the biggest benefit that we've experienced, in that we have only one application that we can use to collaborate and speak with each other. 

I think what the team likes most is the improvements when it comes to communication. We've been using Skype for business in the past but the audio and visual communication is really good with Microsoft Teams. I also really like the speed of the product and the way that the channels can be leveraged.

There is nothing that annoys me at the moment but perhaps the layout can be improved. In my experience working with Microsoft tools, they continuously work on usability. There are a few minor issues when scheduling meetings, and that is that some of the descriptions are really long. And there seems to be very little control over what a user could control in terms of the texts that appear. An invitation, for example, can look very complicated. So I would say that Microsoft Team invitations from the calendar within the solution could be improved.

The solution is stable, I've never experienced it being unavailable or behaving in a peculiar way. 

We are only 30 people using this program, but what I have not noticed any issues when more colleagues participate in Microsoft Teams. When usage increases, the program still offers a seamless, consistent experience. We may even add more users, so I believe the program is very scalable.

I haven't used the technical support yet, because I contact our administrator directly. But I know that he was working with Microsoft's technical team from time to time, as well as a third party that delivers hosting services.

We used Skype for Business before but Microsoft Teams came along with the Microsoft Office subscription that we had. We had subscriptions to Office. And then we moved from On Premise Exchange to Exchange Online. It was the natural choice to make. We do use other services from other providers, but I would say that Microsoft Teams is the most stable one. 

From an end-user perspective, the initial setup was really straightforward. We started to use Microsoft Teams when we deployed Microsoft Exchange Online earlier this year, and as part of that, we adopted the use of Teams and Yammer. I have been using Microsoft Teams in the past, but it wasn't really until we as an organization had deployed it and exchanged online that we were all able to enjoy the benefits. Testing the application before was very fragmented.

Deployment took a couple of days. When we started to go from using Microsoft Outlook for mail, we started to integrate Yammer and Teams. 

My advice to others would be that, if they're working with a similar product, they should have a change management program in place. They should also give themselves a few days at least to deliver some training for the users. I think the training is really important to enhance the user adoption experience. It doesn't have to be a lot, but at least give them an introduction and a guided tour through the program's features. 

The biggest lesson I've learned is actually using a single application that can deliver all of the services that are required. Since I've only been using the solution for six months, I haven't even used all the features yet. I think that Microsoft Teams may replace Microsoft Outlook in the future.

On a scale from one to 10, I will rate this solution a seven. I think there's always room for improvement, even if it's not obvious what those improvements can be. I guess I could be tempted to say eight but not higher than that. I am very satisfied with Microsoft Teams. 

I use Microsoft Teams for remote access. I can check the calendar and call my team. I can ask them to share the screen. 

The most valuable feature of Microsoft Teams is that I can attach files in any format. 

The main issue is that the link goes down when there are internet issues. 

I have been using the tool for four years. 

I would rate the product's stability a ten out of ten. 

I would rate Microsoft Teams' scalability a ten out of ten. My company has 10 users for it. 

The solution is priced high. 

I would rate Microsoft Teams a ten out of ten. 

For communication purposes, we use Microsoft Teams in our company.

The most valuable feature of the solution is that it can be included in most systems.

The application's user interface on Google has shortcomings that need to be improved.

I have been using Microsoft Teams for three years. I use the solution's latest version. My company has a partnership with Microsoft.

In terms of stability, there are some errors and issues at times. I rate the solution's stability a seven out of ten.

Scalability-wise, I rate the solution a ten out of ten.

In our company, almost 500 people use the solution.

The solution's support is responsive. I rate the support team a six out of ten.

Neutral

I rate the initial setup as a nine on a scale of one to ten, where one is low and ten is high.

The solution is deployed on the cloud.

I rate the pricing as a five on a scale of one to ten, where one is cheap, and ten is expensive.

Overall, I rate the solution an eight out of ten.

We use Microsoft Teams for meetings. Since the pandemic, most of my clients don't physically go to offices, and we do most of our meetings through Microsoft Teams.

Using the solution's screen-sharing feature, we can go through a document together and take control.

The solution’s stability could be improved.

I have been using Microsoft Teams for the past two years.

Microsoft Teams is a stable solution. I rate Microsoft Teams an eight out of ten for stability.

Microsoft Teams is a scalable solution. Around 5 users are using the solution in our organization. The solution is used a few times a week in our company.

I rate the solution ten out of ten for scalability.

The solution’s initial setup is easy.

The solution is deployed on the cloud in our organization. The solution’s deployment took a few minutes.

Overall, I rate Microsoft Teams an eight out of ten.

We use Microsoft Teams in our company to communicate with teammates and schedule meetings.

Compared to other solutions like Skype, Microsoft Teams is a good tool for communicating with teammates.

The most valuable features of Microsoft Teams are scheduling a meeting and integration with other Microsoft services like SharePoint and OneDrive.

The software could be optimized for Mac systems because sometimes it is slow and consumes a lot of memory.

I have been using Microsoft Teams for one year.

I rate Microsoft Teams an eight out of ten for stability.

I rate Microsoft Teams an eight out of ten for scalability.

The solution’s initial setup is easy.

I am using the latest version of Microsoft Teams. Microsoft Teams is deployed on-cloud in our organization.

Microsoft Teams is the best tool for team communication.

Overall, I rate Microsoft Teams an eight out of ten.