Additional Microsoft Entra services and features related to identity, access, and network security
The error indicates that the Authenticator app cannot find a valid account entry to complete MFA, so the sign-in flow is not completing.
Use the following steps to resolve it:
- Make sure the Authenticator app can complete sign-in
- Open Microsoft Authenticator directly and ensure the app is unlocked (no app lock/passcode screen blocking it). A locked app can prevent the entry box from appearing and cause an "Authentication did not complete"–type failure.
- Confirm that notifications for Microsoft Authenticator are enabled on the device and not set to silent/blocked. If notifications are silent or disabled, the prompt needed to complete MFA may not appear.
- Check device and app health
- Ensure the device has a working internet connection (try switching between Wi‑Fi and mobile data).
- Verify the device date and time are set correctly, preferably to automatic.
- Confirm that the latest version of Microsoft Authenticator is installed from the app store.
- Re-add the account cleanly
Because the app reports it cannot find an account to complete MFA, the existing entry is likely invalid or incomplete.
- In Microsoft Authenticator, remove the problematic work/school account entry (if one is present for this Azure login).
- Then, from a browser where the Azure account can at least start sign-in, follow the normal MFA registration flow again so that a new entry is created in Authenticator. If the browser sign-in is stuck because of the broken app registration, an administrator may need to reset MFA as described below.
- If sign-in still cannot complete
- If the sign-in keeps failing with messages like "Authentication did not complete" or similar, and re-adding the account in the app does not help, an administrator in the tenant should require re-register MFA for the user so that all MFA methods can be configured again from scratch.
- An admin can do this in the Microsoft Entra admin center by going to Identity → Users → [select user] → Authentication methods → Require re-register MFA, as described in the referenced guidance.
If there is no other global administrator in the tenant and this is a tenant lockout scenario, the issue must be escalated to Microsoft Support (Data Protection / Tenant Recovery) so they can help restore access and reset MFA registration.
References: