Issue with Authentication Methods – Phone Number Update Delay

Jordanaa Chong 0 Reputation points
2025-02-28T02:25:40.3533333+00:00

Hi,

I'm experiencing an issue with updating phone numbers under Azure B2C User → Authentication Methods → Add Phone Number.

Currently, our system calls the API to update a user’s mobile number in Authentication Methods. However, users need to check the Authentication Methods screen to confirm if the phone number has been updated.

Issues Observed:

  1. The Authentication Methods screen does not update for more than 30 minutes, even if we refresh it every 3–5 minutes.
  2. The screen only updates when performing F12 → "Empty Cache and Hard Refresh".
  3. If a user tries to manually add their phone number, they receive the error:
    • "Unable to add Phone Number - Mobile phone method is already registered for this account."
    1. Even after refreshing, the phone number still does not appear in the interface.

Could you help us understand why this delay is happening and how we can resolve it?

Thanks!

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
13,166 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
23,481 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Kancharla Saiteja 1,025 Reputation points Microsoft External Staff
    2025-02-28T06:15:54.46+00:00

    Hi @Jordanaa Chong ,

    Thank you for posting your query on Microsoft Q&A. I am Saiteja from Q&A will be assisting you with your query.

    Based on your query, I understand that you are unable to retrieve authentication details API calls and observed delayed update on authentication methods.

    1. Authentication Methods screen does not update at least 30 minutes: As you know, we have seen the recent update of MFA changing from legacy to new authentication methods. This delay might be happening due to the recent updates, and we have seen similar issues with other clients as well.
    2. Is your user unable to update the phone number, you can add a custom policy to make this happen using the following link.
    3. B2C does NOT store MFA phone numbers in a place exposed by MS Graph API i.e. authenticationMethods. B2C instead stores it in strongAuthentication which is a legacy property. This may also happen when you add the user MFA phone number using custom policies which does not return in MS Graph authentication phoneMethods call. This is observed as a known issue from Azure AD B2C.

    I hope this information is helpful. Please feel free to reach out if you have any further questions.

    If the answer is helpful, please click "Accept Answer" and kindly "upvote it". If you have extra questions about this answer, please click "Comment".

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.