A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
To stop repeated 2FA prompts and protect the account, follow these steps:
- Do not approve any unexpected prompts
- Deny all sign-in requests that are not initiated personally. This prevents an attacker from completing sign-in even if they know the password.
- Secure the account password
- Immediately change the password for the Microsoft account from a trusted device and network.
- Avoid reusing old passwords.
- Check for unusual activity and blocks
- Repeated prompts usually mean someone is repeatedly trying to sign in (possibly from another IP or location). Microsoft may temporarily block or challenge these attempts as “unusual activity,” which can trigger extra verification or blocks as described in the verification-code troubleshooting guidance.
- Reduce repeated verification attempts
- Avoid repeatedly requesting verification codes or sign-in attempts, as high volume can cause temporary blocks on verification methods.
- If a “Try another verification method” or similar block appears, use another verification method on the account if available (alternate email, SMS, etc.), or wait for the temporary block to clear before trying again.
- Strengthen sign-in methods
- Where possible, add and verify multiple secure sign-in methods (for example, Authenticator plus SMS or alternate email) so that access is not lost if one method fails.
- If sign-in or verification is blocked
- If messages such as “Try another verification method” appear and no alternative method is available, follow the guidance to:
- Try another network (switch between Wi‑Fi and mobile data).
- Wait at least 24 hours without repeated attempts if a temporary block is suspected.
- If messages such as “Try another verification method” appear and no alternative method is available, follow the guidance to:
- If still having trouble with Authenticator itself
- If Authenticator notifications are not working correctly (for example, expired notifications or no alerts), ensure:
- The device time is set to automatic and correct, then restart the device.
- Notifications are enabled for Authenticator and the device is not in Do Not Disturb/Quiet mode.
- If Authenticator notifications are not working correctly (for example, expired notifications or no alerts), ensure:
- Contact support if access cannot be restored
- If sign-in or verification issues continue and self-service options do not work, use the official support channels described in the verification-code troubleshooting article (Sign-in helper and Contact Microsoft Support). Support agents cannot send verification codes or change account details, but can guide through supported recovery paths.
For IP-level blocking of attackers, Microsoft’s automated protection systems evaluate sign-ins for unusual activity and may block or challenge risky attempts. Manual per-IP blocking for consumer accounts is not exposed in the Authenticator app; protection relies on strong credentials, MFA, and Microsoft’s risk-based controls.
References: