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
Its great to have guest access on a project level for one-off partnerships but can you allow guest access on a domain level (IT or admin to add) as well? WE have a few freelancers we work with on multiple accounts with multiple teams so adding them to various TEAMS reduces who has access to chat with them. If a new project whats to ping them for availability or a question they need to set up a TEAM to have the ability to chat with them.
Progress is being made on what Warren? It's clear that the crux of this thread is that current features are inadequate.
Great to hear you're working on them - but clearly there's a need to understand if they'll be fit for purpose.
How can I leave MS TEams as a guest? I am member of 4 different tennants as a guest. Can I leave them on my own?
Peter Ruzicska commented
Need IT control about the invitations, probably an accept-deny email to the IT team would be enough BEFORE the invitation sent out. Also a simple Microsoft account should be enough to be a guest.
Glad to see this is being worked on as it is a total blocker. I'd drop other things and focus on this as the top priority if you aren't already. Let us know when finished and we'll reconsider Teams but we have no choice but to stay with Slack for now.
Alison Trinidad commented
Feedback re the new features on MS Teams rolled out today. Tested by sending invitation to personal email. When trying to click on the link in the email invitation from my personal MacBook Pro (which does not have Teams app installed), the link was not recognized by Safari or Chrome, nor was it recognized on my personal iPhone. As the meeting organizer, when I clicked on the link from MS Outlook, it opened a link in Safari no problem and automatically transferred to the MS Teams app.
The call-in function worked perfectly, though. Just couldn't share screen or present.
Jed Boulton commented
"Only Office 365 work or school accounts can be added as guests." thanks! now my engineering group is going to communicate with their software dev consultants via slack. This should have been built into this product from the beginning
Guest Access for parents would be helpful as schools begin to implement Teams within their classrooms. Many parents will not have an email address that aligns with Office 365 and this would create a huge barrier between home/school communication.
Can I assign a Teams license to a Guest to allow them to be an admin of a Team?
This is extremely limiting to my team and appears it should be a rather quick and easy fix. Please get on it! This product is still in alpha stages at best.
Rogier Blok commented
Guest Access (without Microsoft account) would make this product so much better. As a Global project organization it is essential for us in the further roll-out of Teams.
Shawn Keene commented
The FAQ is not clear about Microsoft Accounts, or if we can invite someone in our Azure AD that doesn't have an office license assigned (like a contractual temp worker that needs to collaborate with a team).
Existing guest access does not work. My vendor has O365 and uses Teams, but gets an error every time they try to follow the invitation link - "Issue Type: Failed to accept invitation". This is such a basic failure. Both companies have opened tickets with MS and the responses have been 100% unhelpful. We'll keep using Slack until Teams's basic functionality actually works.
I was excited when reading through this and saw "IT'S HERE!" It's not here. You've just allowed paid Microsoft customers to use resources in someone else's tenant. We need real guest access to be able to implement this anywhere.
@warren I want to implement this today, but it's not possible. Collaborating with several firms on one project can't be done. Some of them use Google for Business or self-hosted emails. I imagine a few of them have O365 but certainly not all. I suppose that leaves Slack... alas
Please make it public, allowing anyone to be added, not only MS subscription holders. It can only add value and a positive image to MS Teams
Need to be able to add a guest with any email address, not just a MS address
It's super easy to do that. Not sure what's holding you. Just create a special user account...
Michael Kulpa commented
The current implementation of "guest access" is effectively worthless. If I want to participate with another organizations "teams" instance I have to sign out of my account and into the guest account for their instance.
It's unusable for us at this point and I hope true public federation is implemented.
Ivor B commented
I support the idea of making the Team App standard access to all MS Outlook/Hotmail accounts (even as Guest access) but that is still a stopgap, as several people have commented. I'd like to remind you of the aims Angela set out above over a year ago:
"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."
What we need is a way for a Team admin to add anyone they need to the Team on a structured basis - as a Guest, as a Full Team Member, even as a lower-level Admin, and with strict controls over that addition - say time limited and/or password controlled. This does not need to break Office365 security but it does require a more open access policy- one that it is perfectly possible to implement.
Such a change would instantly make Teams a go-to app and make Office365 an even more desirable option for smaller organisations and charities, who are currently still faced with sorting out a variety of replacement apps to fit their needs. I don't understand why Microsoft are not prioritising this.
Regards from gloomy London UK.