A cloud-based identity and access management service for securing user authentication and resource access
The screenshot shows the Azure sign-in page reporting that the verification code is incorrect, even though the same code is being used from the authenticator app. This behavior matches a stuck or mismatched Azure Multi-Factor Authentication (MFA) registration for the account.
For personal Microsoft accounts used to access Azure, this typically has to be fixed by resetting the MFA registration for the user from within the tenant where the account is being used.
A working pattern from similar cases is:
- Sign in to the Azure tenant with another account that has Global Administrator rights (this can be a newly created admin account in that tenant).
- In the Microsoft Entra admin center, go to Identity → Users → All users.
- Select the affected user account.
- Open Authentication methods.
- Select Require re-register MFA.
- Sign in again with the affected personal account; Azure will prompt to register MFA again and a new authenticator method can be configured. After re-registration, the new codes should be accepted and sign-in should succeed.
If there is no other Global Administrator in the tenant, this must be escalated to Microsoft Support (Data Protection / Tenant Recovery) so they can verify ownership and reset the MFA registration for the account.
References:
- Reset Personal Azure MFA - Microsoft Q&A
- Global Admin Locked out - Microsoft Q&A
- "We did not receive the expected response" error message when you try to sign in by using Azure Multi-Factor Authentication
- "We didn't receive a response" error message when you try to sign in by using Azure Multi-Factor Authentication