Make the Authentication Phone and Authentication Email field settable with Powershell.
Hi folks – apologies for the lack of updates here. This work is still in progress but unfortunately we don’t have an ETA that we can share yet. We will update as soon as we do. Thanks!
I did a test with the graphic tool , but it remains update user by user, is there a method like a batch that I can use in order to setup more than 1 user?
Niels Haaijer commented
Dougal Maguire commented
Total Carnage Folks
we plan to bring over 20k Users due to Corona online - Schools - pupils - can you imagine the mess and the struggle with not being able to control this setting? even if we precreate the user and validate their emails, we still can't make sure, that they use the same one for their o365 account - that is simply crazy
Liam Bramwell commented
We're migrating from on-prem MFA to Azure Cloud MFA and realised that whilst we can use Set-MsolUser to pass the StrongAuthenticationMethods, we still have to manually go down and backfill all user's phone numbers.
Dan Smith commented
We're coming up on 1 year since the last update from Microsoft.
Could we get some information about when this capability will be available?
Maciej Horbacz commented
I've bumped into same issue that my users had incorrect phones numbers in MFA.
This API would help a lot but due to lack of it I've manged to resolve this issue using Selenium with Powershell. It might come in handy folks:
Ron Houet commented
Hello Microsoft, are you listening at all to this uservoice? Almost 4 years and counting....
Please can you provide an update, preferably with some sort of timeline? In 4 months we'll be celebrating 4 years since it was originally requested!
Is there an update on this?
Ron Houet commented
I'm also setting it up for 16k+ users and facing this same problem for a community college.
Prepopulating mobilephone field is no option since it has to be hidden according GDPR and there is (also) no way of hiding it. And you don't want students calling teachers on their private phones and vice versa!
So setting Authentication Phone and Authentication Email field with Powershell is the only option. You wrote may 6 2019 that you would update soon... that's 8 months ago!
Mika Baljaskin commented
+1 from here also. 25k+ users have the necessary mobile phone info at place in AAD, only thing I would need is replicate MobilePhone to ($upn.StrongAuthenticationUserDetails) PhoneNumber. This is possible to do from GUI one user at a time, some automation would be greatly appreciated.
William Fiddes commented
Can we confirm that both will be available?
Also, any updates?
Volz, Gary commented
Where we at?
Andreas Klementsson commented
What is the status now? Any updates?
This is a must have for Enterprise Customers. Normally all fields are reachable/modifyable via powershell and/or graph. But in this case the fields can be modified via GUI one by one only. Very uncomfortable.
really needed for large companies
each user can setup is phone number but we want to modify for each user the alternativephonenumber with an IT support phone number
Azharuddin, Sheikh commented
any update about the feature implementation?
Richard Brooks commented
We want to use our desk phone at the office for MFA. In fact it works, if we use the original (not the new SSPR and MFA combined) method. In that case, the AD field "telephoneNumber" gets propogated to the Office 365 "Office phone" field in the user's contact information. However, in Azure Active Directory > Authentication Methods, there is no field that picks up this number. When I paste the number (+1 905-544-5439 x219) into the "Alternate phone" field I get an "Invalid phone number format" error. This needs to be fixed, or we can't use the combined SSPR/MFA experience. And I can't see the "Authentication phone" field that's being mentioned in this thread. Where is it?
Hi folks - apologies for the lack of updates here. This work is still in progress but unfortunately we don't have an ETA that we can share yet. We will update as soon as we do. Thanks!