Troubleshooting MFA for Microsoft 365

Introduction to Troubleshooting MFA 

Most of the time setting up the MFA for Microsoft 365 is a quick process, but there is a chance a variety of errors or issues can occur. This article covers some of the common problems that can temporarily impede setting up or confirming MFA for your account and what to do in those circumstances. Check out the scenarios further below, which includes screenshots of the errors that can be encountered.

Please visit this Microsoft Support page if you are encountering a different error than what can be found in this article.

Overall the most reliable and secure option for MFA is the Microsoft Authenticator app. Using MFA on an office phone can be more prone to errors and is not as readily available as well.

For students setting up MFA, this article will contain errors that can appear as well. For setup instructions, please visit the MFA Setup for Student Email on Microsoft 365 article. 


Looking for general information, instructions on how to initially add MFA options, or needing assistance adding more MFA options? Here are the other articles available about MFA for Microsoft 365:


General Tips:

1.  Common fixes include:

  • Start over from the beginning of the MFA setup process (previous page may also work).
  • Switch to another web browser.
  • Clear browser data (cookies/cache).
  • Trying to add a MFA option that isn't working at a later time.

2.  When initially logging in, double check that you are signing in with your EFSC email address. This will be the same as when you log in to myEFSC. Try visiting office.com or outlook.com if experiencing errors logging in or utilize a separate browser.

3.  Timeouts are known to occur frequently and can halt progress. If this occurs, simply head back to the beginning of the setup process. It is recommended to complete MFA setup in one sitting and without staying on the same page for a length of time.

4.  Airplane mode will need to be disabled if it is on, otherwise setup and retrieval of verification codes will not work.

5.  Removing and reinstalling email applications on mobile devices may be necessary to clear up some issues that arise.

6.  While it is best to avoid adding an office phone number altogether besides as a backup option, if it appears it is not working correctly, try adding the number using the Phone or Alternate Phone option instead.

7.  If you are not receiving phone calls to confirm verification, try switching to a different browser to see if that will trigger the calls to go through.

8.  In the event no MFA option can be accessed, contact the IT Support Desk via phone or by creating a ticket for assistance.

 


List of Known Errors and Solutions:

Listed below are potential error messages and issues that can happen in the MFA process. Check out this list first and refer to the corresponding number for more information.

  • (1) “Sorry, but we’re having trouble signing you in.”
  • (2) “An error was encountered. Error updating user.”
  • (3) Multiple App Passwords – Security Info
  • (4) “We're sorry, we ran into a problem. Please select "Next" to try again”
  • (5) “Request failed due to exceeding the number of allowed attempts”
  • (6) “Session expired. Please try signing in again.” / "The session has expired."
  • (7) "An unexpected error has occurred"
  • (8) "We're sorry, ran into a problem. Please choose "Resend notification" to try again." 

 

(1) “Sorry, but we’re having trouble signing you in.”

This common error message can occur if you were initially setting up an MFA option and a verification code was not entered right away or the page timed out. Here are some potential fixes:

  1. Simply head back to the previous page and try again.
  2. Start over from the beginning of the MFA setup.
  3. If the issue persists, temporarily switch to another browser to setup the MFA.
  4. Clear the browsing data (cookies/cache) in the web browser.

error1

 

 

 

 

 

 

 

 

 

 

(2) “An error was encountered. Error updating user.”

Can occur when initially trying to setup an MFA such as Authentication phone. You may be able to proceed all the way through each step until clicking the Done button at the end when this message will appear. Here are some potential fixes:

  1. If you are initially setting up MFA for the first time, it is recommended to start over for the time being and select a different option. This can always be added later.
  2. Try this option again later and you may be successful in adding the MFA option with no error.
  3. If the issue persists, temporarily switch to another browser to setup the MFA.
  4. Clear the browsing data (cookies/cache) in the web browser.

error2

 

 

 

 

 

 

 

(3) Multiple App Passwords – Security Info

If you see there are multiple app passwords in your Microsoft 365 account in the Security Info section, it is likely they will not interfere with your account. If you do not plan to use these app passwords, as it is most probable you won’t need to use them, they can be deleted in this section via the Delete button to the right of each listed App password. Keep in mind that app passwords will primarily be used for devices that do that not have two-factor authentication capabilities, typically for older operating systems, and the general setup for MFA will not require it on a daily basis.

error3

 

 

 

 

 

 

 

(4) “We're sorry, we ran into a problem. Please select "Next" to try again”

This error can potentially occur when trying to add or edit a method in the Security Info area in Microsoft 365. In the case for the below image, this occurred when trying to switch the option from text to a phone call for MFA. Here are some potential fixes:

  1. Try this option again later and you may be successful in editing the MFA option with no error.
  2. If the issue persists, temporarily switch to another browser to change the MFA.
  3. Clear the browsing data (cookies/cache) in the web browser.

error4

 

 

 

 

 

(5) “Request failed due to exceeding the number of allowed attempts”

While initially setting up a MFA method, this error may happen when continuously trying to add a method in a short time frame, often if the attempted method is not working. It may be difficult to notice this error right away as the error might only appear for a moment before disappearing, with the process proceeding to the next step automatically. This may lead to the message: “An error was encountered. Error updating user.” See details above for that error. Here are some potential fixes:

  1. If you are initially setting up MFA for the first time, it is recommended to start over for the time being and select a different option. This can always be added later.
  2. Try this option again later and you may be successful in adding the MFA option with no error.
  3. If the issue persists, temporarily switch to another browser to setup the MFA.
  4. Clear the browsing data (cookies/cache) in the web browser.

error5

 

 

 

 

 

 

(6) “Session expired. Please try signing in again.” / "The session has expired."

This message will mostly occur if the MFA setup is not completed all at once and the page timed out, or if you step away and left the setup on a page for more than a few minutes. It is best to complete the MFA in one sitting and without staying on one page for too long. Here are some potential fixes:

  1. Simply head back to the previous page and try again.
  2. Start over from the beginning of the MFA setup.
  3. If the issue persists, temporarily switch to another browser to setup the MFA.
  4. Clear the browsing data (cookies/cache) in the web browser.

 

 

 

 

(7) "An unexpected error has occurred"

This message will likely populate if the MFA setup was not completed quickly and a timeout occurred. For the two images below, these appeared after arriving to a Success page during the setup, which is at the end of the process. The first image will appear in the top right side of the page, and the second may prompt if the page is refreshed. Here are some potential fixes:

  1. If the error keeps appearing, close out the browser tab or window for the MFA setup.
  2. Attempt to sign in to your account. Sometimes the setup can be successful and you may be prompted to verify your MFA.
  3. If the MFA setup was not successful, starting over from the beginning is the best solution.
  4. If necessary, switch to another browser or clear the browsing data (cookies/cache) if the error is stuck on the page.

 

(8) "We're sorry, ran into a problem. Please choose "Resend notification" to try again." 

Can occur during setup process where a two digit code is required to be entered using the Microsoft Authenticator app. This normally happens if the code was not entered right away. There is a chance this can happen if the page continuously tries to load although the number was entered correctly. Here are some potential fixes:

  1. First try the Resend notification link as mentioned in the error. This will be on the MFA setup page that provides the two digit number. Then enter the number quickly into the Microsoft Authenticator app.
  2. If the same error appears, try to refresh or go back to the previous page to proceed.
  3. Close out of the browser tab or window, then start over from the beginning of the MFA setup.
  4. If the error persists, switch to another browser to attempt the setup or clear the browsing data (cookies/cache).

 

 


For further assistance, questions, or concerns, please either create a ticket or call the IT Support Desk at 321-433-7600, open 7am to midnight, 7 days a week. After accessing myEFSC, the Open an IT Ticket button can be found in the IT Support section, typically found near the bottom of the page.

When creating a ticket, select the Email, Teams & Calendaring category, followed by the appropriate Email Assistance service to submit a ticket. Please include an alternative contact method (if you cannot access your email). Include details, error messages, and provide screenshots if possible of the steps you have taken so we may further assist you.

itsupport

 

Details

Article ID: 134273
Created
Thu 9/9/21 4:19 PM
Modified
Tue 8/8/23 2:36 PM