This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 15%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECC%3C/text%3E%3C/svg%3E)
It looks like the "old UI experience" was finally deprecated, but the new Authentication Methods UI experience no longer shows an MFA phone number. The example user below has MFA registered via a B2C custom policy (basically straight out of the starter pack, where strongAuthenticationPhoneNumber is the claim being written):
I have a number of existing users with MFA phone numbers registered this way, and now it is impossible for me to see if any given user has actually registered a phone number, and if they have, what that phone number is.
The only semi-workaround to this is that manually adding an authentication method via Azure Portal will get it to appear, and subsequent updates through a B2C profile-editing custom policy seems to update the method appropriately. The problem is that I cannot seem to access any existing user's phone numbers to script out a blanket update to add Authentication Methods, and it seems as though any new user signups would also suffer from this issue (e.g. when first registering a phone number it will inevitably be written to the "wrong" location within B2C).
PS: this is tagged as Entra ID since apparently there is no tag for B2C.
Hi @Christopher Crook , did you need any more help with this question? If not could you please mark "Accept Answer" on the appropriate answer so other users can reference it?
Thank you,
James
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 81%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENR%3C/text%3E%3C/svg%3E)
Hello, can we put some priority on this? None of the workarounds mentioned help at all - we need the ability to update this phone number for our current login flow.
Hi @Christopher Crook , unfortunately this is a bug that we're currently working on. More information here.
"This is currently being reported as a bug and we have a patch has been released. However, some users like yourself are still experiencing the issue.
The current proposed workaround is to go into Azure Portal and click "Enable" under the Authentication methods menu manually for each user."
I'm sorry that this isn't the answer you're looking for, but we're actively working on a fix. I'll share updates with you as I receive them. Please let me know if you have any questions in the meantime.
Best,
James
@James Hamil that's not a particularly great work-around considering I have >10k users.
The bigger problem is: your suggestion to "click "Enable" under the Authentication methods menu manually for each user" also does not appear to be a thing:
Did you mean "Add authentication method" at the top? Because that requires me to know each user's phone number, which I currently can't get to for those who have registered one already even.
This seems like a pretty massive oversight from the B2C dev team. Is there any way we could just get back the "old" UI in the time being until this is resolved? Or ideally, just tell us what claims need to be written in a custom policy in order to get auth methods to appear in the new UI? Is it as simple as another poster suggested where it just isn't being recognized in the new UI because of a lack of a space character between the country code and phone number?
Semi-related: it looks like the "not helpful" feedback button is also broken on this site:
Seems like a lot of stuff is just falling apart at MSFT currently.
Hi @Christopher Crook , I'm sorry about this. I'm going to bring these issues to the attention of our leadership and try to get some answers, and preferably fixes, to you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
Hi James,
I'm just as confused as Christopher here - I don't see the "Enable" button you mentioned - perhaps a screenshot would be helpful.
This has been an issue since early December for us. I don't see this issue officially acknowledged anywhere in the service health section either - and having to read on forums shouldn't be how paying users learn about this. Is there a timeline yet or what the root cause for this was?
Hi Christopher - I'm in the same boat as you but was able to get a timeline for a fix by raising a ticket. I was told that a fix for this is in their test branches and "the Estimated time given for the rollout is currently end of January". Obviously not great, but better than nothing. I encourage you to reach out to Azure support too if you pay for a support plan if you haven't already.
That got cut off. Obviously, this isn't fast but it's good to have a rough idea. I encourage you to reach out to support in Azure if you pay for any of the support plans to get a better idea too.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hi all, wanted to follow up with you. The product team is still working on a fix, but as Divyjot mentioned it will take some time. We really appreciate your patience.
Best,
James