A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Since access is still available on the Windows PC through the passkey, the supported path is to use that signed-in session to add a new verification method, then remove the old one carefully.
- On the Microsoft account Security page, select Manage how I sign in.
- Select Add a new way to sign in or verify.
- Add Microsoft Authenticator on the new phone, or add another available method such as a recovery email if offered.
- Complete the verification prompt.
- After the new method works, remove the old Authenticator/security method that is no longer usable.
Important: do not change all security info at the same time. Microsoft warns that changing all security info can cause the account to be restricted for 30 days.
For the missing SMS and email codes, the documented causes match the symptoms described:
- Microsoft can temporarily block code delivery because of unusual activity.
- Excessive or repetitive requests can trigger a block or limit.
- There can be temporary delivery delays due to heavy compromised traffic from a region.
- For SMS, phones that block texts from unknown numbers, full message storage, or messaging app problems can prevent delivery.
- VOIP numbers cannot be used for sign-in or verification codes.
The supported actions are:
- Stop repeated attempts. Microsoft specifically says repeated requests can reset or prolong the block.
- Try another verification method already on the account.
- Try another network by switching between Wi‑Fi and mobile data, or use a different Wi‑Fi network.
- Wait longer than 24 hours if needed. Microsoft states that if there is no change after 24 hours, wait longer, up to 1 week.
- If SMS is involved, check whether the phone blocks unknown senders and whether the messaging inbox/app is functioning.
For re-registering Authenticator on the new phone specifically:
- If a push notification was expected but never appeared, Microsoft notes it may still be going to the old device where Authenticator was last active.
- If the old phone is unavailable, use a different verification method to complete setup.
- If Authenticator shows “Authentication did not complete”, check that the app is unlocked, notifications are enabled, the app is updated, the phone has internet access, and date/time are correct.
About the recovery code: the provided context does not define what the recovery code resets or when it should be used, so only the supported guidance applies here: if no listed verification methods are usable during sign-in, select I don't have any of these and follow the prompts to replace security info. If all security info must be replaced, Microsoft states there is a 30-day wait before sign-in is allowed with the new info.
Also, support agents are not allowed to send verification codes or change account details. If codes still do not arrive after trying another method/network and waiting, the next supported step is to use the sign-in helper or Contact Support.
References: