Disabling Voicemail will remove conflictions when using our PBX's Voicemail box. Once your users are setup, you can run the following Powershell Script to bulk remove the Voicemail Setting.
User(s) does not appear in list after Sync
The sync will identify users with Phone System license or E5 license and add them to the user list. If users are missing from the list, then check in Office 365 to ensure one of the required licenses is assigned.
Sync Failures
Sync information is available by viewing the dropdown arrow on the Sync button (on the Users tab) and selecting ‘View Sync History’.
- The Sync history logs show the various synchronization steps that have been applied to the Customer Office 365 tenant and the responses received back from the Office 365 system. It will also show error information if any errors have occurred.
- The most common reason for Sync errors is trying to operate a Sync function when logged in as a user without the correct permissions, or as a user logged in to a different Office 365 account when attempting to run the Sync function. This is most likely to occur when the service is being configured on behalf of a customer by an IT services operator, where the operator is not logged in with customer Admin user credentials.
- The changes made to the Office 365 platform by the Sync function can take several minutes to take effect especially in busy periods. This can mean that subsequent actions in a Sync job can fail as Office 365 is processing earlier steps. In these situations, the system is configured to safely allow a retry of the Sync function. The recommended action is to wait for at least 2 minutes and re-try the Sync function.
No Calls tab or Dial Pad in Teams
The Calls icon appears in the Microsoft Teams client when a user has the correct ‘phone system’
license and the configuration is completed for the user to make calls. There are several reasons that can cause the calls icon to be absent:
- The user does not have a phone number applied in the Office 365 admin center
- The Sync Now action has not been performed since the user was added to the portal.
- The user does not have a phone system license
- Insufficient time has elapsed since the user set-up was performed
- Microsoft Office 365 has an internal error Checking and resolving the above issues
If a user is not switching to Voice Enabled, you can use the following PS Script to enable.
- $userCredential = Get-Credential
- $sfbSession = New-CsOnlineSession -Credential $userCredential
- Import-PSSession $sfbSession -AllowClobber
- Get-CsOnlineUser -Identity "[User Name]"
- Set-CsUser -Identity "[User Name]" -EnterpriseVoiceEnabled $True
The user does not have a Phone System license
To use calling in Teams, you should assign licenses to your users for features like Audio Conferencing and Phone System. This Microsoft article explains how to add these licenses in bulk and for an individual user.
Note: the service configuration means you will be using on-premises PSTN connectivity for hybrid users, so you only need to assign a Phone System license. You should NOT assign a Calling Plan.
Some elements of the configuration within Microsoft Office 365 can be subject to delays of several hours as information propagates between different parts of the Microsoft system. This can vary from day to day, so we recommend that you aim to carry out the configuration at least 48 hours prior to your go-live date to allow for this
Microsoft Office 365 has an internal error
If all the above steps have not fixed the issue, then you may need to remove and re-apply the user’s
license with the following process:
1. Remove all O365 licenses from the user, wait 15 minutes, then add them back
2. Add the phone number back on the user. If the user is not shown in the Skype for Business legacy portal, then wait another 15 minutes and try again
3. Delete the user from the service portal and activate the Sync Now process to re-add them.
4. Quit Teams (right-click in the taskbar and choose ‘Quit’) and start it again
5. If still no dial pad then wait a while, quit and restart again. Sometimes this works straight away and sometimes it can take up to a day.
6. In some scenarios the removal of an unused calling plan or service may have left remnants of old configuration code behind. This must be raised with Microsoft with an explanation of the removed service, commenting on the missing Calls Tab or Dial Pad and the advice that you are adding Call2Teams third-party service.
Revoke access to the service in the Customer’s Office 365
Customers may have policy requirements meaning they need to revoke the access to the service that was granted during the setup process. Revoking access will not disrupt the service but will necessitate re-authentication should any changes be required using the Sync Now feature.
- To revoke access the customer admin should log into: https://portal.azure.com/
- When logged in, go to Azure Active Directory and then select Enterprise Applications

- Select the Call2Teams application and chose Delete. Access is now revoked for the service.
Access is now revoked for the service.