To fix an Authenticator app code prompt loop, first identify the correct account, file, device, or service context. The steps below isolate the cause and apply a result you can verify.
Protect a Working Sign-In Method Before You Start
Start by confirming whether the symptom affects one file, one device, one account, or the service itself. That distinction determines whether the next action belongs in the desktop app, the web portal, or an administrator console.
Quick Authentication Recovery Path
First, open the Microsoft Authenticator app and make sure it is unlocked. Next, check notifications and silent mode, and verify the final state before changing any backup or secondary account.
Why This Can Happen
- The wrong personal, work, school, billing, or administrator account is selected
- A license, permission, connection, file rule, or local setting does not match the requested action
- Cached credentials or an incomplete synchronization or activation state hides the current server status
- The Microsoft service or application requires a more specific control than a generic restart
How to Fix an Authenticator App Code Prompt Loop

- Open the Microsoft Authenticator app and make sure it is unlocked
- Check notifications and silent mode
- Update the Authenticator app
- Verify network connectivity
- Check device date and time
- Ask them to review Microsoft Entra sign-in logs and, if needed, reset or re-register MFA for the account so the Authenticator app can be set up again
After the final step, reopen the affected app, portal, file, or account page and confirm the exact status or behavior described in the title.
WPS Office: A Free Alternative for Local Office Work

WPS Office cannot directly change Microsoft-side account, billing, subscription, activation, tenant, OneDrive service, or SharePoint permission state. Those changes must be completed in the appropriate Microsoft portal.
For local productivity, WPS Office is a free Microsoft Office-compatible alternative with Writer, Spreadsheets, Presentation, and PDF tools. It opens and saves major formats including DOCX, XLSX, PPTX, and PDF through a familiar, streamlined interface that supports a smooth everyday migration.
Test advanced macros, add-ins, external connections, sensitivity controls, and Microsoft-only cloud integrations on a copy before moving a critical workflow.
Practical Checks That Prevent a Repeat
- Record which account, app, and file owns the workflow
- Keep a verified backup before removing access, changing ownership, or replacing a local file
- Apply high-impact changes to one test item or user before expanding the scope
- Save confirmation numbers, dates, and screenshots of the final settings when they affect billing, security, or permissions
Frequently Asked Questions
Where should I start when I need to fix an Authenticator app code prompt loop?
Open the Microsoft Authenticator app and make sure it is unlocked. Then check notifications and silent mode.
Should I keep another sign-in method while I fix an Authenticator app code prompt loop?
Check notifications and silent mode. Before applying the change broadly, confirm the same condition in one representative account, file, cell, message, or device.
Why might fix an Authenticator app code prompt loop still fail after the first change?
Update the Authenticator app. Keep the original data or current account state until this test produces the expected result.
Which final check proves the steps to fix an Authenticator app code prompt loop worked?
Ask them to review Microsoft Entra sign-in logs and, if needed, reset or re-register MFA for the account so the Authenticator app can be set up again. Reopen the affected app, file, or portal and confirm that the result remains in place.




