Page tree
Skip to end of metadata
Go to start of metadata


In This Article


Overview

In this article you will be adding your unique Teams Direct Routing domains to your Office 365 tenant.  These routing domains are created and managed by Evolve IP.  Additionally, you will be creating a new user/service account for each of the routing domains. 

Here's an example of the routing domains and user/service accounts.  Do NOT add the below domains to your Office 365 tenant.  You will receive your own unique domains from Evolve IP.

LocationRouting DomainUser/Service Account UPN
Evolve IP Eastc1005437.phl01.us.teams.evolveip.neteip-tdr@c1005437.phl01.us.teams.evolveip.net
Evolve IP Westc1005437.las01.us.teams.evolveip.neteip-tdr@c1005437.las01.us.teams.evolveip.net

*Note: you will receive unique domains for your configuration from the Evolve IP delivery team. 

Adding a domain to your Office 365 tenant requires Global Administrator permissions.



Adding Your Domains

After Evolve IP has created your direct routing domains, perform the following steps to add each domain to your Office 365 tenant:

  • Sign into your Microsoft 365 Admin Center with a user account that's a Global Administrator.

  • In the left navigation pane, browse to:  Setup > Domains

  • In the main window, click the + Add Domain button.


  • Enter your Direct Routing domain, and click Next.


  • Copy the TXT Value and take a screenshot of the information as shown below.  The TXT Value needs to be added to your domain's DNS zone, which is done by Evolve IP.

  • Once the TXT value has been added to your DNS zone by Evolve IP, you can click the Verify button, which forces Microsoft to check for the DNS record.

  • If needed, click Save and Close to come back later.


  • After verifying the domain, click Next.
  • On the Update DNS Settings page, select I’ll add the DNS records myself and click Next.
  • Clear all values, click Next, and then click Finish.
  • Make sure the domain has a status of Setup Complete or Healthy.



Add the User/Service Account

For each routing domain added to your Office 365 tenant, you need to create a user/service account using the domain, and temporarily assign it an Office 365 license that includes MS Teams (e.g. Office 365 E1).

  • Sign into your Microsoft 365 Admin Center with a user account that at a minimum has the User Account Administrator role.
  • In the left navigation pane, browse to:  Users > Active Users
  • Click the button to Add a User

User/Service Account Details


 Expand for details on adding a user/service account in a US based configuration
ItemValue
First NameEvolve IP Teams
Last Name

Direct Routing - East
or
Direct Routing - West

Display NameEvolve IP Teams Direct Routing - East
or
Evolve IP Teams Direct Routing - West
Username (UPN)eip-tdr @ your.direct.routing.domain.net [pick either the east (phl01) or west (las01) from the drop-down menu]
Password
  • Select:  Let me create the password (create a complex 16-character alpha-numeric password with special characters)
  • Deselect:  Require this user to change their password when they first sign in

Notes:

  • You can document the password, or just reset it if ever needed.
  • There is no requirement to ever sign in with this account
  • After the back-end direct routing configuration is completed, you can disable the user account (block sign-in).
  • The user/service account should never be deleted.
LocationIf needed set the location to the United States.
LicensesSelect an Office 365 license that includes MS Teams (e.g. Office 365 E1)
RolesUser (no administration access)
Profile InfoNone, unless you have organizational requirements to add profile info.

spacer


 Expand for details on adding a user/service account in an EU based configuration
ItemValue
First NameEvolve IP Teams
Last Name

Direct Routing - NNpeer01
or
Direct Routing - NNpeer02

Display Name

Evolve IP Teams Direct Routing - NNpeer01
or

Evolve IP Teams Direct Routing - NNpeer02
Username (UPN)eip-tdr @ your.direct.routing.domain.net [pick either the NNpeer01 (AMS) or NNpeer02 (DFT) from the drop-down menu]
Password
  • Select:  Let me create the password (create a complex 16-character alpha-numeric password with special characters)
  • Deselect:  Require this user to change their password when they first sign in

Notes:

  • You can document the password, or just reset it if ever needed.
  • There is no requirement to ever sign in with this account
  • After the back-end direct routing configuration is completed, you can disable the user account (block sign-in).
  • The user/service account should never be deleted.
LocationIf needed set the location to your country.
LicensesSelect an Office 365 license that includes MS Teams (e.g. Office 365 E1)
RolesUser (no administration access)
Profile InfoNone, unless you have organizational requirements to add profile info.


Verify the User/Service Account

After creating the user account, wait 10-15 minutes and then sign into the Skype for Business Online service using PowerShell. 

Run the below command to verify the user account is enabled for MS Teams:

Get-CsOnlineUser eip-tdr@your.direct.routing.domain.net | FL DisplayName, SipAddress, Enabled, TeamsUpgrade*
  • A SIP Address should be present and include the domain.
  • Enabled should equal True, which means the account is licensed for Teams.
  • The Teams Upgrade Effective Mode should equal TeamsOnly

Example Output

DisplayName                      : Evolve IP Teams Direct Routing East
SipAddress : sip:eip-tdr@c1002345.phl01.us.teams.evolveip.net
Enabled : True
TeamsUpgradeEffectiveMode : TeamsOnly
TeamsUpgradeNotificationsEnabled : False
TeamsUpgradePolicyIsReadOnly : None
TeamsUpgradePolicy : UpgradeToTeams
TeamsUpgradeOverridePolicy :


If the Teams Upgrade Effective Mode is not set to TeamsOnly, run the following PowerShell command:

Grant-CsTeamsUpgradePolicy -Identity eip-tdr@your.direct.routing.domain.net -PolicyName UpgradeToTeams

Note: Due to the amount of load on Microsoft's Teams environment, provisioning and changes to the account may take hours to complete.



Next Steps

We recommend that you wait about an hour before continuing to the next step.  This allows Microsoft's back-end services to fully sync up with the new routing domains.