Fix Microsoft 365 MFA Authenticator Code Setup Failure
Question details
The user is unable to set up Microsoft 365 multifactor authentication using an authenticator app code, receiving an unexpected response error.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Setting up an authenticator application for Microsoft 365 multifactor authentication using verification codes.
- Observed behavior
- MFA notification prompts work successfully, but registering via a verification-code authenticator app fails with the error message "We did not receive the expected response," even when using multiple different authenticator applications.
Ensure you have the contact information for your organization's IT or Azure AD administrator, as resolving this authentication issue requires administrative access to the Microsoft 365 tenant settings.
Contact Administrator to Verify MFA and Conditional Access Policies
Since notification prompts work but verification codes fail, your administrator needs to ensure that verification codes are explicitly enabled in your organization's authentication methods.
In Microsoft 365 and Azure AD, administrators can restrict which multifactor authentication methods are permitted for users. If verification codes are not enabled in the Authentication Methods policy or are blocked by Conditional Access policies, the setup will fail regardless of which authenticator app you use.
Reach out to your organization's Microsoft 365 or Azure AD administrator and explain the specific error message you are receiving.
Ask the administrator to review the organization's Azure AD Multi-Factor Authentication settings and Conditional Access policies.
The administrator must navigate to the Azure portal, check the authentication methods policy, and verify that the 'Verification code from mobile app or hardware token' option is enabled for your account.
Re-register the Authenticator App After Policy Updates
After your administrator confirms that verification codes have been enabled, you will need to start the authenticator app registration process over again from your security settings.
Looking for a Hassle-Free Office Suite? Try WPS Office
While resolving Microsoft 365 account and MFA issues can be complicated, your daily productivity shouldn't be affected. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office, allowing you to create, edit, and save Word, Excel, and PowerPoint files locally without complex account or cloud setups.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button to get the installer for your operating system.
- 2. Install the Software: Run the downloaded file and follow the simple on-screen instructions to complete the installation.
- 3. Open Your Files: Launch WPS Office and directly open your existing Microsoft Office documents to seamlessly continue your work.
Frequently Asked Questions
Why does the Microsoft authenticator app push prompt work but the verification code fails?
This situation usually occurs when the organization's Azure AD administrator has enabled push notifications for MFA but has not enabled the use of verification codes in the authentication methods policy. Both methods require explicit administrative permission.
Can I bypass Microsoft 365 MFA if my authenticator app continues to fail?
No, if your organization's security policies require MFA for Microsoft 365 access, you cannot bypass it. You must work with your IT administrator to resolve the authenticator configuration issue or use an alternative approved sign-in method, such as an SMS code or phone call, if those are permitted.
Does the error 'We did not receive the expected response' mean my specific authenticator app is broken?
Not necessarily. If you test multiple different authenticator applications (like Google Authenticator or Authy) and receive the exact same error, the issue is typically rooted in the server-side Microsoft 365 or Azure AD configuration rather than a malfunction of the app itself.
How long does it take for administrator MFA policy changes to take effect?
Changes made by an administrator to Azure AD authentication methods or Conditional Access policies can take anywhere from a few minutes to a few hours to fully propagate across all Microsoft 365 services.
