unable to reset MFA for one of my organization mailbox in Azure console. error Value of unique property 'ProxyAddresses' with ObjectId '28b36d98-etc...'

Musab Shareef (Admin) 0 Reputation points
2026-03-29T08:27:35.4733333+00:00

I can't delete previous registered device from user MFA profile.

also user not able to find any code in his Authenticator app or login by any other method!

reset MFA or deleting MFA method in Azure console not working

Microsoft Security | Microsoft Authenticator
0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-03-29T08:27:52.39+00:00

    The error about the unique property ProxyAddresses is unrelated to the actual MFA reset; focus on resetting the user’s MFA methods instead of changing the mailbox or proxy addresses.

    Given that:

    • The user cannot get codes from Microsoft Authenticator
    • No alternative sign-in method works
    • Resetting/deleting MFA methods in the Azure/Entra portal is failing

    Use one of the supported recovery paths below.

    1. Try a standard MFA re‑registration reset (if not already done)
    • In the Azure portal, go to Microsoft Entra ID → Users → [select the user] → Authentication methods.
    • Select Require re-register multifactor authentication.
    • Have the user sign in again; they should be prompted to set up MFA from scratch.
    • If this still fails or you cannot delete the existing methods, proceed to step 2.
    1. Delete the user’s Authenticator registrations via Microsoft Graph (admin required) If you are a Global Administrator and portal-based deletion is not working, delete the Microsoft Authenticator methods directly using Microsoft Graph:
    2. Go to Graph Explorer and sign in as a Global Administrator.
    3. In the query area:
      • Set HTTP method to GET.
      • Use this query (replace with the user’s UPN): https://graph.microsoft.com/beta/users/<user-principal-name>/authentication/microsoftAuthenticatorMethods
      • Run the query.
    4. If a permission error appears, in Modify permissions → Open the permissions panel, grant UserAuthenticationMethod.ReadWrite.All and Consent, then run the query again.
    5. In the response, copy the id (GUID) for each authenticator method.
    6. For each id, run a DELETE query:
      • Set HTTP method to DELETE.
      • Query: https://graph.microsoft.com/beta/users/<user-principal-name>/authentication/microsoftAuthenticatorMethods/<authenticator-id-guid>
      • Run the query and confirm a 204 No Content response.
    7. After all authenticator methods are deleted, have the user sign in again and complete MFA setup with a fresh Authenticator registration and/or an additional method (phone/SMS) so they are not locked out again.
    8. If there is no other Global Admin or Graph access fails If this user is the only Global Admin and you cannot perform the steps above, or all admin-side resets fail, the tenant’s MFA reset must be handled by Microsoft’s Data Protection / Tenant Recovery team via a support case or phone call, as shown in the referenced Q&A threads. A support engineer can verify tenant ownership and reset MFA from the backend.
    9. General guidance for the user’s Authenticator app
    • If the user sees no 6‑digit OTP and only push approvals, the account may be configured for passwordless or push-only; once the old registration is removed (via steps above), a new registration will restore proper codes/approvals.
    • Ensure the user keeps at least one additional MFA method (phone call/SMS) configured to avoid future lockouts.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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