Hi everyone -- I'm splitting this feature out from the "Guest Access" feature request so that you can weigh in on this specific issue and provide feedback for it here. Please write in the comments what you would like to see with Federation and I will incorporate it into this description. -Suphatra
#1 -- When our team have a live call meeting we can not add people to the call that doesn't belong to the team, even if they are from the same company. Additionally can we brought client which will be federated.
#2 -- Need to be able to P2P chat/call/screen share with federated partners and other Office 365 tenants that are trusted by default. Need to be able to add all of these same people into meetings.
Of the two items in this request, #1 is complete and available.
- is still in the works.
This is part of the convergence roadmap – https://skypeandteams.blob.core.windows.net/artefacts/Skype%20for%20Business%20to%20Teams%20Capabilities%20Roadmap.pdf
As more details become available for item #2 I will share them with you.
It's unbelievable that Federation wasn't part of this. It's been a part of Lync/SFB since pretty much day one. Honestly, whoever designed this product should be looking for a new job. If you intend to replace S4B with Teams it must do 100% of what S4B does plus the new features. It'd be like Ford designing a new car and forgetting to include tires.
Peter Braun commented
Has been mentioned a few times already, but as there is no like button on comments, here again... it would be great, if at some stage, we could use Teams to interact with non-Office365 tenant users. Being able to share something, chat, screenshare, voice or video call with someone who gets invited via their MS/Skype, Google or Facebook account via web based Teams client would be great. On top, interacting with a Skype client user would take Teams to a whole new powerful level.
currently if having a chat with federated user, this information is not showing on my own Teams window. it is challenging to have to go back and forth between tenants to view the threads/chats.
Brad Friedlander commented
We need to be able to add an external person (e.g., a customer) using their real (own domain) email address to specific channels within a Team. This type of guess has no visibility or permissions without explicitly adding them (as opposed to Team members who have the same access to all channels).
Mark Jones commented
Federation with customers would be amazing. The ability to set policies as to who can share with who would be even better
Richard Lynn commented
You realize that the answer to your problems is $4 per month, right? FOUR DOLLARS.
You are seriously too cheap to spend 4 dollars to keep your team chatting?... And that's somehow MS's problem? *eyeroll*
Marco Janssen commented
Really missing the ability to add non-Office365/Microsoft accounts as guests
we have security requirements that we can limit users from federated partners only approved users or department instead of the whole company. we would like to have control on policy like file share, screenshare etc.
I would like to add a guest who is does not have 365 business. We work with volunteers out in the community across our province and would like to meet with them on projects we are working on together.
Federation so team can be shared outside of the home enterprise, this needs to be full federation not guest sign in for approved users.
We need to be able to allow collaboration with outside users at scale, so can't do this on a one after another / individual level but need controls @domain.com level.
Let's go federation!
this feature should include a list of tenants in which UPN is registered
and it should be possible to switch between the tenants (just like on portal.azure.com)
otherwise it would be a mess in the teams and chats list
James Arber commented
The Guest Access feature is nice, but its clunky to sign out of Teams and Sign in again on a clients. Federation similar to Skype4B would be a brilliant way to allow users to be members of multiple Teams tenants whilst still allowing users to see the benefits their local Teams instance provides.
Josh Sullins (Michelin) commented
Yes, please!!!!! Let's go federation!
David Rosenthal commented
We need to differentiate what federation means in this blended world please. Federation in the Skype world is something completely different than federation in the SharePoint world. We are now blending these worlds together in Teams, so we need to properly understand what we are talking about here and what capability is being offered.
Need to be able to P2P chat/call/screen share with federated partners and other Office 365 tenants that are trusted by default.
Need to be able to add all of these same people into meetings