Teams Number

IBN 4,336 Reputation points
2022-04-14T11:09:12.47+00:00

Hello Teams Community,

Please I need your help on this issue.

We have a user called Alex who was assigned a phone number +44207xxxx229 but it has changed to +44209xxxx913.

The issue is that the number for on our users has changed automatically, please see screenshot below:

193136-image.png

This was previously +44207xxxx229 and this same correct number is also on the user’s AD account.

We’d like to know why and how this number has changed automatically.

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,122 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. JimmyYang-MSFT 49,031 Reputation points Microsoft Vendor
    2022-04-15T06:53:32.673+00:00

    Hi @IBN

    I found you phone number type is direct routing. Could you check if you create the Number Translation Rules policy in your phone number?

    To get it , you could run the following command to get translation rules assigned to the SBC:

    Get-CsTeamsTranslationRule  
    

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



  2. JimmyYang-MSFT 49,031 Reputation points Microsoft Vendor
    2022-04-28T09:20:34.717+00:00

    Hi @IBN

    Sorry for misunderstand the translation rules meaning!

    Yes, you're right. I checked again and found your phone number has been changed in Teams admin center, not during call process.

    Based on my knowledge, If a user or resource account has a phone number set in Active Directory on-premises and synched into Microsoft 365, you can't use Set-CsPhoneNumberAssignment to set the phone number. You will have to clear the phone number from the on-premises Active Directory and let that change sync into Microsoft 365 first.

    0 comments No comments