Microsoft Authenticator will not generate code

Bob Wiehl 0 Reputation points
2026-11-16T19:12:19.74+00:00

I transferred the Microsoft Authenticator app to my new phone and it will not work.

I have an MSP account on the app and need to use it to access a clients O365 account. I tried uninstalling and reinstalling the email address, but Authenticator will not generate a code for me to access my clients Office365 portal.

Can you please help?

Thanks - Bob

Microsoft Security | Microsoft Authenticator
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-16T19:13:02.1933333+00:00

    Re-register Microsoft Authenticator on the new phone; transferring or reinstalling the app restores only the name of a work account, not its MFA credential or code generator.^1^

    Re-register the account

    Because removing and reinstalling the account in the app did not work, update its server-side authentication registration:

    1. At the Microsoft 365 sign-in page, select Sign in another way and use any available alternative method, such as your old phone, SMS, or another registered method.
    2. Open Security info for the MSP work account.
    3. Select Add sign-in method → Microsoft Authenticator.
    4. On the new phone, open Authenticator and select:
      • +
      • Work or school account
      • Scan QR code
    5. Scan the QR code displayed in the browser and complete the test approval.
    6. Confirm that the new registration works before deleting the old Authenticator method.

    If Authenticator shows Action required or Sign in to restore your account, open that account entry and complete its sign-in and verification prompts. Work or school accounts must still be registered again after restoration.^1^

    If the client account is a guest account

    An MSP identity accessing a client’s Microsoft 365 tenant is commonly represented there as a B2B guest. MFA can be performed in the client’s resource tenant, so registering the new phone only in the MSP/home tenant might not repair the client registration.^2^

    Try opening Security info while signing into the affected client organization and register Authenticator there. If the client has configured cross-tenant trust for your home tenant’s MFA, the home registration can be accepted instead; otherwise, a separate client-tenant registration may be required.^3^

    If no alternative sign-in method is available

    Ask an administrator in the client’s tenant to reset the MFA registration for your guest user:

    1. Sign in to the Microsoft Entra admin center as at least an Authentication Administrator.
    2. Go to Entra ID → Users.
    3. Select the MSP guest user.
    4. Select Authentication methods.
    5. Select Require re-register MFA.
    6. Sign in again and register the new phone when prompted.

    This operation removes the existing Authenticator, phone, and software OATH methods and requires MFA setup again.^4^

    If the failure also affects the MSP account in its own organization, an Authentication Administrator in the MSP/home tenant must perform the same reset there. Reset only the affected tenant registration; a client administrator cannot reset the authentication record held by the MSP’s home tenant.


    References

    1. Restore one-time password codes in Microsoft Authenticator | Microsoft Support
    2. Authentication and Conditional Access for External ID
    3. Tutorial: Enforce multifactor authentication for B2B guest users
    4. Manage user authentication methods for Microsoft Entra multifactor authentication
    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.