unable to login to non federated azure account

Question

unable to login to non federated azure account

SWAMY Puneeth GSCIN GTO-MAR-CPL-VOY 0

Am unable to login to non federated azure account, its asking the one time code generating in mobile authenticator application , but actually i added the non federated azure account in my mobile authenticator application but not getting any code

Please advise how to fix this , i guess MFA has to reset

Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-05-25T16:21:35.2133333+00:00

Hello SWAMY Puneeth GSCIN GTO-MAR-CPL-VOY

Based on the details you’ve shared, this appears to be a tenant lockout scenario.

To resolve this, the recommended approach is to contact the Microsoft Data Protection team. You can reach them by calling Microsoft Customer Service using the phone numbers listed here: https://support.microsoft.com/en-us/topic/customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

If you have access to another tenant or subscription where you still have Global Administrator privileges, you may also raise a support request from there to get assistance in restoring access to the affected tenant.

For future reference and to help prevent tenant lockouts, please check: Preventing tenant lockouts - Microsoft Learn.

If neither option is possible, please don’t worry—let us know, we are happy to assist you further!
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-05-26T10:32:11.6566667+00:00

Hello SWAMY Puneeth GSCIN GTO-MAR-CPL-VOY

Following up to see if you were able to create the support ticket, otherwise please let us know, we are happy to assist you further!
Carolyne 1,151 Reputation points Microsoft Employee

2026-06-04T06:07:17.7466667+00:00

Typically if the Authenticator app isn't generating a one-time code for your non-federated Azure account, the account registration in the app is likely incomplete. I believe you can add it by scanning the QR code from https://aka.ms/mfasetup (https://aka.ms/mfasetup). If you can't sign in at all to reach that page, contact your tenant administrator to reset your MFA registration so you can re-enroll.

1 answer

Your answer

Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-05-25T16:21:35.2133333+00:00

Hello SWAMY Puneeth GSCIN GTO-MAR-CPL-VOY

Based on the details you’ve shared, this appears to be a tenant lockout scenario.

To resolve this, the recommended approach is to contact the Microsoft Data Protection team. You can reach them by calling Microsoft Customer Service using the phone numbers listed here: https://support.microsoft.com/en-us/topic/customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

If you have access to another tenant or subscription where you still have Global Administrator privileges, you may also raise a support request from there to get assistance in restoring access to the affected tenant.

For future reference and to help prevent tenant lockouts, please check: Preventing tenant lockouts - Microsoft Learn.

If neither option is possible, please don’t worry—let us know, we are happy to assist you further!
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-05-26T10:32:11.6566667+00:00

Hello SWAMY Puneeth GSCIN GTO-MAR-CPL-VOY

Following up to see if you were able to create the support ticket, otherwise please let us know, we are happy to assist you further!
Carolyne 1,151 Reputation points Microsoft Employee

2026-06-04T06:07:17.7466667+00:00

Typically if the Authenticator app isn't generating a one-time code for your non-federated Azure account, the account registration in the app is likely incomplete. I believe you can add it by scanning the QR code from https://aka.ms/mfasetup (https://aka.ms/mfasetup). If you can't sign in at all to reach that page, contact your tenant administrator to reset your MFA registration so you can re-enroll.

Answer 1

The mobile Authenticator app is not showing a code because the current MFA method for that account is likely configured as push notification (Approve/Deny) rather than a one-time password (OTP) code, or the registration is no longer valid. This must be fixed by resetting MFA for the user.

Use the following options depending on the tenant situation:

If there is another Global Administrator in the tenant
1. A Global Admin signs in to the Azure portal and opens Microsoft Entra ID.
2. Go to Users and select the affected user account.
3. Open Authentication methods.
4. Select Require re-register multifactor authentication.
5. Have the user sign in again; they will be prompted to set up MFA from scratch and can re-add the account in Microsoft Authenticator (and, if desired, enable OTP codes).
Guidance for this operation is in:
- "Require re-register MFA so that you can configure the MFA methods again" in the Manage user authentication options article referenced here: https://learn.microsoft.com/en-us/entra/identity/authentication/howto-mfa-userdevicesettings#manage-user-authentication-options
If there is no other Global Administrator and this user is the only Global Admin
1. Forum moderators and normal admins cannot bypass or reset MFA in this case.
2. Contact Microsoft Support and have a ticket raised to the Data Protection / Tenant Recovery team. They have specific tools and procedures to verify identity and reset MFA for a locked-out sole Global Admin.
3. Use the regional Customer service phone numbers - Microsoft Support page to find the hotline, then clearly state that this is a tenant lockout, that the caller is the only Global Admin, and that MFA needs to be reset.
This process is described in the Q&A threads where:
- The Data Protection team is engaged when the only Global Admin is locked out due to Authenticator issues.
- Support verifies ownership and then resets MFA registration so the admin can sign in and reconfigure the Authenticator app.
If the issue is that the app is configured but shows no OTP code at all
- For some enterprise accounts, the Microsoft Authenticator entry may only show Approve/Deny notifications and not a 6-digit OTP. In that case, the sign-in screen must be using the correct method (push notification) rather than expecting an OTP.
- If the portal explicitly asks for a 6-digit code but the app entry has no “One-time password code” line, the MFA registration is misaligned and must be reset using one of the two paths above (another Global Admin or Data Protection team).

Until MFA is reset and re-registered, sign-in will continue to fail if the requested factor (OTP code) does not exist in the app.

References: