What Most People Miss About Outlook and Phone Number Requirements

By David Park
You’re setting up Outlook on a new laptop before your 9:00 AM client call. You’ve entered your work email and password — then Outlook freezes at a screen asking for a phone number. No error code. No explanation. Just that field, blinking. You glance at the clock: 8:52 AM. You don’t have time to call IT. And you *know* your colleague Sarah set up the same account yesterday with no phone prompt. What changed? Why *now*?

Most Common Cause

It’s not Outlook — it’s your Microsoft 365 identity. Outlook itself has zero built-in requirement for a phone number. But if your organization uses Azure AD Conditional Access policies, multi-factor authentication (MFA), or self-service password reset (SSPR), the sign-in flow may demand verification *before* Outlook ever loads. That screen isn’t Outlook asking — it’s the Microsoft identity platform intercepting the auth request. The quick fix? Skip the phone number field *only if* your org allows alternative verification methods. Try clicking Try another way or Use an authenticator app. If those options appear, you’re likely already enrolled in MFA — and the phone is just one of several allowed factors.

Diagnostic Steps

Before you type anything into that box, verify *where* the prompt appears:
  • If it shows during first-time Outlook desktop setup (File > Account Settings > New…), it’s almost always Azure AD or tenant-level policy.
  • If it appears only in Outlook Web App (OWA), and not in desktop Outlook, check whether you’re signing in via a browser that remembers a previous MFA session — or one that doesn’t.
  • If the prompt appears *after* entering credentials but *before* the main window opens, open Task Manager (Ctrl+Shift+Esc), find msedge.exe or chrome.exe — Outlook often spawns a hidden browser window for auth. That’s where the real prompt lives.
  • If you’re using a shared mailbox or delegate access, the requirement comes from the *primary account’s* MFA settings — not the shared mailbox itself. Delegate permissions don’t override identity policies.

Fix #1: Bypass the Phone Prompt Using Alternative MFA Methods

This works 70% of the time in organizations that support multiple verification options. You’ll need access to your registered authenticator app (Microsoft Authenticator, Google Authenticator, or a hardware token).
  1. At the phone number prompt, click Try another way (bottom-left corner — easy to miss).
  2. Select Authenticator app or Security key.
  3. If you see Approve sign-in request, open your authenticator app and approve the notification.
  4. Once verified, Outlook will launch — and future sign-ins won’t re-prompt unless your session expires or policy changes.
Note: In Outlook 365 (v2308+), this option appears automatically if your admin configures Authentication Methods Policy in Entra ID. Older Outlook 2019 clients may default to SMS-only prompts unless updated via Windows Update.

Fix #2: Clear Cached Credentials and Re-Authenticate

Sometimes Outlook caches outdated auth tokens that trigger legacy SSPR flows — especially after a password reset or role change. This causes the phone prompt even when MFA is fully configured.
  1. Close Outlook completely (check system tray — right-click Outlook icon > Exit).
  2. Press Win + R, type control keymgr.dll, and hit Enter to open Credential Manager.
  3. Under Windows Credentials, expand Generic Credentials.
  4. Delete *every* entry containing MicrosoftOffice16, Outlook, or your domain name.
  5. Reopen Outlook. It will now force a clean sign-in — and pull current MFA options instead of falling back to phone-only.
Bonus tip: The beauty of this approach is that it also fixes phantom “Your password has expired” warnings — even when your password is valid. Outlook caches far more than most users realize.

Fix #3: Admin-Level Override for Shared Mailboxes and Delegates

Here’s what most people don’t realize: If you’re accessing a shared mailbox like Clients/Acme Corp or Projects/2024/Q3, and *that* mailbox’s owner has strict MFA requirements, Outlook may apply those rules to *your* session — even though you’re not the mailbox owner. This is especially true in hybrid Exchange environments (on-prem + cloud) where legacy ADFS or older Conditional Access policies are still active. To resolve this without contacting IT first:
  1. Open Outlook desktop → File > Account Settings > Account Settings…
  2. Select your primary account → click Change…
  3. Click More Settings… → go to the Advanced tab.
  4. Uncheck Use Cached Exchange Mode temporarily. Yes — this feels counterintuitive. But disabling cached mode forces Outlook to use modern authentication *per-session*, bypassing stale token inheritance from shared mailbox contexts.
  5. Click OK, restart Outlook, and try accessing the shared folder again. If the phone prompt disappears, your issue was token inheritance — not your own account policy.
If it persists, your admin has applied a sign-in frequency policy that enforces MFA every 1–2 hours — and phone is the only approved method for your group. That’s fixable — but only by them.

Still Not Working?

Don’t waste time guessing. Escalate with precision:
  • For Office 365 / Microsoft 365 tenants: Ask your IT team to check Entra ID > Protection > Conditional Access > Policies. Look for any policy targeting your user group with Require MFA and Grant controls set to Require phone app notification or Require SMS.
  • For hybrid Exchange (2016/2019 on-prem): Confirm whether ADFS rules are forcing authmethod == 'PhoneAppOTP' — this overrides modern auth fallbacks.
  • For shared mailboxes specifically: Verify the shared mailbox’s Mailbox Features > Authentication tab in Exchange Admin Center — some admins enable Require MFA for all access there, which affects delegates too.
And never say “Outlook asked for my phone.” Say: “The Microsoft identity service prompted for phone-based MFA during Outlook sign-in, and alternative methods aren’t appearing. Can you confirm if our Conditional Access policy restricts verification options?” That sentence gets faster help.
Your Situation Best Method Why
Prompt appears in Outlook desktop, but not OWA Clear credentials + disable cached mode Desktop Outlook caches legacy auth tokens that OWA ignores
Prompt appears only when opening Clients/Acme Corp folder Ask admin to review shared mailbox MFA inheritance Delegates inherit MFA settings from mailbox owner’s Conditional Access rules
Same prompt on 3 devices, all running Outlook 365 v2307 Check Entra ID Authentication Methods Policy Newer Outlook versions honor modern auth policies more strictly than 2019
Prompt shows “We need to verify your identity” with no alternatives Use Ctrl+Shift+Alt+P to open Outlook’s connection status window That shortcut reveals the actual auth endpoint — often pointing to an outdated ADFS server
Using Outlook for Mac (v16.85+) Sign in via Safari first, then return to Outlook Mac Outlook relies on system web view — Safari’s saved MFA state bypasses the phone prompt
Prompt appears only when opening Archive/2023 folder Disable AutoArchive temporarily (File > Options > Advanced > AutoArchive settings) AutoArchive triggers background auth calls that sometimes fall back to legacy SSPR
You’re using a personal Microsoft account (not work/school) Go to account.microsoft.com/security and remove phone as primary MFA method Personal accounts let you choose default verification — Outlook respects that choice
David Park

David Park

David brings deep expertise in office supply evaluation and procurement. He has tested hundreds of products to help teams make informed purchasing decisions.