Azure portal sign-in fails with error 500121 — Authenticator TOTP code rejected despite valid 6-digit code

Bob Archer 0 Reputation points
2026-04-08T02:45:59.0433333+00:00

Problem

When signing in to the Azure portal (portal.azure.com) with my personal Microsoft account (******@live.com), the Microsoft Authenticator app displays a valid 6-digit TOTP code, but entering it returns: "You didn't enter the expected verification code."

Important: Sign-in to all other Microsoft services works normally — Outlook, Office 365 apps, account.live.com, and support.microsoft.com all accept authentication without issue. The MFA failure is isolated to Azure portal sign-in only.

Error Details

  • Account: PII
  • Error Code: 500121
  • Error Message: "You didn't enter the expected verification code."
  • Request Id: cfdf54f4-81ee-41a6-8cf0-574eb81e0900
  • Correlation Id: 019d64c5-acc6-7e49-a541-6ba358f96afa
  • Timestamp: 2026-04-06T21:52:51Z (UTC)

Troubleshooting Already Completed

  1. Synced time on phone and PC (verified against NTP source)
  2. Re-registered Authenticator via account.live.com/proofs/manage
  3. Tried incognito/private browser mode
  4. Tested multiple browsers (Edge, Chrome, Firefox) and multiple devices
  5. Disabled VPN/proxy
  6. Tried SMS and email fallback verification
  7. Verified notifications, background refresh, and app version are current
  8. Removed all passwordless sign-in entries and re-added Authenticator as standard TOTP app

None of these resolved the issue.

Request for Microsoft Support

I am requesting that Microsoft:

  1. Run a backend trace using the Request Id and Correlation Id above to identify the exact TOTP validation failure point
  2. Check for Conditional Access or risk policy blocks that may be interfering with Azure sign-in specifically while allowing other services
  3. Investigate backend replication issues — possible mismatch between the TOTP secret registered on the account and the one used by the Authenticator app
  4. Audit the account state for mismatches between passwordless and TOTP registrations that may cause Azure's verification engine to expect a different credential type
  5. Restore Azure access for this account
  6. Escalate to the Account/MFA Engineering Team if neededI have screenshots
Microsoft Security | Microsoft Entra | Microsoft Entra ID

1 answer

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-04-08T02:46:33.8133333+00:00

    Error 500121 with the message “You didn't enter the expected verification code” indicates that Microsoft Entra multifactor authentication is not accepting the verification response that’s being provided.

    From the available information, the supported remediation steps are:

    1. Confirm that the correct verification code is being entered and that it is current for the time window. If using Microsoft Authenticator or another TOTP app, ensure the displayed code is typed exactly as shown before it changes.
    2. If using the Microsoft Authenticator app with push notifications, make sure Verify is selected on the notification screen and not Cancel. Selecting Cancel causes the “expected response” error.
    3. If the current method continues to fail, switch to another verification method during sign-in by choosing Other verification options (for example, SMS or a different registered method) and complete sign-in that way.
    4. If multiple failed attempts have occurred, Microsoft Entra multifactor authentication may temporarily block additional attempts as unusual activity. In that case, wait before trying again, or use a different MFA method. If there is concern about malicious activity, an administrator should review Microsoft Entra sign-in logs.
    5. If none of the above resolves the issue, contact the organization’s help desk or a Microsoft Entra ID administrator so they can investigate the sign-in logs and, if needed, reset MFA registration for the affected account (for example, by requiring re‑registration of MFA so that new methods can be configured).

    Backend traces, tenant-level policy review, and engineering escalation can only be performed by Microsoft support or a tenant administrator through official support channels; these actions are not available directly from documentation.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.