Initial Configuration
This guide explains the steps required to configure Microsoft Teams for use with sipcall telephony services.
To use the Microsoft Teams phone system, you need the appropriate Microsoft 365 Business license or a Microsoft 365 Enterprise license, each with the "Microsoft 365 Phone Standard" add-on.
You will temporarily need one license and add-on for the one-time activation of the direct route (domain with voice route).
The Teams user’s name must not exceed 100 characters, otherwise calls cannot be delivered.
You can also find this guide as a video on our YouTube channel.
1. Order the Microsoft Teams Option
Before starting with this installation guide, the Teams option must first be ordered in the customer or partner portal, and the domain must be verified according to the ordering process.
2. Activate the Domain
2.1 Create User
Log in to the Microsoft 365 Admin Center and create a new user under "Users" → "Active users"
using the previously created sipcall domain. This user is used to activate the domain.
The user domainactivation@cu<yourCustomerNumber>.msteams1.sipcall.ch
is required temporarily and can be deleted after the initial configuration.
2.2 Add Microsoft Licenses
Assign an Enterprise or Business license to the user (Microsoft 365 E1 / E3 / E5 / Business Basic / Business Standard / Business Premium) as well as a Phone System license (Microsoft Teams Phone Standard), and complete the setup by clicking "Finish".
Alternatively, you can temporarily remove the license and add-on from another user and assign them to the domain activation user.
Wait at least 1 hour before proceeding to the next step.
Depending on Microsoft’s load, this may take longer. If it takes more than an hour,
a yellow highlighted message will appear above the location.
3. Configure Teams Phone System using PowerShell
- To perform the configuration, you need Windows PowerShell and the "Microsoft Teams" PowerShell module.
- PowerShell must be run with administrator privileges to install the module.
Notes on the "MicrosoftTeams" PowerShell Module
The Microsoft Teams PowerShell module MicrosoftTeams 7.1.0 was successfully tested by us.
Additional Information:
Our guide explains how to install the "MicrosoftTeams" PowerShell module on Windows.
If you do not want to perform the configuration with Microsoft Windows, the installation differs slightly:
3.1 Preparation
3.1.1 Install the "Microsoft Teams" module
-
Open PowerShell as administrator.
-
Install or update the Microsoft Teams module with the following command:
Set-ExecutionPolicy RemoteSigned -Force
Install-Module MicrosoftTeams -RequiredVersion 7.1.0 -AllowClobber
- Finish PowerShell after installing the module.
3.2 Configuration
3.2.1 Start session
- Reopen PowerShell (PowerShell as administrator does not need)
- Import the Team PowerShell module
Import-Module MicrosoftTeams
- To start working with the Microsoft Teams PowerShell module, type the following command:
Connect-MicrosoftTeams
- The following is a pop-up for Microsoft 365 authentication. Your user must be assigned the Microsoft role "Global Administrator" or "Team Administrator".
3.2.2 Assign phone number
Assign the desired sipcall number to any existing Microsoft 365 user or team resources account with the following command to:
Set-CsPhoneNumberAssignment -identity "yourusername@yourcompany.com" -PhoneNumber "+<sipcallPhoneNumber>" -PhoneNumberType DirectRouting
Example with 3 users and a "Team Resources Account" (for team telephone auto attendant):
Set-CsPhoneNumberAssignment -identity "homer.simpson@thesimpsons.ch" -PhoneNumber "+41441234001" -PhoneNumberType DirectRouting
Set-CsPhoneNumberAssignment -identity "marge.simpson@thesimpsons.ch" -PhoneNumber "+41441234002" -PhoneNumberType DirectRouting
Set-CsPhoneNumberAssignment -identity "bart.simpson@thesimpsons.ch" -PhoneNumber "+41441234003" -PhoneNumberType DirectRouting
Set-CsPhoneNumberAssignment -identity "mainnumber@thesimpsons.ch" -PhoneNumber "+41441234000" -PhoneNumberType DirectRouting
3.2.3 Create PstnUsage
Set-CsOnlinePstnUsage -Identity Global -Usage @{add="sipcall"}
3.2.4 Create Voice Route
Create a voice route and replace cu_____.msteams1.sipcall.ch
with the SBC domain from your order:
New-CsOnlineVoiceRoute -Identity "sipcall" -NumberPattern ".*" -OnlinePstnGatewayList "cu_____.msteams1.sipcall.ch" -Priority 1 -OnlinePstnUsages "sipcall"
Wait at least 10 minutes before proceeding to the next step.
3.2.5 Create policy
Create the policy for the voice route:
New-CsOnlineVoiceRoutingPolicy "sipcall" -OnlinePstnUsages "sipcall"
Wait at least 10 minutes before proceeding to the next step.
3.2.6 Assign policy to user
You can assign the policy individually or for several users as a batch:
- Assign variant individually
- Assign batch variant
Grant a user permission for the policy:
Grant-CsOnlineVoiceRoutingPolicy -Identity "yourusername@yourcompany.com" -PolicyName "sipcall"
Example:
Grant-CsOnlineVoiceRoutingPolicy -Identity "homer.simpson@thesimpsons.ch" -PolicyName "sipcall"
Grant-CsOnlineVoiceRoutingPolicy -Identity "marge.simpson@thesimpsons.ch" -PolicyName "sipcall"
Grant-CsOnlineVoiceRoutingPolicy -Identity "bart.simpson@thesimpsons.ch" -PolicyName "sipcall"
Grant-CsOnlineVoiceRoutingPolicy -Identity "mainnumber@thesimpsons.ch" -PolicyName "sipcall"
Replace yourusername1@yourcompany.com
, yourusername2@yourcompany.com
with your users and add more if needed.
$users_ids = @("yourusername1@yourcompany.com","yourusername2@yourcompany.com")
New-CsBatchPolicyAssignmentOperation -PolicyType OnlineVoiceRoutingPolicy -PolicyName "sipcall" -Identity $users_ids -OperationName "Batch assign voice routing"
Example:
$users_ids = @("homer.simpson@thesimpsons.ch","marge.simpson@thesimpsons.ch","bart.simpson@thesimpsons.ch","mainnumber@thesimpsons.ch")
New-CsBatchPolicyAssignmentOperation -PolicyType OnlineVoiceRoutingPolicy -PolicyName "sipcall" -Identity $users_ids -OperationName "20240418 batch ticket aaa-bb-123"
3.2.7 Verification
Afterward, test according to the Check Configuration article.
After successful verification, you can release the license and the "Phone Standard" add-on of the domainactivation
user and delete the user if needed.
3.2.8 End session
End the PowerShell session:
Disconnect-MicrosoftTeams
Allow Microsoft some time after completing the configuration.
It may take up to 1 hour for the configuration to take full effect.
Further Resources
For additional product information, downloads, and support, visit the manufacturer's website: