Fix Microsoft Authenticator Listed as a Non-Usable Authentication Method
Question details
The user needs to resolve an issue where Microsoft Authenticator is stuck as a non-usable authentication method, blocking Single Sign-On (SSO) with error code 50072.
- Product
- Microsoft Entra ID / Microsoft Authenticator
- Device & OS
- not provided
- Scenario
- A user is trying to sign in using Single Sign-On but fails because the system requires MFA enrollment due to a configuration or location change, yet the app provides no prompts.
- Observed behavior
- The Microsoft Authenticator app is listed under non-usable authentication methods. Sign-in audits show interrupted requests with error code 50072, and removing or reinstalling the app does not restore functionality.
Before troubleshooting, ensure you have Global Administrator or Authentication Administrator privileges in your Microsoft Entra ID tenant to review user sign-in logs and modify MFA settings.
Require Re-registration and Revoke Sessions in Entra ID
Forcing a re-registration clears corrupted MFA states and prompts the user to set up their Authenticator app freshly.
Simply uninstalling the app on the user's mobile device is often insufficient because the corrupted authentication state remains active in the Entra ID backend. Revoking sessions and requiring a fresh setup ensures a clean synchronization.
Sign in to the Microsoft Entra admin center as an Authentication Administrator and navigate to Identity > Users > All users.
Search for and click on the specific user profile experiencing error code 50072.
Click on 'Revoke sessions' in the top menu bar to clear any active, interrupted, or stuck sign-in tokens.
Navigate to the 'Authentication methods' blade for the user in the left menu and select 'Require re-register MFA'. This forces the user to set up a new usable authentication method upon their next login.
Temporarily Change the User's Primary MFA Method
Use this as an approved temporary workaround if the Authenticator app continues to fail, allowing the user to bypass the non-usable method block.
Escalate to the Microsoft Support Community
If standard resets fail, the issue might require deeper backend investigation or product-specific guidance from Microsoft.
Experience Hassle-Free Productivity with WPS Office
While resolving Microsoft Entra ID and identity authentication issues can be complex, your daily document workflow shouldn't be. If you're looking for a highly compatible, free, and robust alternative to Microsoft Office, WPS Office provides a lightweight and unified workspace.
Frequently Asked Questions
What does Microsoft Entra error code 50072 mean?
Error code 50072 indicates that a user must enroll in multifactor authentication to access the application. This is typically triggered by an administrative configuration change, such as applying new Conditional Access policies, or when a user signs in from a completely new location.
Why is my Microsoft Authenticator showing as a non-usable authentication method?
This status occurs when the authentication registration state in Microsoft Entra ID becomes corrupted, falls out of sync with the user's mobile device, or fails to meet newly implemented security policy requirements for the tenant.
Does removing and reinstalling the Authenticator app fix the non-usable method issue?
Not consistently. Reinstalling the app only clears local device data. If the Microsoft Entra ID backend still holds a stuck session or a corrupted registration state, administrators must manually execute the 'Require re-register MFA' command and revoke active sessions for the fix to work.
Is it safe to disable MFA to bypass the 50072 error?
Disabling MFA completely is not recommended as it compromises account security. It should only be used as a last-resort, temporary workaround if approved by your security policies. It is vastly safer to issue a Temporary Access Pass (TAP) or switch the user's authentication method to SMS/Phone while investigating the app issue.
