Credential verification failed because account is temporarily locked

[lensteruk]

I have a user on an M1 MacBook Air who has suddenly been getting the following message - credential verification failed because account is temporarily locked. We authenticate via 365 using JAMF Connect. I have checked on Azure (or whatever its new name is!) and the account isn't locked, I have sent a command via Unlock user account but no success -- any ideas ??

thanks in advance

Lenny

[jsommers]

We have also been having this Issue on one of our testing M1 MBPs. Did you ever end up finding a solution?

[lensteruk]

Jack

i am afraid i did not. I took the rapid and somewhat nuclear option of deleting the user account and when the user logged in via SSO a new account was created. If you find the cause I would be very interested to find out how to resolve this without having to delete the account. Good luck

[curtisklope]

I have a user that got this message a couple times, on the third try it worked and they got in...

We use Google for logging in to Jamf Connect, I'm wondering if maybe it was just a network issue...?

Anyone else still seeing this issue?

[jaredstulen]

Similar issue here.
Deploying Jamf Connect in our environment, Google as the IdP. After doing a migration on a previously deployed M2 MBP, the user forgot their password. After several failed attempts to login to the computer they remembered the correct password. They get the Google login window, authenticate with 2SV, but then the MacOS login window pops up with the following error "Credential verification failed because account is temporarily locked", and they are unable to get past it. User is on MacOS 15.3.2 and Jamf Connect 2.45.1 Any thoughts?