Teams + Skype for Business

The integration story between Teams and Skype for Business is an important one because the amount of overlap between the two products is surely going to cause all sorts of confusion among customers.  So having the two worlds talk to each other is going to be important.

The good news is, there is an integration story if you are using Skype for Business (SfB) Online.  The bad news is, if you are on-prem with SfB, there is no integration story and a few things are going to be less than ideal overall.  At the current time, the only integration between the two platforms is the ability to instant message between the products.

[EDIT: I didn’t mention it here before initially I did in my larger review you can see SfB Meetings under the meeting tab.  Intent here was to talk IM/P integration specifically.]

Scenario #1 – Microsoft Teams user sending to Skype for Business User


A few things I’ve notice about this workflow that are important to call out.

  • If the SfB Account for the Sender is hosted on-prem its going to fail with a bad error message.  As you can see in the screen shot, it will make it appear as though you can send the IM message at first but will just get stuck in a sending state forever.
  • Although the user is logged into and using Microsoft Teams they MUST be enabled for Skype for Business.  If the user isn’t enabled for Skype for Business, then nothing works.
  • SfB Presence is VERY SLOW to update and is misleading.

What does that last one mean?  When a Microsoft Teams user logs into the client it is also logging in via a customized version of UCWA to the Office 365 environment.  You can see this to a degree from the SfB Client.  If you are logged into a Skype for Business client as the receiver and the Teams user is not logged into SfB or Teams, they will appear offline.


Once I have logged into my Teams client as my sender you will notice the status update for the user.


When I log off of the Teams client, you will notice the presence doesn’t update and it appears as though I’m still online.


I’ve tested it a few times, it will remain in this incorrect presence for a solid 10 minutes.  The user will go to Away after 5 minutes and then eventually to Offline.  It appears as though the log off event from Teams doesn’t trigger a corresponding log off event in SfB Online through that customized UCWA implementation.

Outside of the above item of note the IM/Presence integration works exactly as expected.  Users from Teams can start an IM and continue that conversation with a Skype for Business user.

Scenario #2 – Skype for Business user sends message to a Teams/SfB User

In this scenario it’s all about where the receiver (User B) is hosted and which clients the user will get the toaster pop in.  Essentially, if User B is hosted in SfB Online and logged into Teams at the same time, they will get dual notifications – one in SfB and one in Teams.  If the user is user is hosted on-prem for SfB then they will only get a toaster pop in SfB.


Hopefully that takes a little bit of the mystery out of Teams + Skype for Business integration.

9 thoughts on “Teams + Skype for Business

  • Pingback:Introducing Microsoft Teams | Inside Skype for Business

  • November 3, 2016 at 8:17 am

    Great review and simple explanation of the current issues with SfB integration with Team. Hopefully with feedback like this making it’s way to Microsoft this will be resolved before GA next qtr.

    Look.forward to your updates.!

  • November 5, 2016 at 11:24 pm

    Thx for your reviews Richard. In terms of Skype for Business interop, we do interop with Skype for Business meetings in that you see them in your meetings list after clicking on the Meetings button in the app bar. Clicking join will deep link you into the appropriate meeting inside the Skype for Business client.

    –Brian MacDonald, Microsoft Teams engineering

    • November 7, 2016 at 8:13 pm

      Thanks for the note Brian. Yeah, I did mention it in my other post but should have noted it again here. Thanks!

  • December 1, 2016 at 7:38 pm

    We are seeing an issue at work where someone on Teams tries to have a 1:1 chat with someone else on Teams, so when they search for that person to start a conversation (with no prior conversation history with that person in a 1:1 chat), it’ll pull up the persons SFB contact rather than their Teams contact. So the person will end up sending a message to the receiver from Teams -> SFB, rather than Teams -> Teams.

    Any ideas? I wish there were a way to turn off the Teams -> SFB integration.

    • December 5, 2016 at 9:53 pm

      If the person has never logged into Teams yet it will default to SfB (it assumes everyone is using SfB it appears). I don’t see a way to turn it off. If the person is in Teams but it’s still trying to do a Teams to SfB IM, then I would suggest filling a bug as that is not how it’s supposed to work.

  • Pingback:Microsoft Teams integration with Skype for Business | The Cloud Mouth, Loryan Strant, Office 365 MVP

  • March 20, 2017 at 12:30 pm

    Hi, Do Microsoft have Persistent chat good roadmap in future for on premise or this will be replaced by Teams for on premise


    • April 3, 2017 at 1:09 pm

      I have no seen anything in a public roadmap for PChat in years. I fear it’s dead (I’ve been saying that for 5 years now but who knows).


Leave a Reply to Tony Cancel reply

Your email address will not be published. Required fields are marked *