top of page
  • Writer's picturesamanthaeasterday

#microsoftteams #teams #teamsdirectrouting

So you want to set up external calling in Teams. There is a lot of information out there about direct routing in Teams. Microsoft actually does a pretty good job documenting it. But one thing that gets lost in the documentation is creating an account with the new sub domain. Below are the steps to set up an SBC in your Teams environment.

  1. Your telco has set up their Microsoft supported Direct Routing SBC. They will provide you a FQDN and port they have set up as a tenant on the SBC.

  2. Go to your 365 Admin Center. You need to add that FQDN as a sub domain for your organization. Once you do that, you will get information similar to the below, which you will need to share with your telco.

3. Once the domain is verified by both parties. You can move forward.

4. This next step is one that gets missed. You need to create a user, using the new domain. If you don't do this, you will get an error when adding an SBC. In 365 Admin Center, add a user with the domain. You will want to think about the naming convention now, because most likely, your SBC list will grow.

5. In the Teams Admin Center. Go to Voice-> Direct Routing. Click Add and change the necessary settings.

6. Click Save

7. In the same page in Teams, click on Voice routes.

8. You'll need to set up routes. I set up 3, LocalCalling, LongDistance, International. Once they are set up. Click on the route to edit. Chose Add/remove SBCs. You will now see the SBCs you have enrolled. You need to click the boxes and press Apply.

88 views0 comments
  • Writer's picturesamanthaeasterday

#microsoftteams #teamsdialpad #phonesystemlicense #teamsdirectrouting

I set up direct routing with our sip providers sbc. But didn't have a dial pad in Teams to make any test calls. After some research and convincing our Microsoft support provider of the licenses I need (that's a different story). I outlined you need 3 things to have a dial pad in Teams.

1. The user must have a voice license, like Phone System or Business Voice.

2. The user must have Enterprise Voice enabled. This is typically done in PowerShell using Set-CsUser.

3. The user must be "granted" a Voice Routing Policy.

The Phone system license will either be an add-on to our E3 license or will be apart of an E5 license.

If you are migrating from Skype for Business to Teams, Enterprise Voice should already be enabled.

You should have Voice Routing Policy set up for Teams and you will use the command Grant-CsOnlineVoiceRoutingPolicy -Identity -PolicyName "TeamsRoute".

248 views0 comments
  • Writer's picturesamanthaeasterday

Updated: Jul 13, 2021

#teamserror #teamsonly #tls1.0

In a past blog post, I talked about how our Polycom phones wouldn't sign in a new or difference user. After A LOT of troubleshooting, I found out tls 1.0 is getting blocked somewhere in our network, which is not allowing the phones to reach the ports they need.

Recently, I have been working on Direct Routing in Teams. I wanted to move myself to TeamsOnly (bye bye Skype) but received an error:

User is homed on-premises in a Skype for Business or Lync deployment. On-premises users can be upgraded to Teams using Move-CsUser in the on-premises tools. For details, see

I thought, okay, no problem, I'll do what they say and use PowerShell. BUT low and behold, I received the same error message. This told me a lot and helped me figure out, fairly quickly, what the command was looking for on the backend and helped me down my path of yet, another, tls 1.0 issue.

Rather than spending the next, however long, to continue my search of finding where it is getting blocked. I thought, why do I have to use tls 1.0? So I found a command to force PowerShell to use tls 1.2, so I can move my account to TeamsOnly and move on with my life!

Open PowerShell on your Skype server or install the modules (search for past blog post). And run these:

[Net.ServicePointManager]::SecurityProtocol =


move-csuser -identity -target -useoauth

You are now on TeamsOnly!

So, you might ask, but....what now?

Well, It's simple, I added the commands to my script for when I move more users to TeamsOnly for the pilot. But yes, yes...I will still work on where tls 1.0 is getting blocked, in my spare time ;)

  • Twitter
bottom of page