Skip to main content
Question

Jamf Connect Login With Microsoft EntraID OTP fails but push notification works

  • February 20, 2026
  • 2 replies
  • 93 views

Hey all - Ran into a thing that has been mentioned before, but it was a year ago and a few Jamf Connect login versions ago. We are now up to 3.6

 

Had a user who had their Microsoft Authenticator switch from sending them push notification to enter a number to requiring her to enter the 6 digit number. 

She would get the Jamf Connect Login window and enter her MS login, PW and the 6 digit 2FA code. The Jamf Connect Login window would stay up, but load her profile page. She would also see an error that password needed to be at least 7 characters, and contain one number and one alphanumeric character.

 

It took me a VERY long time (and a computer wipe) to figure out that it looks like the Jamf Connect login window is passing that 6 digit number to the OS for login instead of the users Password. 

 

Once we reset her Authentication Methods in EntraID so that the push notification workflow returned, her login issues on her laptop went away. 

 

Has anyone else run into this before? If so is there a setting in my config profiles or policies that I can set that will address thatm or is this a bug in how Jamf Connect Login acts? I’m submitting to Jamf regardless.. but I was alos hoping to get some verification that I’m not crazy.. :) 

 

~Mark

2 replies

nporta
  • New Contributor
  • March 19, 2026

I also experienced the same thing, and lost almost a full day debugging it, until i figure it out.

It started happening after updating jamf connect login to 3.7.0, before that it was working just fine. 


Forum|alt.badge.img+3
  • New Contributor
  • March 27, 2026

You’re not crazy — I’ve seen the same “6‑digit OTP gets treated like the macOS password” failure mode, and the password complexity pop-up is just macOS reacting to that short numeric string.

In practice the only stable mitigations I’ve found are:

  • force users back to a push / number-match flow (as you did), or
  • roll back / hold at the last known-good Jamf Connect Login version until Jamf ships a fix.

If you need a quick explainer for why macOS throws that specific “min length / alphanumeric” message, this is a handy reference: Apple Password Policy