To get a sign-in code when Microsoft Authenticator is not working, use the correct account, product, permissions, and destination. This guide explains the supported workflow and the checks that confirm the result.
Protect a Working Sign-In Method Before You Start
Confirm the owning account, required permissions, affected files or services, and the exact outcome you need. Keep a backup when the task changes local content or removes access.
Quick Authentication Recovery Path
First, sign in to the entra.microsoft.com as at least Authentication Administrator. Next, select User -> All user, and verify the final state before changing any backup or secondary account.
How to Get a Sign-In Code When Microsoft Authenticator Is Not Working

- Sign in to the entra.microsoft.com as at least Authentication Administrator
- Select User -> All user
- Select the user (your account) to act on and select Authentication methods. then select Require re-register of multi-factor authentication
- Use the old iPhone to approve sign-ins or provide codes while adding the account to Authenticator on the new iPhone
- Ask a Global Admin to reset MFA for the account (Require re-register MFA / reset authentication methods) so MFA methods can be configured again on the new iPhone
- Contact Microsoft support by phone and request the Data Protection team to reset MFA for the tenant admin, following the guidance in the referenced threads
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
Which control should I check first to get a sign-in code when Microsoft Authenticator is not working?
Sign in to the entra.microsoft.com as at least Authentication Administrator. Then select User -> All user.
Should I keep another sign-in method while I get a sign-in code when Microsoft Authenticator is not working?
Select User -> All user. Before applying the change broadly, confirm the same condition in one representative account, file, cell, message, or device.
What is the safest next test if get a sign-in code when Microsoft Authenticator is not working does not work?
Select the user (your account) to act on and select Authentication methods. then select Require re-register of multi-factor authentication. Keep the original data or current account state until this test produces the expected result.
How do I verify the result after I get a sign-in code when Microsoft Authenticator is not working?
Contact Microsoft support by phone and request the Data Protection team to reset MFA for the tenant admin, following the guidance in the referenced threads. Reopen the affected app, file, or portal and confirm that the result remains in place.




