@TAHIN said in Microsoft Teams ready for Production ?:
Teams and Slack both set out to solve an incredibly big problem with email: conversation-based collaboration. I really want to love it because if you run analysis on the type of email that flows between users of an organization, 70% of it is 'read once and delete' or one-liners. It's like supercharged IM. It took a while to wrap my head around the whole idea, but now I can see the overall potential, and it's staggering. But the OP comment regarding external user limitations is why we're not pursuing it. Having project collaboration for our internal users on Teams and having to import emails from external users would add too much overhead and confusion, and be a training nightmare.
Other reasons we're not using it:
A lot of documentation doesn't exist yet. Such as if we roll this out, we'll have archiving / legal hold requirements.
Doesn't have the kind of 3rd party product integrations that Outlook has, which we rely on.
We're actually fully licensed for it, wouldn't cost anything, but the use case isn't quite there until it can include everyone. We'll probably re-visit it in 12-18 months.
Same here, we are licensed for it and turn it off. Just doesn't make sense for us.