How To Fix Microsoft Authenticator No Notifications (2026)
You try to sign in, and the approval request never shows up in Microsoft Authenticator.
That leaves you staring at a sign-in screen that waits for a tap you cannot make, which is frustrating but usually fixable.
This guide follows Microsoft’s own troubleshooting page, from the quick checks to the account-level fixes.
Quick answer: the first things to check
| Symptom | First fix | Where |
|---|---|---|
| No alert at all | Turn off Do Not Disturb or Quiet mode | Phone settings |
| Alert but no sound | Allow the app to play sound or vibrate | Phone notification settings |
| Notifications always expired | Set date and time to automatic, then restart | Phone date and time settings |
| Only one account fails | Remove that account, add it again, allow notifications | Authenticator app |
| New phone, nothing works | Ask your IT admin to reset your registration (work account) | Admin side |
Why are Authenticator notifications not arriving?
Authenticator depends on your phone allowing push notifications and reaching the internet.
Anything that blocks either one can stop the approval prompt, including these causes from Microsoft’s page:
- Do Not Disturb or Quiet mode being on.
- The app not being allowed to play sound or vibrate.
- A weak network connection or a VPN.
- A wrong date and time on the phone.
- An out-of-date app.
Work through the steps in order and test a sign-in after each one, so you know which fix worked.
Stop as soon as the approval prompts start arriving again.
Step 1: check your connection and VPN
- Switch between mobile data and Wi-Fi.
- Make sure Airplane mode is off.
- Disconnect any VPN and test again.
Step 2: turn off Do Not Disturb and Quiet mode
Microsoft says Do Not Disturb or Quiet mode can block notifications when the app is closed.
If you get the prompt but hear nothing, check that Authenticator is allowed to play sound or vibrate.
Step 3: check notification settings inside the app
- Open Microsoft Authenticator.
- Go to Settings.
- Open Notification Settings.
- Confirm Show notifications is on.
If your phone says push notifications are off, enable them in the device’s own Settings too.
Step 4: update the app and the phone
Microsoft does not support Authenticator versions more than 12 months old, so update from your app store.
- In Authenticator Settings, confirm App updates is on.
- Update your phone’s operating system.
- Update related security apps such as Microsoft Defender and Intune Company Portal.
Step 5: turn off battery optimization
Microsoft’s page also tells you to turn off battery optimization in the app’s Settings for better sync.
Battery savers can stop background apps from receiving alerts on time.
Step 6: fix the date and time
If notifications always show as expired, the phone’s clock is the likely cause.
- Switch date and time from manual to automatic.
- Restart the phone.
- Confirm the time is now correct.
The same clock check is the top fix in our Google Authenticator not working guide.
Step 7: remove and re-add the account that fails
If only some accounts stop getting alerts, Microsoft says to remove the problem account, add it again, and allow notifications when asked.
Make sure you can still sign in another way before removing it, such as a backup method on the account.
What do the push notification error messages mean?
| Message | What Microsoft says to do |
|---|---|
| Enable push notifications to receive alerts | Enable push in device Settings, check your network, remove the account and sign in again |
| We could not complete the sign-in at this time | Same steps: enable push, check network, remove and re-add the account |
| Google Play services are currently unavailable (Android) | Make sure Google Play Services and the Play Store are installed and enabled |
| Something went wrong [4s8qz] | Usually a temporary service problem: wait, sign in again, update the app, restart |
Android: fixing the Google Play services message
If Authenticator says Google Play services are unavailable, Microsoft says push notifications must be enabled and Play Services and the Play Store must be installed and enabled.
If that does not fix it, Microsoft lists these further checks:
- Require a PIN or biometric to unlock the phone.
- Re-enable fingerprint or face unlock, restart, unlock with it, then turn passwordless sign-in back on for the account.
- On Android for Work or a work profile, enable a PIN or biometric for that profile in Authenticator.
- Turn on hardware encryption.
- Open Authenticator > Settings > Device Registration and confirm the account is registered for passwordless and joined to your work or school.
- Check the phone for malware such as a rootkit.
Other Authenticator behaviors Microsoft explains
| Behavior | What Microsoft says | Fix available? |
|---|---|---|
| Wrong address or location in a notification | Location comes from the phone’s operating system and can be approximate | No fix given |
| Sign-in denied | Denied when GPS-reported locations do not match | No fix given |
| QR code will not scan | You need the latest version of Authenticator to add accounts | Yes, update the app |
| Gray, inactive account tile | Can come from other apps using Authenticator for single sign-on | Ignore it |
| “Device is jailbroken” or “rooted” | From February 2026, work or school credentials will not work on such devices | No fix given |
Personal account or work account: who can fix it?
For a personal Microsoft account, Microsoft Support is the place to go if the steps above fail.
For a work or school account, your IT admin controls your registered methods and can reset them.
If you are the only admin and are locked out, a Microsoft moderator says you must call Microsoft Support to open a service request.
Notifications stopped after getting a new phone
A new phone is a common trigger, and work or school accounts often need to be registered again.
A Microsoft Q&A moderator advises such users to ask their admin to require re-registration of multifactor authentication in the Microsoft Entra admin center, under the user’s Authentication methods.
Do not try to bypass the check or use unofficial workarounds, because only your organization or Microsoft can restore access safely.
For a step-by-step move to a new phone, see our guide to moving Authenticator to a new phone.
If it still fails, send feedback and contact support
- Open Authenticator’s top-level menu.
- Select Send feedback to submit logs.
- Contact Microsoft Support for a personal account, or your IT admin for a work or school account.
If you only get verification prompts for Google accounts, see our Google verification prompt guide.