Applies To

Customers/Partners 


TABLE OF CONTENTS


Overview

You may run into a situation where after adding a user and doing a sync the phone number or DID number for the user will not populate into Teams Admin Center or the Teams user application.  Sometimes this is just having to wait on Microsoft to propogate the phone numbers.  If you have waited over 24 hours, then there may be another underlying issue.  


Explanation of Behaviour

Phone numbers or DID's will not populate on the Teams user Dial pad in the Teams application.  The phone number or DID number will not populate under the user in Teams Admin Center.  If you use the following powershell command: 

Get-CsPhoneNumberAssignment -Identity (user's email address placed here) and the number doesn't show.  There is a good chance you could have users assigned in Azure under a Security or Azure Groups.  This is very apparent if you are using Large Tenant Mode in the portal.  


Please note, if you not using Azure Groups or Security Groups then this article is not for the issue you are having.  This issue only applies if you are using Azure Groups or Security Groups.  Please refer to our other KB documents for phone numbers not populating or Dial Pad not populating. 


Solution

If you have users assigned in Azure Groups or Security Groups in Azure, and use those groups to assign the Microsoft Phone System License, then the Microsoft Phone System License will not work properly in assigning the phone number to the user.  The dial pad will show but the phone number or DID will not populate.  The user will not show "true" for EnterpriseVoice Enabled.  Currently Microsoft does not have a fix for this issue.  To get around this you will need to directly assign the Microsoft Phone System License to the user.  Once you have assigned the MS Phone System Licenses directly to the user then a new sync will need to be done.  It may require 2 syncs in order for the phone number to populate. 


Disclaimer

Please note Destiny Automate Ltd. (formerly Qunifi Limited) cannot be held responsible for the content of any third-party documentation offered.