Overview
Admin experience when he/she try to assign a number to an user, "No results were found"
1. Replication delay & License status
To address the delay in license assignment and replication from Microsoft, connecting to PowerShell is indeed a practical approach. Here’s a step-by-step guide to help you figure out the status of the license assignment:
- Check License Status,
- Open PowerShell: Start by opening PowerShell with administrative privileges,
Connect to Microsoft Teams: Use the
and try following,Connect-MicrosoftTeams
cmdlet to establish a connection to your Teams environment
- Wait for Replication: Keep in mind that after assigning a Microsoft Calling Plan to a user, it can take up to 24 hours before they’ll see the dial pad in their Teams client,
Get-csOnlineUser -Identity "madushkadias@deployskypeforbusiness.com" | fl
Output shows following and Provisioned plan missing, and so, my assumption become valid.
PreferredDataLocation :
PreferredLanguage :
ProvisionedPlan :
UsageLocation : US
UserDirSyncEnabled : True
after few hours following reflected,
ProvisionedPlan : {MCOMEETADD, MCOPSTN2, MCOEV}
Since we are using Teams calling, it is required to have the correct usage location matching the emergency address assigned. Try to assign the number again, assuming all is done with the license, but still, the Teams calling number cannot be assigned to the user. The next step was to try again via PowerShell command and the following was found:
Unfortunately above error doesn't show in the GUI, Modified this field on Azure AD and use PowerShell to assign the number and it was success.
3. After everything failed for you then only option will be opening a ticket with Microsoft.
Enjoy!