Microsoft Teams is here! It was released to General Availability (for Office 365 customers) on Tuesday. I’ve already seen several reviews of the chat platform. Links to some reviews are below.
Of course we have to weigh in; what kind of Skype for Business blog would I be if I didn’t? However, this is not just another review. I was able to trial Teams internally after the release, and thought I’d do something different.
By going through the information I’ve scoured from the Web, Twitter conversations, and my internal Teams trial, I have come up with several Teams-related questions. Questions which I shall answer!
Here are the questions. You can jump to any answer just by clicking the one you want. Let’s go!
Questions about the New Microsoft Teams
How is Teams organized?
Is there a mobile app?
What are the advantages (if any) over Slack?
Can we use Teams without an Office 365 account?
Will we get a free version of Teams? How about a consumer version?
What’s the cheapest option: Slack, HipChat, Workplace, or Teams?
How’s the bot?
What kind of integrations are available?
What’s the biggest drawback?
Teams keeps it simple, in terms of organization. Each Team has Users invited to it. Teams may set up Channels to contain their conversations. You have the option of Public or Private Channels. Within the conversations, users can share files, video calls, a Wiki, etc.
Hierarchically, it’s like this: TEAMS > CHANNELS > USER CONVERSATIONS
There’s also an Activity Feed accessible from the left-column bar at all times. It shows your @mentions, replies, etc. Very much like Workplace’s News Feed.
Yes, but Microsoft did something a little funny with this one. The Teams app is the most advanced on Android—there you can make video and audio calls. iPhones and Windows Phones don’t have this yet. I’m sure it’s coming, but for now, Android users win out on Teams features.
I find two main differences, which you could call ‘advantages.’
One: Threaded conversations are native in Teams. (Slack did add this recently.) For those who are used to Slack’s message format, this might take a little adaptation time. But for those used to forums or sites like Reddit, threads are familiar territory.
Two: The Office 365 Integration. That eliminates extra cost, extra user accounts/licenses, and installation time. It’s one more tool in the toolbox.
Want a more direct comparison? TechWyse Blog did a great infographic comparing Teams and Slack:
Teams vs. Slack – TechWyse
Nope. Not even to try out. I used a test user from a customer’s Office 365 account to try Teams.
This makes me sad, honestly. Teams is good enough to work as a standalone product. But I guess that’s not part of Microsoft’s strategy anymore (and we just have to live with it).
No. No plans for this at all.
That could change of course. I would like it if it changed. Slack made clever use of a free version to bring customers on, and Microsoft won’t even try a similar approach? It could even be an easy avenue into Office 365.
The numbers are very close here. Workplace is competing on price, but we’re talking a few dollars’ difference per user.
Here are some numbers from each service. I’m going to assume a standard account type, for 100 users.
- Workplace: $3/month per user (for the first 1,000 users)
- HipChat Plus: $2/month per user
- Slack: $8/month per user
- Microsoft Teams: Depends on Office 365 account level. Office 365 Business accounts range from $6-15/month per user. Office 365 Enterprise accounts range from $8-35/month per user.
As you can see, it’s really close. Teams could end up “costing” more than the others, but you’re also getting Office 365 bundled.
T-Bot is ready to help you on load. He’s (she’s? It’s?) really quick to respond too. I fired a few standard questions at T-Bot, and he gave exactly what I needed. Much like Slackbot, Slack’s own bot (who admittedly has a cuter avatar).
Unfortunately, T-Bot lacks a sense of humor. I tried some silly questions and a philosophy question. Poor T-Bot got confused and sent me to the FAQ.
Plenty! Teams comes with 150 third-party integrations available at launch. More will come.
To integrate a service into a Channel, click the plus icon in a channel’s top nav. You’ll see a popup window with available integrations.
I integrated Asana, our project management system. It took one login and about 20 seconds.
That’s one fewer tab I need to keep open right there.
This one deserves its own section. Because there is one big drawback to Teams…and no, it’s not the Office 365 bundling. It’s an operational flaw that many users have already come across. And it’s already hurting Teams adoption.
The Damaging Flaw: No External User Access
You cannot invite external contacts to use Teams.
I have a Skype for Business user account. But it’s Server-based, not O365-based. Thus my trial account couldn’t see it, and I could not send messages “out.”
This is the biggest issue I saw people having with Teams. It just befuddles me. Limited only to O365 users? No possibility of inviting someone into a chat, even temporarily? None.
Annoyed by this? You’re definitely not the only one:
How can we make Teams better? – External Access and Federation
This WILL hurt Microsoft. As I said, some potential users are already swearing off Teams in favor of Slack, where they can chat with external users. Now, maybe losing market share will compel Microsoft to enable external users…but a lot of people aren’t holding their breath.
MORE TEAMS LINKS:
Teams is Microsoft’s Most Intriguing Productivity App Yet – Engadget
Microsoft Teams goes live with new email integration, enterprise bots – ZDNet
Teams, Microsoft’s Slack rival, opens to all Office 365 users – TechCrunch
Microsoft’s Teams is almost an excellent Slack-killer, and it’s now live for O365 – Ars Technica
Teams: Feels like an Evolved Skype for Business Persistent Chat
Teams isn’t just competing with Slack. It also competes with HipChat, Workplace, and to some degree, its own Skype for Business Server product!
Here’s why I think that. The Channels, available under Teams (which are either Public or Private, as set by administrators), are basically enhanced chat rooms. Skype4B’s Persistent Chat has a very similar structure. Private messages are essentially Instant Messages. You add voice to existing Conversations. They’re even called the same thing in both Skype for Business and Teams. “Conversations.”
The other Skype4B functions—voice, meetings, IM‐were covered in Office 365’s Skype for Business Online offering. Teams adds the Persistent Chat function.
Now, that’s not a bad thing in itself. As I’ve said many times, I love using chat. But I can’t help thinking Microsoft has miscalculated here. They’re trying to replace one product with another, but hobbled it by not allowing external user access. The MS Walled Garden rears its ugly head.
We’ll see how many people decide to climb over it or not.
Do you have a Teams question nobody’s answered yet? Send it in! Add a comment or email it over. I’ll happily update this post with it. Or create a new one, if the question merits.
And please share your Teams experiences too! I’m certain we’ll come back to Teams, soon enough.