Since the sudden growth of IM service demands issue with Teams\Skype Dial Pad Missing has become a common problem in the Microsoft 365 space. Here’s a quick checklist for you.
Check if user configuration and provisioning status
Firstly, always verify the deployment/environment (Pure Onine, SfB Hybrid, Direct Routing etc.)
After that, check licensing status of Phone Systems and Calling Plans
Finally, get the results of Get-CsOnlineUser from SfBO PowerShell look for MCO Validation Errors, Provisioning Timestamp & Counters.
MCOValidationError are cause by some common data issue :
Duplicate User Principal Name detected within the tenant.
SIP address already in use by another account within the tenant.
SIP address or LineURI not being in the correct format.
Common hybrid related DNS issues that could break federation for on-premise based tenant.
LastSyncTimeStamp (Timestamp of when the last Sync process completed)
LastProvisionTimeStamp (Timestamp of when the last Provisioning process completed)
LastPublishTimeStamp (Timestamp of when the last Publish process completed)
LastSubProvisionTimeStamp (Timestamp of when the last Sub-provisioning process completed)
ProvisioningStamp (A value in this field implies that a Provisioning step is outstanding)
SubProvisioningStamp (A value in this field implies that a Sub-provisioning step is outstanding)
PublishingStamp (A value in this field implies that a Publishing step is outstanding)
ProvisioningCounter tracks how many times a Provision process has been attempted. For instance, a value greater than 3-5 usually indicates a problem requiring Microsoft Support engagement.
SubProvisioningCounter tracks how many times a Sub-provision process has been attempted. For instance, a value greater than 3-5 usually indicates a problem requiring Microsoft Support engagement.
PublishingCounter tracks how many times a Publishing process has been attempted. For instance, a value greater than 3 usually indicates a problem requiring Microsoft Support engagement.
MCOValidationError (If a value is present, indicates that the provisioning system has detected an issue with the user data that needs to be addressed by tenant admin before provisioning can complete.)
SIPAddress and SIPProxyAddress (Helps verify that the SIP address and Proxy SIP Address are as desired, a core component before a user can sign-in).
Enabled – Verifies that the system believes the user is enabled for service.
RegistrarPool – the specific Skype for Business Online pool where the user resides. Consequently, user sign-in cannot happen if there is no RegistrarPool defined.
HostingProvider – Indicates where the user is homed. SRV: represents on-premise, on the other hand sipfed.online.lync.com indicates the user is homed online.
Isolate if the issue only exist to all user or only specific to a user. For example, the issue only happens to a group of user or the issue is service wide. Consequently, you will be able to rule out things and find a clearer path where the issue resides.
Do test calls to the affected users to see if they are able to receive calls. Meanwhile, capture the error prompt you will receive. Consequently, the output could lead you to a topic found in the internet or even a solution.
Check Teams and Skype Admin Center > Users
See if Phone System is set to “on” or if there is a phone number assigned to the user
Check also Teams and Skype Admin Center > Legacy Portal > Voice > Voice Users
Re-assign License (turn off Calling Plan and Phone System ONLY). In addition, leave it for hour and before re-assigning the license. In my experience, I will give 4 – 24 hours replication time before reproducing the issue.
Firstly, Go to Microsoft Teams Admin Center > Teams Apps > Setup Policies > Add > Add app setup Policy ( Put a description ) and then highlights everything ( Activity, Chat, Teams, Calendar, Calling and Files ) > SAVE.
After that, go to users > select the name of the affected account > Policies > Edit and set up everything to the policy that you’ve created > Apply.