Microsoft Account Without a Phone Number (2026)
If you are trying to set up a Microsoft account without a phone number, you are in an unusual position compared with most signups: Microsoft is actively moving away from phone numbers, not toward them. The signup form at signup.live.com will verify you by email, and as of mid-2026 Microsoft's own support documentation says that for personal accounts you may no longer be able to add a phone number as a sign-in method at all.
That is the good news, and it is genuinely different from the situation with Apple, PayPal or Coinbase. The complication is that "Microsoft account" covers a lot of ground, and a handful of specific flows still demand an SMS code — and in those flows Microsoft explicitly refuses VoIP numbers. This guide separates the two cases so you know which one you are in.
The short answer on a Microsoft account without a phone number
For an ordinary personal account — an Outlook.com or Hotmail address you want for email, Windows sign-in, Xbox or Office — you do not need a phone number. The current signup flow asks for an email address, a password, your name and date of birth, then verifies you with a code sent to email, followed by a CAPTCHA. No phone field appears.
Where people run into the phone wall is further along: Azure and certain paid trials run a separate identity check that does require SMS, and an account flagged for "unusual activity" may be put through a verification step that wants a phone. Those are the cases where the number you use has to be a real mobile line.
What changed in 2026: Microsoft is phasing out SMS
In May 2026 Microsoft published a support notice stating that it "will start phasing out SMS as a method of authentication and account recovery for personal Microsoft accounts." The reasoning Microsoft gave was blunt — SMS-based authentication is now a leading source of fraud, largely because of SIM-swap attacks and code interception.
The replacements Microsoft is pushing are passkeys and a verified email address. Its stated rationale is worth quoting, because it is also the best argument for not attaching a phone number to this account in the first place: verified email and passkeys "ensure users can recover access even if they change phone numbers or lose devices."
Microsoft has not published a completion date for the phase-out, so treat this as in progress rather than finished. But the effects are already visible in the product. Microsoft's security-info page now carries the line "The option to add a new phone number may not be available for your Microsoft account," and through 2026 the Microsoft Q&A forums have filled up with users who cannot find an "add phone number" option at all. Independent advisors there are pointing people to the support article's wording — "For increased security, you can no longer add a phone number" — and directing them to use an alternate email, an authenticator app or a passkey instead.
What this means practically
If you are setting up a new personal account today, build it on email plus a passkey or authenticator app from the start. You are not working around a restriction by skipping the phone number; you are following the path Microsoft is steering everyone toward. Microsoft allows up to ten different verification methods on one account, and the supported ones are an email address (which does not have to be yours, only one you can access), an authenticator app, and a passkey unlocked with biometrics or a device PIN.
How to create the account without a phone number
- Go directly to
signup.live.comrather than clicking through from a product page. Several of the account-creation failures reported on Microsoft's forums were resolved by starting at the signup URL itself. - Choose "Get a new email address" if you want an Outlook.com or Hotmail address, or enter an existing address from any provider — a Microsoft account does not have to use a Microsoft mailbox.
- Set a password, then enter your name and date of birth.
- Enter the code Microsoft emails you. This is the verification step; there is no phone equivalent being requested here.
- Clear the "Help us beat the robots" CAPTCHA. If it loops back without accepting your answer, switch to the audio challenge — that is the fix that worked most consistently for users reporting the loop.
- Once you are in, go to
account.microsoft.com/securityand add your durable recovery methods immediately: a passkey on your phone or laptop, an authenticator app, and a second email address you control. Do this the same day. An account with only one recovery path is the account that gets permanently lost.
One caveat on step 6 that catches people out: if you ever strip all security info from a Microsoft account and replace it, Microsoft puts the account into a restricted state for 30 days before the change takes effect. During that window you cannot change your password, aliases or parental controls, and your OneDrive vault is inaccessible. Microsoft says it cannot expedite the 30 days unless you cancel the request. So add methods alongside existing ones rather than clearing the slate.
Where Microsoft still forces a phone number
| Flow | Phone required? | What to know |
|---|---|---|
| New personal account at signup.live.com | No | Email code plus CAPTCHA. No phone field in the current flow. |
| Adding a new sign-in method to a personal account | Not possible for many accounts | The option is being withdrawn. Use email, authenticator or passkey. |
| Azure free account and some paid trials | Yes | Separate identity check. Rejects VoIP outright. |
| "Unusual activity" verification on an existing account | Sometimes | Automated protection. May ask for SMS or may just need a cooling-off period. |
| Recovery on an older account that already has a phone attached | Yes, that specific number | You cannot substitute a different number to pass recovery. |
The Azure case is the one that produces the most frustration, because the error is unambiguous and there is no alternative route. The exact wording Microsoft returns is: "Sorry, we do not accept Voice over IP (VOIP) numbers. Try again with a different number." In a documented thread on Microsoft Q&A, a user confirmed their number received both calls and texts normally, tried the "Call me" option as Microsoft's moderator suggested, and was still refused as VoIP. The only remedy offered was to open a support request.
Why Microsoft rejects VoIP numbers
Microsoft's own troubleshooting page states it plainly: "VOIP numbers cannot be added as a way to sign in or get verification codes," and advises adding a mobile number instead. This is not a quirk of Microsoft's. It is a carrier lookup — a database query against the number's line type and carrier assignment, run before any code is sent, which is why the rejection comes back instantly rather than after a failed delivery. We covered the mechanics of that check in how websites detect VoIP numbers.
The practical consequence is that the free options most people reach for first will not clear it. A Google Voice number is classified as VoIP and fails these checks, which we went through in detail in does Google Voice work for SMS verification. The same applies to most app-based second-number services and to every "receive SMS online free" page, whose numbers are shared, already burned through thousands of signups, and publicly readable by anyone.
If you do need a number for Azure or a trial
Then it has to be a non-VoIP mobile line, and — this part matters more for Microsoft than for most platforms — you should think about how long you need to keep it.
A single-use verification code is fine for passing Azure's one-off identity check. It is a poor choice for anything that becomes security info on an account you intend to keep, because a number you no longer control is a recovery path you no longer have. Given how often Microsoft accounts get flagged for unusual activity and pushed into a verification step, losing a recovery method is a real risk, not a theoretical one. If a number is going to sit on the account, rent one you can hold and renew — TextVerified, for instance, offers US non-VoIP rentals from one day up to open-ended, starting around $1.50 — rather than using a one-shot code. If you only need to clear a single check and will then rely on a passkey and verified email, a one-time non-VoIP verification is the cheaper and cleaner option. Our breakdown of what SMS verification actually costs compares the two models on real numbers.
Troubleshooting the blocks you will actually hit
Most people who say they "can't make a Microsoft account without a phone number" are not being asked for a phone at all — they are hitting one of two other walls and misreading it.
The CAPTCHA loop. You solve "Help us beat the robots" and it simply reappears. There is no official fix. What works in practice: the audio challenge instead of the visual one, a private browsing window, no VPN, and a different network. Several users reported success switching from Wi-Fi to mobile data.
"Unusual activity" on creation. Account creation is blocked by an automated protection before you reach any verification step. Repeated retries make this worse, not better; the waiting period suggested on Microsoft's forums ranges from 24 to 48 hours with no attempts in between. Use a brand-new address rather than one you have already tried, turn off VPNs and ad blockers, and then leave it alone for a day. There is no number you can buy that solves this one.
If codes are being sent but not arriving, that is a third and separate problem — our diagnostic checklist for missing verification codes walks through how to tell delivery failure apart from rejection.
FAQ
Can I create an Outlook.com email without a phone number?
Yes. The current signup flow verifies you by emailing a code to another address you control, then shows a CAPTCHA. No phone number is requested. Older forum answers claiming signup "will not proceed" without a phone date back to 2017 and no longer describe the flow.
Is Microsoft really removing SMS verification?
Microsoft announced in May 2026 that it would begin phasing out SMS for authentication and account recovery on personal accounts, citing fraud. No completion date has been published, and accounts that already use SMS have not all lost it. But new phone numbers can no longer be added on many personal accounts, and the direction of travel is clear.
Why does Azure reject my phone number when it works fine?
Because the check is on the number's line type, not on whether it can receive messages. If a carrier lookup returns VoIP, Azure refuses it before sending anything — including through the "Call me" option. A real mobile line is the only thing that clears it. See VoIP vs non-VoIP numbers for why the distinction exists.
Should I attach a phone number to my Microsoft account at all?
If you are starting fresh, there is a reasonable case for not doing so. A passkey plus a verified recovery email is both the more secure configuration and the one Microsoft is standardising on, and it does not break when you change numbers or move country. A phone number on the account is one more identifier tied to you, and SMS is the weakest of the available factors.
What if my account is already locked and recovery wants my old number?
A different number will not substitute — recovery checks the specific number on record. Your route is Microsoft's account recovery form, which asks for other evidence you own the account, such as previously sent messages and billing details. Add a passkey and a second email as soon as you regain access.
The broader pattern here is worth noting if you are setting up accounts across several platforms: the direction is not uniform. Microsoft is retreating from SMS while Apple has gone the other way and now requires a verifiable mobile number on every new account — we covered that in the honest answer on Apple IDs without a phone number. Check the platform before you buy a number for it.