Microsoft 365 sign-in can fail when Microsoft Authenticator does not receive a verification code; the supported fix is app troubleshooting first, then business support escalation.
Authenticator in Microsoft 365
What the sign-in problem means
The reported issue is a Microsoft 365 account sign-in block at the authenticator prompt. The user is asked for app-based verification, but no code arrives in the Microsoft Authenticator mobile app, so the login cannot be completed.
- This is an account verification issue tied to Microsoft 365 sign-in, not a local document or desktop editor setting.
- The mechanism involved is the Microsoft Authenticator mobile app and its code delivery or approval flow.
- Removing or changing the authenticator requirement is not something a local Office-style app can do by itself because the control lives in Microsoft’s cloud account system.
What is supported and what is not
| Area | Supported from the source | Limitation |
|---|---|---|
| Mobile troubleshooting | Update the mobile device OS and reinstall Microsoft Authenticator. | This may not remove the MFA requirement if the account policy still enforces it. |
| Admin or backend review | Contact Microsoft 365 business support phone numbers by country or region. | Backend changes are handled by Microsoft support, not by a local productivity app. |
| Verification outcome | Successful sign-in after the app works again or support resolves the account-side issue. | the available product guidance does not provide a tenant admin menu path to disable MFA directly. |
Where to start before escalation
Install the latest mobile system version first because app delivery issues can come from outdated device software.
Remove and reinstall Microsoft Authenticator to refresh the app environment tied to the sign-in prompt.
Try the Microsoft 365 login once more and confirm whether the app now receives the expected verification step.
Verification is simple here: if the code or approval request appears in Microsoft Authenticator and the account signs in successfully, the issue was likely app-side. If the prompt still appears with no code delivery, the source points to backend assistance as the next supported route.
When Authenticator blocks Microsoft 365, the real fix is app-first, backend-second

For this Microsoft 365 sign-in issue, the source-backed path is clear: update the mobile OS, reinstall Microsoft Authenticator, and test again. If the code still does not arrive, use Microsoft 365 business support so the account’s backend verification setup can be reviewed properly.
Use WPS Office as a Free Microsoft Office Alternative
the available guidance identifies the most likely first cause as a Microsoft Authenticator app problem. It recommends two exact actions before anything else: update the mobile device to the latest operating system version and reinstall Microsoft Authenticator.
If that does not restore code delivery, the supported escalation path is Microsoft 365 business support through the Microsoft Learn page for support phone numbers by country or region: Find Microsoft 365 for business support phone numbers by country or region . Use the page to find the correct regional number, then ask for help investigating the account on the backend.
Supported entry point
- Web page: Microsoft Learn support contact page for Microsoft 365 business support phone numbers by country or region.
- Use the page search shortcut noted in the source to find your area quickly, then call the listed support number.
- Expected result: Microsoft’s Data Protection or support team can review the issue from the backend when the app-side checks do not solve it.
no documented behavior establishes the reported case-facing Microsoft 365 admin path, button, or field that removes the authenticator requirement directly. Because of that, this article does not invent a disable-MFA menu path. If the app update and reinstall do not work, backend support is the supported next step.
A practical note about WPS Office
WPS Office cannot remove Microsoft 365 authenticator requirements, repair tenant-side MFA, or change Microsoft cloud account settings. However, if you are blocked from Microsoft 365 temporarily and still need to work on compatible local DOCX, XLSX, PPTX, or PDF files, WPS Office is a free, lightweight option with a familiar ribbon-style UI, PDF tools, and WPS AI features for drafting, summarizing, and rewriting content. Compatibility is generally strong for common files, but advanced Microsoft-only cloud features, account controls, and some complex formatting or macros may not behave identically.
Common follow-up questions

Fix Microsoft Authenticator When No Code Appears in the App FAQs
What should I verify after updating the phone and reinstalling the app?
Try signing in to Microsoft 365 again and check whether the Microsoft Authenticator app now receives the code or approval prompt. Successful sign-in confirms the issue was likely app-side.
Where is the official support entry point if the authenticator code still does not arrive?
Use the Microsoft Learn page for Microsoft 365 business support phone numbers by country or region, then contact the appropriate regional support team for backend assistance.
Where is the supported Microsoft entry point for escalation?
Use the Microsoft Learn page for Microsoft 365 business support phone numbers by country or region. On that page, use Ctrl+F and search for your area name to find the correct support number.
Can I remove Microsoft Authenticator from Microsoft 365 sign-in by myself?
Not from the evidence provided here. The source only supports app troubleshooting and then Microsoft 365 business support for backend investigation, not a self-service removal path.




