A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Set the phone’s date, time, and time zone to automatic, restart it, and then test the code shown specifically under the Availity entry in Microsoft Authenticator.
Correct the code synchronization
Authenticator codes depend on an accurate device clock; even a small difference can make a newly generated code invalid.^1^
- iPhone: Open Settings → General → Date & Time, then enable Set Automatically.
- Android: Open Settings → System → Date & time (the path varies by manufacturer), then enable automatic date/time and automatic time zone.
- Restart the phone.
- Confirm the computer used to access Availity also shows the correct time and time zone.
- Restart the Availity sign-in process and enter the current code.
Since waiting for another 30-second code did not help, repeatedly waiting for additional codes without correcting the clock is unlikely to change the result.
Verify the Availity enrollment
Microsoft Authenticator can hold separate code generators for several services. Each code is unique to the service enrollment, so select the entry created from Availity’s QR code—not a Microsoft work, school, or personal account entry. Availity’s setup process requires enrolling the authenticator using an Availity-generated QR code.^2^
Do not delete the existing Availity entry yet. Removing it without first resetting the enrollment can leave you unable to generate a code that Availity accepts.
If it remains invalid
If the phone was changed, Authenticator was reinstalled or restored, or the Availity entry was re-added, the app’s enrollment may no longer match the one stored by Availity. Ask your organization’s Availity administrator to reset your two-step authentication and provide a new Availity QR code for re-enrollment.^3^
If an Availity administrator is unavailable, submit a login/access request through Availity Customer Support.^4^ Microsoft cannot reset this particular MFA enrollment because Availity, rather than the Microsoft account system, controls it.
References