Troubleshooting Microsoft Authenticator Sign-In Problems (Entra MFA)

Summary

Fixes for common problems when signing in with Microsoft Authenticator on your UMS account, including missing or expired notifications, sign-in loops, "Something went wrong. [4s8qz]," push notification errors, and Authenticator no longer working on a jailbroken or rooted phone.

Body

If Microsoft Authenticator isn't working when you sign in to your University of Maine System (UMS) account, find your problem below and follow the fix. Having trouble adding Authenticator for the first time? See Troubleshooting Microsoft Authenticator Setup Errors (Entra MFA) instead.

Table of Contents

  1. Solution
    1. Not getting a sign-in notification
    2. Stuck in a sign-in loop
    3. Notifications always say they've expired
    4. "Something went wrong. [4s8qz]"
    5. Error messages in the app
    6. New, lost, or replaced phone
  2. Still stuck?
  3. Additional resources

Solution

Microsoft keeps a list of quick checks that fix many Authenticator problems, such as updating the app and checking your phone's settings. Start with Troubleshoot problems with Microsoft Authenticator, Microsoft Support (External Link), then use the sections below.

Microsoft's tips mention keeping security apps such as Microsoft Defender and Intune Company Portal up to date. If you don't have these apps on your phone, you can skip that tip.

ℹ️ INFO: When a Microsoft article tells you to contact your "IT admin" or "admin," contact the IT Service Desk.

Not getting a sign-in notification

Notifications are the alerts that pop up on your phone. If the Authenticator notification never arrives, you can't finish signing in.

  1. Turn on notifications for Microsoft Authenticator.
  2. Turn off Do Not Disturb, which blocks notifications.
  3. Open Authenticator and unlock it if it asks for your PIN, fingerprint, or face.
  4. If you need to sign in right away, look for an option on the sign-in screen to sign in another way. The options you see depend on the sign-in methods you've set up.
  5. If you still don't get notifications, follow Microsoft's fix for missing Authenticator notifications (External Link).

Stuck in a sign-in loop

A sign-in loop is when you keep landing back on the same sign-in screen and can't get into your account. Find the version that matches what you see.

You approve the sign-in in Authenticator, but you're sent back to sign in again:

This is usually caused by your web browser, not Authenticator. Follow the steps in the "Stuck in a sign-in loop" section of Common Sign-In Error Messages.

The sign-in screen keeps asking you to approve in Authenticator, but nothing arrives on your phone:

Your phone isn't getting the notification. Follow the steps in Not getting a sign-in notification above, and use the option to sign in another way if you need to get in right away.

If you're still stuck in the loop, contact the IT Service Desk.


Notifications always say they've expired

Authenticator needs the clocks on your phone and on the computer you're signing in from to match the real time. If either clock is off, notifications can show as expired.

  1. Set your phone's date and time to update automatically.
  2. On your computer, check that the date, time, and time zone are correct, and set them to update automatically.
  3. Follow Microsoft's fix for notifications that always expire (External Link).

"Something went wrong. [4s8qz]"

This is usually a short-term problem, such as an Authenticator update in progress. Wait a few minutes and try again. If it keeps happening, find the "Something went wrong. [4s8qz]" section in Troubleshoot problems with Microsoft Authenticator, Microsoft Support (External Link) and follow the steps there.


Error messages in the app

If you see one of these messages while signing in, find it below and follow the fix.

Message What to do
"Enable push notifications to receive alerts" or "Please ensure push notifications are enabled in Settings" Turn on notifications for Authenticator, then follow Microsoft's fix for push notification errors (External Link).
"We could not complete the sign-in at this time." Turn on notifications for Authenticator, then follow Microsoft's fix for this sign-in error (External Link).
"Your device is jailbroken" or "Your device is rooted" Authenticator stops working with your UMS account on this phone. Sign in with another method you've set up, or see MFA Without a Smartphone: Your Options. If you have no other method, contact the IT Service Desk. Learn more: Microsoft's explanation of jailbreak and root detection (External Link).

Help turning on notifications: Turn notifications on for an app on iPhone (External Link) or Control notifications on Android (External Link).

If the fix doesn't work, contact the IT Service Desk.


New, lost, or replaced phone

Authenticator doesn't move your UMS account to a new phone automatically. See Replacing or Recovering an MFA Sign-In Method (Lost, New, or Replacement Device).


Still stuck?

Contact the IT Service Desk.


Additional resources

Environment

  • Applies to all University of Maine System (UMS) accounts
  • Microsoft Entra multi-factor authentication (MFA)
  • Microsoft Authenticator app on iOS and Android

Details

Details

Article ID: 174703
Created
Fri 10/30/26 12:31 PM
Modified
Fri 10/30/26 12:31 PM
Applies To
Students
Faculty
Staff