If the domainA is allowed, the message is sent to the Front End.

The federated Edge receives the SIP message and verifies whether it’s on allowed list, in order to determine if domainA is allowed.

and identify the FQDN and port where the message has to be sent

The Edge will query the record _sipfederationtls._tcp.

If it’s federated then the message is sent to the Edge.

Front End server checks if the domainB is federated or not.

When the user in domainA send a message (INVITE) to the user in the domain, this is what happens: In O365 the federation can be configured in the Legacy Skype for Business portal à Organization à External Communication:Īfter you enable the federation at tenant level, you might wonder how the user in domainA can talk to the user in the domainB. In an on-premise environment the federation can be configured from the Control Panel: How to configure federation in your organization

With federation we describe the possibility to talk to external organizations which are using Skype for Business/Lync.Įvery company can decide to enable federation for specific domains, block specific domains and allow the federation with everyone (open federation).

Let’s start with some theory and describe how federation works in Skype for Business. I therefore decided to write a post which sheds some light into the federation between Teams and Skype for Business topic.įederation is one of the topics which is evolving quite rapidly, and what’s written today (August 2018) might change in the next months. It’s been a while since my last post, but I’ve been receiving several questions about the topic lately.

What happened to skype 2019