A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
The 30-day security-information hold for a personal Microsoft account cannot be shortened; either let it finish, or cancel the pending change if you still have access to the old verification method. ^1^ ^2^
If you initiated the change and want to stop it
- Sign in to your Microsoft account’s Additional security page.
- Expand the verification method marked Scheduled for removal.
- Select Cancel removal.
- Complete verification with the existing phone, email, or Authenticator method when prompted.
The old method remains usable for verification until its scheduled removal date. Canceling is therefore practical only while you can still use an existing method. ^1^
If all security information was replaced
If you selected I don’t have any of these and replaced all verification information, the new information does not become active until the 30-day period ends. During that hold, security-sensitive settings can remain unavailable even though ordinary sign-in and services such as Outlook still work. Support cannot override or accelerate this automated period. ^2^
Continue using the account where it already works, avoid signing out of trusted devices unnecessarily, and wait until the date shown in the pending-change message. After that date:
- Sign in to the Microsoft account.
- Open Security and then Advanced security options.
- Confirm the new phone, email, or Authenticator method works.
- Add multiple backup methods. Microsoft recommends keeping three pieces of security information to reduce the risk of losing access again. ^3^
If you did not request this change
Treat it as a possible unauthorized account change:
- Open Additional security.
- Expand the pending method and select Cancel removal.
- Remove any verification methods you do not recognize.
- Change the account password and review the account’s security activity.
Microsoft specifically advises canceling an unrecognized removal and checking for newly added verification methods. ^1^
Do not repeatedly request verification codes while waiting; excessive requests can cause temporary code-delivery blocking. ^4^
References