Articles in this section

See more

How to integrate Microsoft Teams

Avatar
Nauman Qureshi
  • Updated

 

Introduction 

This guide will walk you through the configuration of Teams direct routing to integrate Teams with Cloudli Connect telephony service. Once the configuration is completed, you should be able to dial to the PSTN from teams and receive calls from the regular telephone network in teams.  

This guide will cover configuring your account or your client’s account if you are a Microsoft reseller. This guide is intended for technical users. As such, you must be comfortable with concepts such as DNS and PowerShell.  

Licenses Requirement 

The voice and phone system for teams requires either 

  • Microsoft 365 E5 plan  
  • Microsoft 365 Business Basic or Microsoft 365 Business Standard or Microsoft 365 Business Premium + the add on Teams Phone Standard license plan. 
    • Please note that the Teams Phone Standard license plan is only available through Microsoft partners, it may not be bought independently.
    • Please note you could have an important Microsoft discount on the Teams Phone Standard license plan if your business is considered as a nonprofit organization.

 

Office configuration – Domain configuration 

To be able to configure Teams, we will need to add your Cloudli Connect subdomain to Microsoft office domains. This will need to be performed for each customer domain that will be managed by the account.

  • Navigate to Cloudli Connect administrative portal

  • Log-in 

  • Once logged in, navigate to Telephony -> Devices and select Microsoft Teams
    Picture1.png
  • Click New on the top right New

Picture2.png

 

  • Make sure to input your domain used at Microsoft (most of the time, this domain will be your email. Ex: user@company.com, your domain in that case would be company.com)
  • Click save, and the SBC domain will be generated

Picture3.png

  • In the left menu, navigate to Settings -> Domains and select Add domain 
  • You should be greeted with the Add domain wizard
  • Enter the SBC domain (e.g., dxxxxxxx.teams.omnivigil.net) and click Use this domain

Picture4.png

  • On the next step, select “Add a TXT record to the domain’s DNS records”

Picture5.png

  • On the Verify your domain page, note down the given TXT value (you will need this for the next step)

Picture6.png

  • Navigate back to the Cloudli Connect Portal and click on the top right Activate Microsoft Teams domain. You will then need to input the TXT value provided by Microsoft in the last step and click create. This will add the TXT record to Cloudli Connect DNS records so that Microsoft can validate the domain.

Picture7.png

  • Go back to the Microsoft domain wizard and click “Verify” 
  • Note that this might take up to 2 hours for the DNS to propagate. In most cases however it is quite quick. 
  • Complete the Add domain wizard 

Office configuration – Users and licenses 

  • Navigate to Microsoft 365 admin center 
  • In the left menu go to Users -> Active users 
  • Ensure that your users have the correct licenses

Picture8.png

  • Create a temporary user using the new domain (dxxxxxxx.teams.omnivigil.net). For example: domainActivation@dxxxxxxx.teams.omnivigil.net.

    • In the left menu go to Users -> Active users 
    • Click New and enter any name 
    • Domain should be the newly created domain (dxxxxxxx.teams.omnivigil.net)
    • Add necessary licenses to the User
  • This user should only be removed once the configuration is completed.

*** Note that this user and the properly assigned licenses are required to activate the voice route, for both Manual and Automated Configuration.
Picture9.png

 

Teams configuration – Admin panel 

  • In the left menu, go to Voice -> Voice routing policies 
    • Click on Global (Org-wide default) 
    • Click Add / Remove PSTN usage records 
    • Add a new PSTN usage record 
      • Name does not matter but note it for future use in a PowerShell command 
    • Make sure that the new PSTN usage record is selected
    • Apply and save changes 

Picture10.png

  • In the left menu, go to Voice -> Dial plans 
    • Click on Global (Org-wide default) 
    • Add a new Normalization rule 
      • Name: Outbound (name does not really matter)
      • Advanced
        • If Condition: ^(.*)$ 
        • Then do this: $1 

Picture11.png

Creating a new Teams extensions 

Now that direct routing is established and that the users are configured in Teams, simply create new Teams extension in Cloudli Connect portal.

  • Navigate to the portal 
  • In the left menu go to Telephony -> Extensions -> Extensions 
    • Click New 
    • Select Extension

Picture12.png

  • Enter the desired Extension Number and User, then select Microsoft Teams: customername.teams.omnivigil.net

Picture13.png

  • Save 

Adding a Teams Extension to existing user

You can add an extension to an existing user simply by editing the extension itself.

  • Navigate to the portal 
  • In the left menu go to Telephony -> Extensions -> Extensions
    • Select the Extension/User you wish to add to Microsoft Teams and click edit.
    • Simply select Microsoft Teams and save

Picture14.png

 

Teams Manual Configuration (Optional)

If you wish to perform the operation manually, please follow our guide. (note that Powershell knowledge is required)

Manual Teams Integration

Teams configuration – Automated PowerShell Script

In order to facilitate the integration, we have created a powershell script to automate the configuration process.

To retrieve that script, navigate to Telephony -> Extensions -> Extensions

Picture15.png

Next, on the top right under Menu, select Microsoft Teams Provisioning

Picture16.png

Select the domain for which you want to generate the Teams configuration script (Note that the downloaded script will only function in the tenant for the selected domain)
Picture17.png

 

*** Before downloading the script ***

You must validate that the extensions are properly set in regard to your users email account.

Picture18.png

Once everything is confirmed, you may proceed and download the script.

 


*** Before running the script ***

There are 2 things we must do before running the script.

  1. We must enable the script itself to be executed.

 – Right click on the powershell script (TeamsConfiguration.ps1) and click on Properties

 – In the General tab, make sure to click “Unblock” at the bottom in the Security option

Picture19.png

 

*** Double check and make sure your activation user has been properly configured domain and licenses wise. License activation for user may take up to 5 minutes. Route creation errors will occur if licenses are not activated.

  1. We must set Execution Policy via Powershell

 – Open powershell with administrator rights

 – Enter the following line to enable remote sign in via powershell

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

You are now ready to execute the script.

 

Adding/Removing/Changing User Extensions

To Add/Remove or change any user configuration in regard to their extensions, you will simply have to make the modification in the Extensions tab in the Portal.

Once the changes are done, simply download the script again and run it.

*** Note ***

Any configuration that is not reflected on the Microsoft Teams Provisioning page will be overwritten by the script.

Make sure that if any manual configuration has been made in Microsoft, it is also reflected in the Microsoft Teams Provisioning page.

Final words 

Calling a configured extension should now route the calls to the user’s Team client, whether it’s a cellphone or desktop client. 

Each user that was configured using the SetCs-User command should now have access to the dial pad to dial the regular telephone network. They will however need to log out of all their device and then log back in. 

Picture20.png

Related articles