Teams dial pad missing due to RegistarPool Attribute

[Madushka Dias]

Not a question but thought this should share in the community with my blog post and recent finding.

Most common issues after moving/migrating users to Teams from SfB were few,
Teams license assigned or assigned license change not replicate on time or delay.

•    License was Phone System since this was Direct Routing work. 
  
•  is enable for Enterprise voice.
•  Whether the user assigned a Voice Routing Policy.
•  Whether the user assigned a Teams Calling Policy.
•  Registar Pool missing/ empty. 
  
  I found this new experience and read full article - Teams dial pad missing due to Registar Pool Attribute 
  I got help from my old friend (MS Premier support) to do the replication in Backend @Muninder PS
  
  Thanks 
  
  Reach out to me on Madushka Dias (@madushka) / Twitter or https://www.linkedin.com/in/madushkadias/. 

[#2]

We currently have an open ticket with Msft (35000526) and for the last 3 weeks we have been having to ask Msft to fix on the backend everytime we add a new user! They fail to share what the issue is and the fix! It is getting very frustrating that any new starters have to wait days until they get a dialpad which is not promoting a good induction to our business. 

If anyone has any more information please share. I'm certain this issue is wide spread and Msft are not sharing the fix on purpose. @Madushka Dias