Forum Discussion
User lost phone number
The most common causes I've seen for this error is that you had SfB at one point, and there are lingering AD attributes that were synced to Office365, so Teams thinks the account is in SfB.
Take a look at the object on-premises, the values you're looking for all start with msRTCSIP-*, so do this for your problem user:Get-ADUser <identity> -Properties * | Select msRTCSIP*
The ones I've found cause the most issues are msRCTSIP-HomeServer, msRTCSIP-OptionsFlags, msRTCSIP-PoolAddress, and msRTCSIP-PrimaryHomeServer. If you really don't have SfB, and you didn't properly decommission it, you can use a PowerShell script to clear the attributes for the user and let them sync to Office365.Set-ADUser <identity> -Clear @('msRTCSIP-HomeServer','......')
Just specify the fields you want to clear, and let the sync run. If you're really not using SfB or any of the fields, you could do the same for all users and all fields, once you've validated. In some customer environments, I leave the msRTCSIP-Line field alone and we let their provisioning software populate that field with their phone number which syncs to Teams, and provides the phone number automatically (with direct routing at least).
The most common causes I've seen for this error is that you had SfB at one point, and there are lingering AD attributes that were synced to Office365, so Teams thinks the account is in SfB.
Take a look at the object on-premises, the values you're looking for all start with msRTCSIP-*, so do this for your problem user:
Get-ADUser <identity> -Properties * | Select msRTCSIP*
The ones I've found cause the most issues are msRCTSIP-HomeServer, msRTCSIP-OptionsFlags, msRTCSIP-PoolAddress, and msRTCSIP-PrimaryHomeServer. If you really don't have SfB, and you didn't properly decommission it, you can use a PowerShell script to clear the attributes for the user and let them sync to Office365.
Set-ADUser <identity> -Clear @('msRTCSIP-HomeServer','......')
Just specify the fields you want to clear, and let the sync run. If you're really not using SfB or any of the fields, you could do the same for all users and all fields, once you've validated. In some customer environments, I leave the msRTCSIP-Line field alone and we let their provisioning software populate that field with their phone number which syncs to Teams, and provides the phone number automatically (with direct routing at least).