Collaboration is a core element of how we work which requires the creation of extended teams on a project or long term engagement. Whilst the majority of our teams are internal staff, there is still a critical element of any project that requires the inclusion of our clients and/or external vendors. It is imperative that Microsoft Teams allows for the easy (but secure) inclusion of external parties for the length of any project or engagement.
This is why historically products like Groups etc. have not been adopted as widely as we would hope. If the tool only allows for 60-70% of a team to participate, it breaks. If a tool does not allow 100% of those who need to be involved to participate equally, if breaks and our users and clients have far too many alternative solutions that they can easily adopt (Slack etc.) to quickly and efficiently do their jobs.
Finally, making external parties sign up for a Microsoft account (such as Hotmail) to authenticate against any collaboration service does not work, and better approach is required and needed.
The #1 requested feature for Microsoft Teams is now here!
We’re starting to roll out the ability to add anyone as a guest in Microsoft Teams. This means that anyone with a business or consumer email account, such as Outlook.com, Gmail.com or others, can participate as a guest in Teams with full access to team chats, meetings and files.
Thank you all for your feedback and support!
749 commentsComments are closed
Graeme Baker commented
Agreed, there are some things that are company wide that we want people to be able to access, but having a separate team that everyone is automatically in seems cumbersome
This is a must have, our team products have multiple consumers within the company, we need a channel for them to subscribe for all notifications, discussions.
This is a deal-breaker for us. We use Slack to help centralize communication with clients on projects. Until Teams has this function we can't even consider moving away from Slack
Love the idea of inviting to single threads!
This is HUGE! Especially as ad hoc communications often need to break down formal team boundaries. Huge.
This needs to be accessible in a browser, last thing big organisations want to do is have to download apps, secure invite link and they are straight in with a guest account - ability to link to their own org's office account or their own personal if they wish, limit what they can do such as download files etc as a bonus
This is crucial for us to consider this for deployment. Microsoft please act fast on this !
SunKee Hong commented
Public Teams or Channels are EXACTLY what we need. At the moment, the only work around are very cumbersome:
A: Create a company wide team and have hundreds of channels under it, and constantly and manually add new people.
B: Add the entire company each time you want to create an open team.
SunKee Hong commented
Yes! I totally agree. Also, the ability to change the visibility & access of an existing Team (like a Facebook event)
Ian Jones commented
Cannot agree more with this.... Take that philosophy to OneNote as well... If this doens't happen, all of these apps will be circumvented by Slack, etc.
I tried changing the group in Outlook to public but it took no effect in Teams.
c b commented
And actually, having Public Teams or Channel option is really ideal because it allows something like this:
A channel is discussing something, and someone wants to ask a question to someone not in that channel/team. They should be able to just type @whoever and it ought to immediately give them the option (if allowed) to add that person to the chat, so the person can seamlessly see the question, hop in, and answer. They can later leave the team if they want.
David Grand commented
Same as this suggestion with hundreds of votes now: https://teamsfeedback.uservoice.com/forums/555103-public-preview/suggestions/16911109-external-access-and-federation
c b commented
First of all, NICE WORK MICROSOFT!! This Teams app is what we were expecting the whole O365 with Skype and Yammer to be like! This Preview release is so far working WAY BETTER than your Skype for Business!
And Public Teams or Public Channels (that don't belong to Team?) would be great so we can have a public chat area.
Adam cogan commented
I work for SSW and sadly this is a blocker, for consulting organisations.
Contrast it with Slack. My guys are in a heap of Slack teams for different clients and that works great. It doesn’t look like we can have multiple accounts open at the same time in Microsoft Teams.
Tobias Johansson commented
Totally agree on all parts of this, especially the last bit where people have to sign up for a Microsoft Account. People use Dropbox and Slack for a reason, the simplicity to share and collaborate.
We are testing Teams company-wide as-we-type, and for us to take our conversation over from slack to teams we need some ability to create public teams.
As Microsoft comes to the table with a Enterprise-mindset, I understand that you create a product that is in effect 'closed by default'. But the 'open by default'-mindset that is built in to both Slack's and Atlassian's offerings are, to my mind, one of the core reasons their products work so well.
I'm working with users from a different company with different Office 365 tenants. It would be great, if you could invite also external users to Microsoft Teams
It seems, that behind the scenes a private group is created for each team. There should be an option to create a public team / group instead.
Hans Schillemans commented
Add external users (from outside your oragnisation) to a Team.