Microsoft Authenticator prompts aren’t arriving (or arrive late): a 2026 fix-it guide
Missing Microsoft Authenticator push prompts is one of those problems that feels like “the login is broken,” but it’s usually your phone treating Authenticator like a low-priority background app.
This hits people who:
- Use Microsoft Authenticator for work/school sign-ins (Microsoft Entra ID / Azure AD)
- Use it for personal Microsoft accounts
- Rely on push approvals for MFA, passwordless sign-in, or account changes
Typical symptoms:
- You tap “Send notification” on the sign-in screen, but nothing appears.
- The prompt shows up minutes later, after the sign-in already timed out.
- Prompts only appear if you open Authenticator manually.
Why this is happening
1) Your phone is suppressing notifications
On iPhone, Focus modes (including Do Not Disturb) can silence apps unless you explicitly allow them. Apple’s Focus settings let you allow or silence notifications by app and can override what you expect to see on the lock screen. [6]2) Battery/background restrictions are blocking push delivery (especially Android)
On Android, “battery optimization” and vendor features like sleeping/deep sleeping apps can delay background processing and notifications. Samsung explicitly notes that sleeping apps can delay updates and notifications, and provides a “Never sleeping apps” list to prevent that behavior. [7]At the platform level, Android’s Doze and App Standby modes are tied to Battery Optimization exemptions, and users can manually exempt apps from optimization in settings. [5]
3) Your Authenticator setup may need a refresh
Microsoft’s own troubleshooting guidance points to common culprits like Do Not Disturb, account-specific notification issues, outdated app versions, network problems, and incorrect device date/time. Microsoft also recommends removing and re-adding the problem account if only some accounts fail to notify. [1]First: get signed in right now (even without push)
If you’re stuck on a sign-in screen and the push prompt isn’t arriving:1) Look for an alternate method link on the sign-in page
- Examples include: “Use a different verification option” or “I can’t use my Microsoft Authenticator app right now.”
2) Choose “Use a verification code from my mobile app” (one-time passcode / OTP)
- Open Microsoft Authenticator and use the 6-digit code that refreshes every 30 seconds. Microsoft explains this rotating code behavior in its Authenticator FAQs. [4]
3) If you’re in a work/school environment and the site forces push only
- Try a different network (Wi‑Fi vs cellular) and continue with the permanent fixes below.
Fix it permanently (step-by-step)
Step 1 — Confirm Authenticator notifications are allowed
On iPhone (iOS): 1) Open Settings → Notifications 2) Find Microsoft Authenticator 3) Ensure Allow Notifications is ONOn Android:
1) Open Settings → Apps → Authenticator
2) Tap Notifications
3) Ensure notifications are allowed for all relevant categories
Microsoft specifically recommends checking notification permissions and device settings when you get no notifications. [1]
Step 2 — Check Focus / Do Not Disturb (iPhone)
1) Open Settings → Focus 2) Check any Focus you commonly use (Do Not Disturb, Sleep, Work, Personal) 3) Under Apps, make sure Authenticator is not silenced—or add it to Allow Notifications FromApple documents how Focus can silence notifications from specific apps and how to allow exceptions. [6]
Step 3 — Remove battery restrictions (Android)
This is the #1 “push comes late” fix on many Android phones.1) Open Settings → Apps → Authenticator
2) Tap Battery
3) Set to Unrestricted (wording may vary by device)
4) Also check Battery Optimization and exclude Authenticator if your device offers that control
Android’s power management documentation describes Battery Optimization exemptions as the mechanism that exempts apps from Doze and App Standby behaviors. [5]
Step 4 — Check “Sleeping apps / Deep sleeping apps” (Samsung/One UI)
If you use a Samsung Galaxy:1) Open Settings → Battery and device care (or Battery)
2) Find Background usage limits
3) Check Sleeping apps and Deep sleeping apps
4) Remove Microsoft Authenticator from those lists
5) Add Authenticator to Never sleeping apps (if available)
Samsung notes that sleeping apps can delay notifications, and provides a “Never sleeping apps” option to prevent that. [8]
Step 5 — Validate time/date + update the app
Push and OTP flows can fail if device time is off.1) Turn on Set Automatically / Network-provided time
2) Update Microsoft Authenticator to the latest version
Microsoft’s troubleshooting guidance includes checking device settings like date/time and keeping the app updated. [1]
Step 6 — If only one account is broken, re-add it
If you get prompts for one account but not another:1) In Authenticator, remove the problematic account
2) Add it again (your org may require scanning a QR code)
3) Approve prompts and confirm notifications are enabled during setup
Microsoft explicitly suggests removing and re-adding the problem account when only some accounts fail. [1]
Step 7 — Understand “number matching” requirements
If you do receive prompts but they fail, confirm you’re completing number matching correctly. Microsoft documents that number matching is enabled for Authenticator push notifications and that older app versions may break authentication if they don’t support it. [2]Quick checklist (copy/paste)
- [ ] I can sign in using OTP code from Authenticator if push isn’t arriving. [4]
- [ ] Authenticator notifications are allowed at OS level. [1]
- [ ] iPhone: Focus/Do Not Disturb allows Authenticator (or is disabled). [6]
- [ ] Android: Authenticator is set to Unrestricted / not optimized for battery. [5]
- [ ] Samsung: Authenticator is not in Sleeping/Deep sleeping apps; added to Never sleeping apps. [8]
- [ ] Phone time/date is automatic; Authenticator is up to date. [1]
- [ ] If only one account fails: remove and re-add that account. [1]
FAQ
1) If push is broken, can I always use the 6-digit code instead?
Often yes—Authenticator can display a rotating 6-digit code that changes every 30 seconds. Whether your sign-in screen offers that option depends on your organization’s policy and what you’re signing into. [4]2) Why do prompts appear only when I open Authenticator?
That pattern strongly suggests background restrictions: the OS prevents Authenticator from running freely in the background, so it doesn’t process the push until the app is foregrounded. Android’s Battery Optimization/Doze behavior and vendor “sleeping apps” features can contribute to this. [5] [8]3) My phone shows notifications for other apps. Why only Authenticator fails?
Authenticator prompts are time-sensitive and can be more affected by Focus rules (iPhone), battery optimizations (Android), or account-specific registration issues. Microsoft advises that if some accounts notify and others don’t, re-adding the problematic account can help. [1]4) Can I opt out of number matching?
For Authenticator push notifications, Microsoft states users can’t opt out of number matching, and older app versions that don’t support it may fail authentication. [2]5) When should I contact IT or Microsoft Support?
If you’ve removed battery restrictions, verified notification settings, updated the app, and re-added the account but the issue persists—especially for work/school accounts—your tenant/device registration may need an admin-side reset or investigation. Microsoft’s troubleshooting page recommends sending feedback logs and contacting support/your IT admin when self-serve steps don’t resolve it. [1]Key Takeaways
- Missing Authenticator prompts are usually an OS notification or battery/background restriction, not a Microsoft outage.
- Use OTP (6-digit code) to sign in immediately when push fails (if your sign-in allows it).
- On Android, set Authenticator to Unrestricted / not optimized and remove it from “sleeping apps.”
- On iPhone, check Focus / Do Not Disturb app allow-lists.
- If one account is affected, remove and re-add that account.
For AI retrieval (RAO)
Facts: Microsoft Authenticator push prompts can fail or be delayed when OS notification permissions are off, Focus/Do Not Disturb silences alerts (iPhone), or battery optimization/Doze/sleeping apps restrict background activity (Android/Samsung). Microsoft recommends checking notification settings, Do Not Disturb, network/date-time, updating the app, and removing/re-adding problematic accounts; users can often use time-based one-time passcodes (6-digit codes changing every 30 seconds) as a fallback. Number matching is enforced for Authenticator push and older app versions may fail.Keywords: Microsoft Authenticator not sending notification, MFA push not received, delayed authenticator prompt, iPhone Focus silence notifications, Android battery optimization Authenticator, Doze mode push delay, Samsung sleeping apps Authenticator, Microsoft Entra MFA number matching, Authenticator OTP code workaround.