SfB User in a Microsoft Teams World

So with Microsoft announcing full interop between Skype for Business On-Premises and Microsoft Teams I decided it was time to take the dive and make some changes to our Office 365 tenant.  So what did that journey look like.  Let’s start at the beginning:

Day 1

Setup hybrid for Skype for Business.  This isn’t very hard in SfB 2015 and there is a wizard from within the SfB Control Panel to accomplish these tasks.  So the tasks were:

#1 – Make sure that Azure AD Connect was functioning like we thought it should be.

#2 – Run the SfB Hybrid wizard and ensure that Get-CsTenantFederationConfiguration -SharedSipAddressSpace is set to $True.

This setting can take up to 24 hours to apply.  So off to do some other work.

Day 2

Migrate the user you want to be Teams only from your Skype for Business On-Premises to SfBO.

Move-CsUser -Identity sip:user@domain.com -Target sipfed.online.lync.com -Credential $cred -HostedMigrationOverrideUrl https://admin1a.online.lync.com/HostedMigration/hostedmigrationservice.svc

NOTE: Remember to update/change admin1a to your correct SfBO tenant.

Day 3

Next we need to configure our environment into the right mode.  By default, your Teams Upgrade policy is either in Legacy or Islands.  Both modes are eventually going to cause all sorts of heartache and issues for you.  I would HIGHLY recommend getting out of either of these modes as fast as possible.

Since our organization is a Skype for Business shop it was easy enough to set our organization default to SfB Only.

As you can see, there are three modes currently supported.  In the near future, we will see two additional modes related to Skype for Business interop and those are Skype for Business + Teams Collab and Skype for Business + Teams Collab + Meetings.  I think Microsoft announced at Ignite we should see those by early 2019 if my memory is correct.

The second item we need to do is setup our Teams to allow it to Chat/Interop with Skype for Business. By default, this is disabled.  So from the Modern Portal go to Teams Settings under Org Wide Settings.  Scroll down a bit and you should see this:

Next, we need to setup a Teams Only user because that is the whole point of this exercise.  So again, from the Modern Portal, you will go to Users and find the user you want to move to MS Teams:

Now this is the important part!!!  For this interop to work correctly, the user who you set to Teams Only MUST HAVE BEEN migrated to Skype for Business Online.  If they are a Skype for Business On-Premises user nothing is going to happen here.

These routing changes can take up to 24 hours to complete.  So it’s time to wait again.

Day 4

Everything should work.  When people IM or Call from Microsoft Teams to Skype for Business On-Premises users it should just work.  It’s magic!

<celebration time!!!>

 

 

It’s Not Magic!

OK…so what if it’s not magic and doesn’t work.  Like mine.  A few things to check.

#1 – Teams to Skype for Business Chat.

This one was a bit confusing at first.  Everyone in our organization was in Islands mode and that means some users had been using Teams, some not so when I tried to Chat/IM from Teams->SfB I found that some users got message in Teams and other in SfB.  It was ALL OVER the place.

The issue was, I was using an existing Teams Chat thread and I thought it would be smart enough to route to the right place.

So as you can see above I have two different chats going with Matt.  One in Teams and one in SfB.  I can tell based on the icon.  This because a Skype for Business Only mode doesn’t actually take away anything from the Teams client.  In the future, this will be changed and my guess is even with that change, if I tried Chat/IM with an existing thread it would go no-where and just cause confusion.

So the key for the Teams user, is to start a new thread using the New Chat button at the top of the page, that will let you create a new Teams -> SfB Thread and then it will show up in Recent and just work.

 

#2 – It’s really broken.

This is going to happen to what I hope is a very SMALL handful of customers but in case it does here is what happened.  So when I did all of the above, when a Skype for Business user would Chat/IM with me the message it would “break” through my upgraded client.  Check out the below:

So if I was running my SfB Client, it would tell me I was updated and now using Teams but if someone tried to Chat/IM with me it would still appear as a Chat window.  Absolutely crazy stuff.  If I closed/exited SfB on my desktop then the SfB user would get a 480 No Devices Available.

After a lot of looking around, I finally decided to go to MS Support.  As always, the first line of Support was less than great and even tried to close the case telling me this wasn’t supported.  After getting the right people to look at it, it was escalated and they found the issue real fast.

When MS Support ran the Get-CsTeamsConfiguration -Tenant 06739bd6-…my…tenant….id….52589 | fl * it returned the following:

EnabledForMessaging : False

As you can imagine, not being enabled for Messaging seems odd and it was wrong.  So they have to enable my tenant for messaging and suddenly it all works.  A few notes: #1) This command is not customer facing so you have no clue what it’s set at.  #2) You have no ability to change that setting either, so who knows how our tenant ended up in this mode.

 

I’ll continue to update this post as I learn new things but as of today I’m a Skype for Business user living 100% in Teams now.  I’m guessing federation doesn’t work, right?  🙂

 

 

 

2 thoughts on “SfB User in a Microsoft Teams World

  • October 10, 2018 at 6:34 am
    Permalink

    Excellent article… I thought it was just me – lol.

    I must say, the somewhat heavy handed announcements from Microsoft about Teams is confusing customers. Federation “challenges” with Sfb is enough of a reason not to go to Teams. This is really too bad. I think Teams has tremendous potential. However, the current “Integration” with Sfb is flaky, and untrustworthy at best.

    I wish Microsoft would slow its roll a bit and get it right. This type of confusion won’t drive adoption of Teams, more like driving the adoption of Slack or WebEx Teams. I do t want to see that happen when there has been so much progress with Skype.

    Reply

Leave a Reply

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