Authentication methods not available at Graph API and UI

Question

Authentication methods not available at Graph API and UI

Aristotelis Papantonis 21

I have an issue with authentication methods on a B2C tenant and more specific with mobile.

While there is an entry on the mobile at the current Azure Portal UI of authentication methods, this entry is not available from GraphAPI (v.1 or beta) (I have available all the right permissions) and the new authentication experience and is not available to take.

Now the only way to have it available at GraphAPI (and new experience ) is to enable manually the indicator ( shown in the screenshot) to use the phone as a sign-in method which I do not want anyway because I want it only as MFA.

The more strange are although is beside I tried to turn it on the phone sign in the issue persists.

Also If I create the entry from Graph API also is available as it should be.

Can anyone know if I miss a configuration or is a bug?

Accepted answer

1 additional answer

Your answer

Answer 1

AmanpreetSingh-MSFT 56,871 Moderator

Hi @Aristotelis Papantonis • Thank you for reaching out.

This is a known issue with B2C. When you register for MFA via B2C user flow/custom policy, the strong authentication phone doesn't contain a space between country code and the actual phone number. If you add a space manually after the country code, graph call will return the expected result. The B2C Product group is already aware of this issue and working on it. However, there is no ETA as of now for the resolution.

This is documented here:

-----------------------------------------------------------------------------------------------------------

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Marko Ivanovski 0 Reputation points

2023-07-26T08:03:16.69+00:00

Hi @AmanpreetSingh-MSFT - we're running into this issue in 2023, has this really not been addressed by Microsoft in the last 2 years? Is there an ETA now?
AdamKozmic-7665 60 Reputation points

2023-08-24T19:03:15.6966667+00:00

I just tried this today, August 24th, 2023, almost 2 years later, and the issue is still present.

Also, the claims transformation that converts a phone number into a string does not add the space, so persisting the claim via a custom policy doesn't comply with the format. See: https://learn.microsoft.com/en-us/azure/active-directory-b2c/phone-number-claims-transformations#convertphonenumberclaimtostring

Answer 2

David Russell 46

Is there an API method to fetch strong authentication phonenumber?

The portal calls "users()?api-version=1.6-internal" which is inaccessible.

If not, then I don't see a way to migrate users from one B2C server to another automatically.

(We are migrating because our B2C server located in Australia is taking up to 9 seconds to respond to requests from Europe - far too slow. We're moving it to USA).

Kale, Yogesh 1 Reputation point

2022-08-23T12:52:22.217+00:00

https://learn.microsoft.com/en-us/graph/api/authentication-post-phonemethods?view=graph-rest-1.0&tabs=csharp
This should help
David Russell 46 Reputation points

2022-09-07T09:07:05.643+00:00

Thanks.

The documentation for the Get action says it's not available:

"This method is available only for standard Azure AD and B2B users, but not B2C users."

In the end I manually copied from Azure portal, and imported to new B2C server with powershell.

Share via

Authentication methods not available at Graph API and UI

1 additional answer

Your answer