Who this guide is for
This guide is for the account owner who started removing every security verification method from a Microsoft account and now wants to undo that request. You still control the old proofs — the phone, email address or authenticator you are removing — and you want to stop the change before it completes.
It is not a guide for reporting a security change you did not make. If someone else appears to be altering your account, the task is different: you are responding to an unauthorized change, not reversing your own request. The steps below assume the request is yours.
The direct answer
A pending removal of all Microsoft account security verification methods may be cancelled from the Security info change is still pending window.
A pending removal of all Microsoft account security verification methods may be cancelled from the Security info change is still pending window. Source
That window is the place to act. The owner uses cancel this request, and needs access to the existing security proofs to complete the cancellation.
The owner uses cancel this request and needs access to the existing security proofs to complete cancellation. Source
Timing matters. When all security information is removed, the restricted period is 30 days; it cannot be accelerated without cancelling the request.
When all security information is removed, the restricted period is 30 days; it cannot be accelerated without cancelling the request. Source
In plain terms: cancel first, then decide what to replace. Do not wait for the removal to finish and then try to shorten the restricted period — the approved facts do not describe a way to do that.
Before you start: a short checklist
| Check | Why it matters |
|---|---|
| The request is one you started | This guide covers undoing your own change, not responding to someone else’s |
| You still control at least one existing security proof | Cancellation needs access to the existing proofs |
| You can reach the Security info change is still pending window | That is where the cancel option sits |
| You have not yet lost access to every proof | Once all security information is removed, the 30-day restricted period applies |
If any row fails, stop and treat the situation as a different task. In particular, if you no longer control the proofs being removed, the approved facts do not establish that you can cancel the request yourself, so do not assume the steps above will work.
Step-by-step: cancelling your own pending removal
- Confirm the request is yours. Recall when you asked to remove all security verification methods. If you did not make that request, this is not the right procedure.
- Check that you still hold the old proofs. Cancellation requires access to the existing security proofs. Have the device, email inbox or authenticator you are removing available.
- Open the Security info change is still pending window. This is the surface named in the approved facts where a pending removal can be cancelled. The approved facts do not describe its exact menu path, so navigate to your account’s security info area and look for the pending-change notice rather than relying on a memorised label.
- Choose cancel this request. This is the action the owner uses to stop the pending removal.
- Complete the cancellation using the existing proof. When prompted, verify with the security proof you still control. The approved facts state that this access is needed; they do not describe alternative verification routes.
- Confirm the pending state has changed. See the verification section below.
Common failure paths
- You no longer control the proof being removed. Cancellation needs access to the existing security proofs. If that access is gone, the approved facts do not establish a self-service route, so do not keep retrying the same steps as if they will work.
- The removal has already completed. Once all security information is removed, the 30-day restricted period applies and cannot be accelerated without cancelling the request. If you are already in that period, the approved facts do not describe a way to shorten it.
- You are responding to someone else’s change. That is a separate task. This guide’s steps assume the request originated with you, and applying them to an unauthorized change may not address the actual problem.
- You are unsure whether the request is still pending. The approved facts describe cancellation from the pending window; they do not describe what a completed removal looks like in the interface, so verify the state before assuming either outcome.
What this guide cannot tell you
The approved facts are narrow. They do not establish:
- the exact menu labels, page layout or navigation path to the pending window;
- how long a cancellation takes to process, or any delivery deadline for confirmation;
- what happens to a cancellation attempt that fails verification;
- any recovery route once the restricted period has begun;
- whether the same steps apply to other Microsoft products or to accounts managed by an organisation.
Where a detail is not covered, treat it as unknown rather than filling the gap with a guess. If you need those specifics, check the current interface and Microsoft’s own account documentation at the time you act.
Verifying the result
After you choose cancel this request and complete verification with an existing proof, check the pending-change notice again. The useful signal is whether the pending removal is still shown as pending. The approved facts do not describe a specific confirmation message, so do not rely on remembered wording; rely on the state of the request itself.
If the notice still shows a pending removal, do not assume the cancellation succeeded. Re-check that you completed verification with a proof you still control, and avoid removing any remaining proof in the meantime — that would move you toward the 30-day restricted period rather than away from it.
After cancelling: plan replacements before removing anything
The point of cancelling is to keep control while you decide what comes next. Once the pending removal is cancelled, treat replacement methods as a separate decision: add or confirm the proofs you intend to keep before requesting removal of the old ones. The approved facts do not describe which methods can be added or in what order, so plan this in the account’s security settings rather than from this guide.
A username scan is not part of this task. TraceSeek checks public handles across 3,000+ platforms, with a free first scan that takes 20-30 seconds and needs no registration or login. It cannot recover an account, reveal connected logins or change platform settings, and a public match is a lead rather than proof of ownership. If your wider concern is which accounts are tied to an email address, the relevant next reading is email account inventory — a different task from cancelling a pending security info removal.