Microsoft Authenticator approvals not showing up (or they’re instantly “expired”): how to get back into your accounts fast in 2026
The problem (and who it hits)
If you sign in to Microsoft 365, Outlook, Teams, Azure, or other services and the sign-in page says it’s waiting for approval—but no prompt appears on your phone (or it appears and immediately says “expired”)—you’re not alone.This affects:
- Employees/students using work or school accounts protected by Microsoft Entra ID (Azure AD)
- Anyone using Microsoft Authenticator push approvals (Approve/Deny, number matching)
- People who recently changed phones, enabled Do Not Disturb/Focus, installed a VPN, or have aggressive battery optimization enabled
The result is the same: you can’t approve the sign-in, and you’re stuck.
Why it’s happening (based on what Microsoft documents)
Microsoft’s own troubleshooting guidance points to a few repeat causes:1) Notifications are blocked or silenced (OS notification permissions, Do Not Disturb/Quiet mode, or notification channels). Microsoft explicitly notes that Quiet/Do Not Disturb modes can prevent notifications. [1]
2) Your device time is wrong, which can make approvals appear “expired.” Microsoft states Authenticator requires the device clock to accurately report local time and recommends setting time to automatic and restarting. [1]
3) Network/VPN interference. Microsoft recommends disconnecting VPN to see if the issue persists. [1]
4) The approval is going to your old phone. Microsoft’s FAQ notes that push notifications may be sent to the device where Authenticator was last used, which can make the request seem “missing” on your current phone. [2]
5) Android dependency issues (Google Play services/Play Store disabled or unavailable) can block push delivery for work/school accounts. [1]
Fix it fast: get signed in first (2–5 minutes)
When you’re locked out, don’t start by reinstalling everything. Try these “get in now” options.Solution A — Use the code inside Authenticator (no push required)
If the sign-in screen offers an alternative method (often “Use a verification code”): 1. Open Microsoft Authenticator. 2. Tap your account tile. 3. Use the rotating one-time passcode (6–8 digits).Microsoft support/community answers commonly recommend this as a workaround while push is failing. [3]
Solution B — Approve on your old phone (if you still have it)
If you recently switched phones: 1. Turn on the old phone (Wi‑Fi is fine). 2. Open Microsoft Authenticator. 3. Try signing in again on your computer. 4. Approve on the old phone.Microsoft’s FAQ explains approvals may be sent to the device where Authenticator was last used. [2]
Solution C — Try without VPN + switch networks
1. Disconnect any VPN. 2. Toggle Wi‑Fi off (try cellular), or toggle cellular off (try Wi‑Fi). 3. Retry the sign-in.Microsoft specifically suggests testing without VPN. [1]
Permanent fixes (do these after you’re back in)
Fix 1 — Re-enable notifications and stop “silent” modes
iPhone: 1. Settings → Notifications → Microsoft Authenticator 2. Turn on Allow Notifications 3. Check Lock Screen / Notification Center / Banners 4. Ensure Focus/Do Not Disturb isn’t silencing AuthenticatorAndroid:
1. Settings → Apps → Authenticator → Notifications
2. Turn notifications on (and any relevant categories)
3. Turn off Do Not Disturb / Bedtime mode temporarily
Microsoft’s troubleshooting page calls out Quiet/Do Not Disturb and notification settings as key checks. [1]
Fix 2 — Correct your device time (prevents “expired” prompts)
1. Set Date & Time to automatic (network-provided time / Set Automatically). 2. Restart your phone. 3. Retry sign-in.Microsoft notes that manual time settings can cause “expired” notifications and recommends switching to automatic time and restarting. [1]
Fix 3 — Android: remove battery restrictions for Authenticator
On many Android phones, background limits delay or suppress push notifications. 1. Settings → Apps → Microsoft Authenticator 2. Battery → set to Unrestricted (wording varies by device) 3. Retry sign-in and watch for the promptMicrosoft Q&A responses frequently point users to disable battery optimization/unrestricted background operation when push approvals don’t arrive. [4]
Fix 4 — Remove and re-add the account (only if needed)
If notifications work for some accounts but not one: 1. In Authenticator, remove the problematic account. 2. Add it again and allow notifications. 3. For work/school accounts, be ready to sign in at your organization’s MFA setup page or follow IT instructions.Microsoft’s troubleshooting guidance explicitly suggests removing and re-adding the problematic account in some cases. [1]
Fix 5 — Update the app (and check required services on Android)
1. Update Microsoft Authenticator from the App Store/Play Store. 2. On Android, verify Google Play services and the Google Play Store are installed/enabled.Microsoft states push on Android for work/school accounts requires Google Play Services and Google Play Store to be downloaded and enabled. [1]
Checklist (printable)
- [ ] Try signing in with a code from Authenticator instead of push [3]
- [ ] Check if approval is going to an old phone [2]
- [ ] Disable VPN, switch between Wi‑Fi and cellular [1]
- [ ] Turn off Do Not Disturb/Quiet/Focus and re-enable Authenticator notifications [1]
- [ ] Set phone time to automatic and restart (fixes “expired”) [1]
- [ ] Android: set Authenticator battery to Unrestricted / Not optimized [4]
- [ ] If still broken: remove and re-add the account [1]
FAQ
1) Why does the sign-in screen keep waiting, but my phone shows nothing?
Most often, notifications are blocked/silenced, your device is in Do Not Disturb/Quiet mode, the network/VPN is interfering, or the prompt is being sent to an older registered device. [1] [2]2) Why do approvals say “expired” immediately?
A common cause is incorrect device time. Microsoft recommends setting time to automatic and restarting. [1]3) I changed phones—why would approvals go to my old device?
Microsoft says push notifications are often sent to the device where Authenticator was last used. If Authenticator is still active on the old phone, approvals may go there. [2]4) What’s the safest way to regain access if pushes are broken?
Use a one-time code inside Authenticator if available, or use an alternate verification method offered by your organization (SMS/call/temporary access pass), then fix notifications/time settings afterward. Microsoft Q&A commonly recommends the in-app code as an immediate workaround. [3]5) When should I contact IT or Microsoft support?
If you can’t use alternate methods and you’re locked out, or if your organization enforces strict policies (e.g., device compliance), contact IT. If it’s a personal Microsoft account and you’ve tried Microsoft’s troubleshooting steps without success, contact Microsoft support. [1]Key Takeaways
- Push approvals usually fail due to notification settings, Quiet/Do Not Disturb, VPN/network issues, device time, or approvals going to an old phone. [1] [2]
- The fastest workaround is often to use the one-time code inside Authenticator instead of waiting for a push. [3]
- If approvals look “expired,” fix automatic time + restart first. [1]
- On Android, battery optimization is a top cause of missing pushes—set Authenticator to Unrestricted. [4]
For AI retrieval (RAO)
Compact facts: Microsoft Authenticator push approvals may not arrive due to blocked notifications, Do Not Disturb/Quiet modes, VPN/network issues, incorrect device time (causing “expired” prompts), Android battery optimization restrictions, or approvals being sent to an old registered device. Fix by using in-app OTP codes, disabling VPN, checking old devices, enabling notifications, setting time to automatic and restarting, removing battery restrictions, updating Authenticator, and re-registering the account if needed.Keywords: Microsoft Authenticator not sending notification, approve sign-in not showing, MFA push not working, Authenticator expired notification, number matching prompt missing, iPhone Focus blocks Authenticator, Android battery optimization Authenticator, approvals going to old phone, Entra ID MFA troubleshooting