Forum Discussion

manojviduranga's avatar
manojviduranga
MCT
Jan 24, 2022
Solved

Unable to assign a Teams Phone number to a brand new user account (Error: we can't save changes)

Hi folks,    I'm facing an issue where I can't assign a Teams phone number (Canadian number issued by Microsoft) to a newly provisioned user via UI or PowerShell. The user was provisioned couple of...
Administrator
calling
  • manojviduranga's avatar
    manojviduranga
    Jan 30, 2022
    Update ----------

    Apparently this had to be escalated to Microsoft support and then to the engineering team internally. After 2-3 days, the number got assigned from the backend. The rootcause is still unknown and I am waiting to hear back.

    Hope this will help someone out there one day.
manojviduranga's avatar
manojviduranga
MCT
Jan 30, 2022
Update ----------

Apparently this had to be escalated to Microsoft support and then to the engineering team internally. After 2-3 days, the number got assigned from the backend. The rootcause is still unknown and I am waiting to hear back.

Hope this will help someone out there one day.
AndyProsser's avatar
AndyProsser
Copper Contributor
Feb 22, 2022

manojviduranga I have a similar issue and even Microsoft Support were struggling with this one.

 

I think I’ve fixed it! Found a bigger hammer…though perhaps “older” is a better description.

After the Admin portal wasn’t working, I went back to PowerShell to delve deeper to gain some insights as to what might be going on.

 

First, I tried Set-CsPhoneNumberAssignment and the same “Bad Request, user not found”.

Then I decided to look at differences between working users and the one that does not work.

 

2 things jumped out.

 

Working:

OptionFlag                           : 131456

SipAddress                           : em***@*******.com.au 

SipProxyAddress                  : em***@******.com.au 

 

Not Working:

OptionFlag                           : 196864

SipAddress                           : al***@******.com.au 

SipProxyAddress                  : 1821529039******bfe68a0b190******cal***@******.com.au 

 

Using the Exchange Admin tool, I removed Al****’s SIP address, then added it again. This normalised the SIP address so both the SipAddress & SipProcyAddress matched.

 

It still did not work. I checked other users and they all had the same OptionFlag as Em*** (Working). I was stumped, but kept digging.

I stumbled across Adam Fowler’s post about the old PowerShell commands being deprecated and will be removed in April this year.
https://www.adamfowlerit.com/tag/microsoft-teams/

 

This gave me an idea…would the old commands work? Maybe they do things a little differently?

I gave it a go. Didn’t work to start with as I needed to find the correct Location Id….Get-CsOnlineLisLocation to the rescue.

 

Now with all the bits I needed, I ran Set-CsOnlineVoiceUser….

 

IT WORKED! No error. Quick check with Get-CsOnlineUser and yes the number is assigned. Checked the Teams Admin and it all looks like it stuck! Rang user, left a Voice Message on the new number. They just called back. 😃

 

Leaving this here incase it helps someone else.

Resources