Teams supports federated guest access for Gmail accounts using the identity provider framework of Azure B2B Collaboration. Office 365 tenants must first decide if they want Gmail accounts as guests in all or some teams before going down the federation route. Why Teams and not other Office 365 apps? It’s all to do with the endpoint used by the client to connect. If it can handle federation, all good. If not, it’s standard Azure B2B Collaboration.
Outlook can schedule online Teams or Skype for Business Online meetings. But what marks an online meeting as different to a regular Outlook meeting? The magic lies in a set of MAPI properties populated by Outlook to help meeting participants connect to the right online meeting. A little poking behind the scenes with MFCMAPI reveals more.
Microsoft Teams now supports the ability to post a topic to up to 50 channels at one time. It’s a feature that no doubt some will welcome with open arms, but it does come with a downside. For one thing, multi-channel posts might lead to a form of the email reply-all storm. Another potential issue is that there’s no good way to see the replies to all the messages posted in the target channels.
Teams is all about open communication, but sometimes you just want to make a statement and not have a conversation. You can do this by restricting replies to a topic, in which case only the original author and channel moderators can reply. And if moderation isn’t used for a channel, team owners take that role.
Office 365 Informatiom Barriers allow tenants to erect communication firewalls between different groups. Teams supports Information Barriers, but currently has a problem adding new guest accounts to team memberships. An easy workaround exists, but debugging what’s going on is difficult because of the lack of clues.