Applies To

Call2Teams - Customers


Users will need to have numbers assigned to them so that Microsoft can identify the user.

These numbers may be DDI Numbers, Extension Numbers or Trunk Numbers.

Administrators may wish to amend the number that Microsoft uses to identify the user.

About Numbers

Following a Sync, the user details are pulled into Call2Teams from the Microsoft 365 Admin account. 

The user details include any number that has been previously linked to the user in the Microsoft 365 tenant account

It is possible that the number field may be blank when the user is made available to Call2Teams.

Assigning/Amending Numbers

Administrators can assign/set numbers for users from within the Call2Teams portal user settings. 

This is then written back to the Microsoft Tenant Account following a new and successful Sync.

Administrators can also amend the user details, including the number, directly on the Microsoft Tenant. 

Again, a successful Sync will update the user. (It may be necessary to remove the user and re-add them).

Assigning More Than One Number To A User

Users may be accustomed to having several DDI lines assigned to them, as offered by their PBX.

However, if there is no PBX present, and users are assigned DDIs directly from a SIP trunk service, then there is no 'system' that can provide multi-DDI-per-user functionality.

As the service relies on, in the most part, the features passed through to it from the customer's systems, the service cannot provide this in place of a PBX.

To achieve the desired result instead, customers should use multiple resource accounts in Teams that forward calls to the desired destination.

The Telephone Number Provided Is Not Valid

When entering phone numbers against a user, the error 'The telephone number provided is not valid' may be seen:

This occurs when the number should be in E.164 format so it can be mapped to MS Teams.

Try adding the correct Country Code to the front of the number:

e.g. +441235123465 

On the user setting, the number must always be in E.164 format as this is a constraint of mapping to MS Teams, which needs a user identity in the format: