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!
768 commentsComments are closed
Dimitar Miriyski commented
You can actually switch to a public team after the team creation.There is a button "Open in SharePoint", right next to the team name > channel on the top bar. Then click on the context menu, Edit Group and you can make it public. Unfortunately there's no way to search for public teams... except to look for the group's name in Outlook.
c b commented
We might have to have more security controls to limit an external (or even internal) user to just see specific Channels on a Team. Not always be allowed to see ALL Channels within a Team. There essentially is the need for just a Public "team" with Channels (which can be private or public). Then if people want to create "Teams" they can to remain more private or segregated. But of course that too can just show up as a type of Channel.
Michael Hayes commented
Yes, the ability to involve external team members is essential. Otherwise, this product will lack the flexibility of Slack.
Enable SSO via OpenId Connect. Allow teams to authenticate based on what systems administrators configure. e.g. Allow Teams to use "defined" LDAP forests, or a O365 administrator might configure an LDAP authentications backing store and allow 3rd parties to Authenticate with Google. Allow claims for various connectors, like Sharepoint, to be configurable. But at the end of the day, it should be very simple for 3rd party (non-technical) people to join Teams.
Maksym Mikhalov commented
We're happy to use new collaboration tool from Microsoft but it is losing any sense to use it without external contacts.
need a way of creating a public channel within my team that can be viewed by all users in my organisation or designated teams within my organisation.
Current structure doesn't allow for adding a public channel for each team
Daniel Harris commented
@Ryan Green one issue with external users having to create an MSA to gain access also goes against the direction MS are going in terms of how they want people to use the MSA.
For example, they recently made it so that you can't create a new personal MSA using a domain that is active in Office 365, which means users have to create a new personal MSA using a new outlook email address etc rather than using your works email address.
I think they are really trying to push the idea that an MSA is for personal use, and an O365 Org account is for business - That's fine if both parties use O365, but if the external user doesn't then there's a number of things they have to do to set one up which involves getting sign off from their IT dept. etc.
Daniel Harris commented
"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."
I would definitely agree with this, it would be nice to be able to create Office 365 accounts for them and just provide them with the temporary password, and we could then remove the account or lock them out as needed from the usual interface.
The problem with that is licensing, since external users don't need licenses in most O365 external access scenarios - That would get expensive if you want to create guest accounts under O365 admin right now and assign licenses
+1 We need this one!
The ability to create a team, where folks can freely join and exit.
So far our evaluation of MS Teams has been positive but if we cannot use it with our outsource vendors then it is useless. Please add this functionality ASAP.
Ryan Green commented
I like most of this but it should have been pared down to 1 issue per request and this has several.
As for creating a microsoft account, I dont see that as an issue, if you are communicating with those parties with skype or slack they had to create accounts for those platforms why wouldn't they for this one? And my personal microsoft account is my gmail email, so you dont have to sign up for a outlook.com account to get a microsoft account.
An Office 365 public group can be part of a Microsoft Team and will include the external users associated with the group.
I Agree 100%. I have mentioned this more than once. External access features and functions are imperative for the small and medium business world. As a matter of fact it will be an excellent "free" marketing tool as external contacts are getting curious about Microsoft products.
David McKnight commented
These are the same comments I had when Planner preview was introduced. For Groups, Planner and Teams to meet their potential, I have to be able to collaborate with contractors and clients.
Mike baker commented
for external Secure should come with basic domain block capability, Basic RMS to protect files or a light touch version of your Adallom for tracking/DLP that isn't in a E5 or E5 EMS bucket.
Absolutely a must have if we're going to test this beyond current state. External team members/collaborators should be a given.
This is really very necessary ! thx
Not having external users will be death of this product. Stunned that it does have it out of the gate . . . that is old msft not new msft. Disappointed.
Arnau Panosa commented
We have the need to have channels in teams that are public to non-members of the team. This would be used, for instance, to create "support" channels so that any user can ask questions in a particular team's public channel, or to create public channels to post news or notices relevant to that particular team, but accessible by any user. This obviously also requires the ability to find those teams and their public channels. As far as I have seen, currently you can only find teams that you belong to.
Ehtesh Choudhury commented
Is there a company wide team for the "Microsoft Teams" group? That would also be appreciated.