Microsoft Teams ready for Production ?



  • Hello all,

    We are with O365 Essentials, so we are eligible for using MS Teams for Free ! so we have been waiting for using it in Production since it was released in Preview mode.

    Based on the recent post from SW, which redirected to following link, the MS Teams is ready for Production.

    http://www.zdnet.com/article/microsoft-teams-goes-live-with-new-email-integration-enterprise-bots/

    Who else is going to use it ?

    I have few questions if you know to answer :

    1. I seen, any user can create Teams, add members, add channels without being Admin, it leaves me without good control or Can we control after it made ready for Production ?

    2. I have evaluated Yammer before MS Teams release preview, and Yammer seems to have good central management with "Network Admin" with reports and stats, whereas in MS Teams, I cannot see such...

    3. No idea about data retention of MS Teams (groups, messages, pics etc.), where does it goes ?

    4. Now we have email groups for some users, to which external users also send emails. And there's no external users access in MS Teams, so if we create MS Teams group, it will be duplicated and confusing group for them, right ?

    I will be posting more queries on same topic, as I receive responses on it :)


  • Service Provider

    We tested in and decided against using it.



  • This should give you most answers
    https://support.office.com/en-us/article/Frequently-asked-questions-about-Microsoft-Teams-–-Admin-Help-05cbe533-2181-4e95-a4b0-52cd7695fafc

    Especially:
    Can I restrict who in my organization can create teams in Microsoft Teams?
    Yes. The same creation settings defined by Office 365 Groups apply to Microsoft Teams. For more information, see Manage Office 365 Group Creation.

    And this https://www.successwithteams.com/



  • @scottalanmiller What made you decide against it? We are getting ready to migrate to teams from HipChat.



  • @RamblingBiped @scottalanmiller hates microso$t. =P


  • Service Provider

    @aaronstuder said in Microsoft Teams ready for Production ?:

    @RamblingBiped @scottalanmiller hates microso$t. =P

    I actually like them more than pretty much anyone that I knows that runs them. No one that runs any version older than Windows 10 voluntarily likes them as much as me. So I'm definitely in the top percentages of fans.


  • Service Provider

    @RamblingBiped said in Microsoft Teams ready for Production ?:

    @scottalanmiller What made you decide against it? We are getting ready to migrate to teams from HipChat.

    We just didn't find any value to it but it lacked the existing features of other MS tools that we already had. It added confusion but not value. Another MS tool to manage but we couldn't figure out why we'd use it.


  • Service Provider

    Remember that it is Skype that we chose instead of it. It lost to Microsoft.



  • I looked in to Teams a little bit. I basically watched the "trailer" for it, and gave it a quick eval. I thought it looked pretty decent, and I could definitely see it's usefulness for certain departments and projects they were involved in. But like SAM said, I didn't really see the value in it over what was already in use. That said, I could see it working out in the company for the users and projects. It's just that you'd need to take full advantage of most of its features, after training the users how to properly use it all, to get it's full value. And even then, will it increase production or add value to the business?


  • Service Provider

    @Tim_G said in Microsoft Teams ready for Production ?:

    I looked in to Teams a little bit. I basically watched the "trailer" for it, and gave it a quick eval. I thought it looked pretty decent, and I could definitely see it's usefulness for certain departments and projects they were involved in. But like SAM said, I didn't really see the value in it over what was already in use. That said, I could see it working out in the company for the users and projects. It's just that you'd need to take full advantage of most of its features, after training the users how to properly use it all, to get it's full value. And even then, will it increase production or add value to the business?

    Yeah, if MS had nothing else, it would be decent. But it's like the fifth tool from MS covering the same ground. I'm overwhelmed with MS Office 365 IM options already.



  • 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.



  • I have a customer that wants to link network drive locations in chat and be clickable like a shortcut or html link. So far I have found no way to do this. Anyone?
    Even trying file://///server1/folder1/ does not work. Then even if I get it clickable, if their browser default is not IE, it wont work.


  • Service Provider

    @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.


Log in to reply
 

Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.