Share via

Cannot re-add phone number as security method – option missing after removal (Case 7101286746)

Caroline S. Brooks 0 Reputation points
2026-04-15T14:53:11.3033333+00:00

Case 7101286746

My Microsoft account is in an inconsistent security configuration state.

I previously had a phone number set as a security method. After removing it, the option to re-add a phone number is no longer available in the account security settings.

This is not a recovery issue. I have full access via Microsoft Authenticator.

A support agent stated this is a “system-wide restriction,” but could not provide any documentation, and this behavior is inconsistent with expected account functionality.

I need this escalated to a team that can review account-level security configuration and perform a manual reset of security methods or remove any incorrect restriction.

Has anyone encountered this, and can a Microsoft moderator escalate this case?

Outlook | Web | Outlook.com | Account management, security, and privacy
0 comments No comments

2 answers

Sort by: Most helpful
  1. EmilyS726 228.8K Reputation points Independent Advisor
    2026-04-15T15:27:10.1433333+00:00

    For personal Microsoft accounts, Microsoft now says you can no longer add a phone number as a new security method. Their current support article states: “For increased security, you can no longer add a phone number” when adding a new way to verify sign-in.

    https://support.microsoft.com/en-us/account-billing/microsoft-account-security-info-verification-codes-bf2505ca-cae5-c5b4-77d1-69d3343a5452 (see section I highlighted)

    User's image

    That said, Microsoft still supports receiving security codes by text in general for accounts that already have phone verification set up, and their support pages still describe SMS verification and genuine Microsoft verification texts.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. Q&A Assist
    2026-04-15T14:53:24.1766667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The documented behavior for Microsoft account security info is:

    1. Security methods (phone/email) are managed from the Advanced security options page of the Microsoft account.
    2. Old security info does not need to be removed unless there is a security risk. If it is removed, new security info should be added first.
    3. If all security information is removed or a full replacement is requested, the account enters a 30‑day restricted state during which no changes or additions to security settings or billing information are allowed. The account remains usable, but security info cannot be modified during this period.

    From the available documentation, the supported self-service path is:

    1. Sign in to the Advanced security options page of the Microsoft account.
    2. Under the verification options, expand each method and use Remove only where necessary.
    3. Avoid removing all security info at once to prevent the 30‑day restriction.

    If all security info was removed or a full replacement was requested, the missing option to add a phone number can be explained by the 30‑day restriction window. During that time, Microsoft cannot accept further changes or additions to security settings, including re‑adding a phone number. After the 30‑day period completes, security info changes can be made again.

    The provided context does not include a documented mechanism for moderators or support to bypass or manually reset this restriction; it only states that the restriction exists to protect the account if security info was removed by someone with unauthorized access.

    For additional guided help with Microsoft account issues (including security info and aliases), the documented path is to use the Microsoft account guided tools referenced below.


    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.