Microsoft Teams supports various ways of communicating with external users.
When it comes to direct messaging, you'd have thought it would be simple to send a person-to-person message even if they're not in your immediate team.
Microsoft Teams direct messaging federation helps support cross-tenant and cross-platform messaging.
In this post, we dig into which option is best for your scenario and explain how to configure each one.
External access, also called federation, is probably the most common method you will be using when communicating with external users.
It means that you can chat and make calls with users outside your organization that also uses Teams or Skype for Business.
There’s also the possibility for a user in Teams to chat with people that use the consumer version of Skype.
In the Teams Admin Center you can Enable/Disable external federation.
You will have two settings which both are enabled by default.
The first setting must be set to “On” to chat with external Teams and Skype organizations.
The second setting set to “On” enables the same with Skype consumer users.
You also have the option to block or allow external access to and from certain domains or from all domains.
By default, no domains are present which means you can find, chat and call people external to your organization in any domain.
This is also called “Open federation.”
To add or block from all domains, click "Block all external domains."
To add or block a specific domain click “Block only specific domains.”
A prompt will appear in where you can type and add a domain and choose to either allow or block it.
Keep in mind that this is either an “allow all except blocked domains” or “block all except allowed domains” configuration.
This means you can’t mix allowed and blocked domains.
You either add the domains for those you want to enable external access and block all others, or you add the domains you want block.
As an example, I added the domain “microsoft.com."
The outcome of this configuration will be that your organization can communicate with all external domains except those using a microsoft.com user account.
Once complete, Microsoft Teams direct messaging federation is achieved.
There are a few gotchas and limitations to consider using external access.
Guest access differentiates from external access in several ways.
Using guest access means you invite a user using the “add member” feature in Microsoft Teams, using their email address.
That user then accepts your invite and become a (guest) member of the team.
You will know which accounts you are a guest in by the "Guest" text in your drop-down options where you change tenants.
This means that a guest user can access your organization’s teams and all its resources like channel conversations, files, Planner etc.
Furthermore, a guest user can use the chat tab in Teams to start direct messages or group messages (and even calls) with your internal users.
For guest access to work, guest access must be enabled in your tenant.
In February 2021, Microsoft is enabling this by default.
Set “Guest access” to “On."
The change can take a few hours to take place.
After that, you can invite people outside your organization to your teams.
Add the guest by clicking “+ Add members” in the chosen team’s settings.
Type the whole email address of the person you want to invite and click “Apply.”
An invitation is now sent to the email address entered.
As soon as they accept it, they can chat with your internal users and Microsoft Teams direct messaging federation is achieved.
As a guest user in Teams you have several benefits over using External access for communication, but there are still limitations.
Mindlink provides an XMPP Federation Gateway to enable Microsoft Teams direct messaging federation with Skype for Business 2019.
It supports bi-directional instant messaging and presence modalities allowing federated partners to communicate between platforms.
MindLink XMPP Federation Gateway supports Skype for Business 2019 (On-Premise and Online) and Microsoft Teams for the following modalities:
The federation gateway is not currently self-service.
If you need to set up Microsoft Teams direct messaging federation specifically for Skype for Business 2019, you can contact the MindLink team here.
Google Chat is quickly emerging as a frontrunner in the enterprise collaboration tool industry.
Given that 91% of enterprises use at least 2 chat platforms, it's likely that different teams within your organization may use both Google Chat and Microsoft Teams.
When this is the case, it becomes unproductive moving out of Teams, into Google Chat, and starting the conversation again.
That why Mio integrates Microsoft Teams and Google Chat for native cross-platform messaging within your enterprise.
With Mio, you can connect direct messages, channels/spaces, and group chats. Functionalities such as rich text formatting, editing and deleting messages, file sharing, emojis, reactions, and GIFs are also supported.
Users can stay in Microsoft Teams and message their colleagues on Google Chat.
Learn more about Google Chat interop here.
2021 not only saw Microsoft Teams users grow to 145 million but saw Zoom's customer base increase exponentially too.
While people at home were hosting quizzes on Zoom, businesses were embracing the video conferencing tool for Zoom Phone and Zoom Team Chat too.
The result?
Instances of both Zoom and Teams everywhere. But, chatting between the two platforms is a challenge.
Mio syncs the conversations your employees have on Microsoft Teams and Zoom.
Once installed behind the scenes, the interoperability tech translates your Teams messages to Zoom Team Chat – and vice versa.
It grabs messages sent from Microsoft Team to Zoom users, and delivers them on the other app.
By embracing message interoperability between your two favorite platforms, your users can:
This means can stay in Microsoft Teams and send messages to users in Zoom Team Chat.
And the same is true vice versa! Your users who prefer Zoom Team Chat can stay in Zoom and message users on Microsoft Teams.