30 day Security Info Replacement Not Working

The supported next action is to have Microsoft Support investigate the existing security-info replacement as a stuck pending change after its recorded completion time, rather than submitting the recovery form again or starting another replacement.

Continue the existing escalation

Reply to the existing support case and request these specific actions:

1. Keep the case open and assign one case owner. Avoid opening another recovery request or unrelated support case unless Microsoft closes the current one.
2. Describe the issue as a technical failure, not an identity-verification request:

   My personal Microsoft account’s security-info replacement remains pending after the exact 30-day completion date and the additional 48-hour delay provided by Support. The ACSR recovery form is unavailable because two-step verification is enabled. Please investigate the backend status of the pending security-info change and confirm whether it completed, failed, was cancelled, or restarted. I am not asking an agent to bypass MFA or manually change the account details.

3. Provide:
   • The existing case or escalation number.
   • The replacement request’s exact start and scheduled completion timestamps.
   • The confirmation and 15-day reminder messages.
   • A current screenshot of the pending-change or verification screen.
   • The address of the new security email, partially masked.
   • Dates of prior contacts and the promised 48-hour extension.
4. Ask for a written status and next update date, specifically whether the pending request is still active and what timestamp Microsoft’s system currently records.

The official process says that, after security information has been replaced, the wait is 30 days before sign-in with the new information becomes available.^1^ The published guidance does not document a general known outage or a normal 36-day processing period for this situation.

Limits of Support and the recovery form

The account recovery form is not a useful path to repeat in this case: with two-step verification enabled, Microsoft requires the configured verification proofs, and losing them can result in a 30-day recovery delay or loss of access.^2^

Support agents also cannot send verification codes, reset links, or directly access and change account details.^1^ Escalation therefore cannot legitimately bypass 2FA; its purpose is to investigate why the automated replacement did not transition at the scheduled time.

Since Support and the security team are already involved, use the official Contact Support flow only if the current case was closed or no longer accepts replies: select Get Help, then Contact Support, and reference the previous case.^1^

Avoid resetting the process

Until Microsoft confirms the state:

• Do not initiate another security-info replacement; it could create a new 30-day hold.
• Do not select Cancel removal or cancel the pending request.
• Avoid repeated verification-code requests. Microsoft states that excessive requests can trigger a temporary block.^1^
• If any device or browser remains signed in, do not sign out or clear its cookies. Use it only to preserve access; changing security information during an unresolved hold could affect the pending request.

Microsoft documents Cancel removal for intentionally reversing a scheduled deletion, not for repairing an overdue replacement.^3^

Reduce the impact while the case is investigated

For third-party services that send codes to the locked mailbox, contact each provider through its own recovery process and change the destination email where possible. Those providers cannot grant access to the Microsoft mailbox, but they may be able to verify ownership independently and detach their services from it.

After access is restored, add multiple independent verification methods, reinstall Authenticator on the new phone, generate and securely store a new recovery code, and avoid relying on the Microsoft mailbox itself as the sole recovery method for other critical accounts.

References

1. Troubleshoot Microsoft verification code issues | Microsoft Support
2. How to use two-step verification with your Microsoft account | Microsoft Support
3. What does 'Scheduled for removal' mean? | Microsoft Support