3 ms·
It is nicely integrated wit (not in all but good enough amount of) Microsoft's ecosystem. If you're a Microsoft shop (we've got plenty of .NET, Azure, Azure Dev
by giancarlostoro 3y ago
It is nicely integrated wit (not in all but good enough amount of) Microsoft's ecosystem. If you're a Microsoft shop (we've got plenty of .NET, Azure, Azure DevOps, M365, etc) then its also a no-brainer. It could use with some polish, but my biggest peeve is where chats are housed. How can I have a "Team" space and no dedicated chat for it? Makes zero sense to me. At least give me ONE "General Chat" at a minimum.
It smoothly integrates back with Outlook, the experience is slightly different, but we have all our meetings over Teams, and the call quality is always great. If you ever have network issues, it suggests calling into the meeting on a land line, which is a small but really nice thing, even sometimes when watching a screenshare it offers listening from a land line whilst watching from your computer in order to cut down on data.
Teams has an insane amount of potential for complete greatness, but given how Windows itself does as well and it gets overshadowed by marketing decisions that anger power users, I'm not holding my breath on Teams achieving what it could. The infrastructures all there, and it is insanely extensible.