Zoom isn't even remotely comparable to Teams for remote collaboration. Zoom is better for some forms of video chatting, that's about it. Teams absolutely kills it as a complete package.
Teams is only one interface. You don't have to use the Teams interface for most tasks. You can sync files locally or work on them through a web browser. I would only use the Teams file browser/editor for a basic preview.
Not only that, but they will obey system-level Do Not Disturb settings, which they currently do not.
It's bizarrely located within the user profile section of the app, not under the Help menu, or the Microsoft Teams menu, or even in the Preferences as you would expect.There is a check for updates option within the client.
Does it work? No clue!
I got a funny feeling that a LOT of people will be disabling this feature.
This sounds like an IT/infrastructure/training problem. Teams has been near flawless for us in over a year of a sudden pivot to remote work. Best to figure it out because it's the core of Microsoft's platform going forward.
Still does not change the fact that grouping everything into a single interface is a stupid idea.
I could not agree more. I use the web version of Outlook/Office 365 at work because the Mac version is just so bad. The search function in the Mac version is just broken and has been for a while now. Encryption is broken as well, but works in the Web version.
Best to wait and see. If Discord was smart they would have taken that 12 billion Microsoft was offering. What would Microsoft do then with...Skype, Teams and Discord???? Ruin one or all of them for sure.
Yeah, but that doesn't excuse the bozonity of the UX and the resource bloat that Teams is... I worked with the lead designer for MS Unified communications and he even agrees that Teams is a UX disaster.
I've been working with Microsoft Sharepoint and their various under-pinnings for nearly two decades. Honestly Teams is the first time that they've actually put everything together into a unified way that makes sense. Video/phone/chat collaboration inside/outside of the organization, file sharing that actually makes sense, remote support through simplified screen sharing where the end user doesn't have to do *anything* to make it work, etc. Again, Teams is simply a different front end for a bunch of existing Microsoft services. It's often only one way - but not necessarily the best way - of interacting with the content. Again - this comes down to training as most users can't see how it all works together at a high level. (In our organization this was certainly a problem at first - many people - even high-level people in IT did not understand how it was designed to work and tried to write it off. It took a great deal of training to get them to see what it is designed to do - and it has since become an essential part of our daily workflow).
Chat and video are only a small portion of what Teams is about. File collaboration is a HUGE part of it as much of Teams is simply a different front end for Sharepoint. That is not in any way trying to bend it to a weird use case - it's an absolutely core feature.
These users are not using the file/Sharepoint section of teams. They are dropping files into a group chat and working out that. Which is the OneDrive of whatever user dropped it first.
If too many users have the rights to create Teams, that's an infrastructure/training problem. The Teams hierarchy needs to have some designed structure behind it just as if you were architecting your Intranet (because, in fact, you are). Small groups sharing files through chats and OneDrive is exactly how it's supposed to work (Personal OneDrive for quick sharing among groups of ~2-5, a full Team/Sharepoint for larger groups/longer-term projects).
Not to mention.
Sadly, as the end user, it is nothing more than a poorly designed UI with poor integration.
