Unified Communication Techies

In my personal experience even you Move users ( Move-CsUser)  it doesnt mean it will be all activate in the Microsoft Teams backend. It will take time to replicate microservices and sometimes it goes up to 24hrs.  Following 4 items are important   - Phone system license attached with the user  - SfB Online Plan 2 License   - EnterpriseVoiceEnabled   - Hosting provider change to sipfed.online.lync.com    - CsOnlineVoicePolicy is assigned to the user or calling plan         How to check this using PowerShell,  Connect to Teams using PowerShell and  Get-CsOnlineUser -identity <mailaddress@abc.com> | ft *LineUri, HostingProvider,  EnterpriseVoiceEnabled In my personal experience make sure above items are in checked.  and addition to above items you can check this tool too -  Dial pad in missing in Teams - Microsoft Teams | Microsoft Docs  

I had very interesting experience recently related to user migration from Skype for business to Teams direct routing.  Most common issue is to missing dial pad would be following,  - Teams license assigned or assigned license change not replicate on time or delay.     License was PhoneSystem since this was Direct Routing work.  - is enable for Enter prise voice - Whether th e user assigned a  VoiceRoutingPolicy -  Whether th e user assigned a  TeamsCallingPolicy Addition to this i checked following,  -Homed location/HostingProvider of the users and whether user has been       migrated successful or not.  Get-CsOnline -Identity xxx@abc.com | fl DisplayName, LineUri, EnterpriseVoice*, HostingProvider This where the interesting part came in found a difference in another attribute which never had seen before.  Get-CsOnline -Identity xxx@abc.com | fl DisplayName, LineUri, EnterpriseVoice*, HostingProvider, ...