Troubleshooting the JamfAAD Pre-fill Authentication Issue

Technical Paper: Device Compliance with Microsoft Entra and Jamf Pro
Solution
Application
Content Type
Technical Documentation
Utilities & Services
ft:locale
en-US

The JamfAAD pre-fill feature introduced in Jamf Pro 10.14.0 may cause an issue (PI-007330) with the authentication experience in environments that use both the Microsoft Entra Integration and Active Directory Federation Services to authenticate to Azure.

This issue prevents users with pre-filled usernames from authenticating to Azure on the first attempt. The user must click Sign in with another account, then re-enter their login credentials to successfully authenticate.

To resolve this issue, upgrade to Jamf Pro 10.17.0 or later and complete the procedure below.

Note:

Upgrading to Jamf Pro 10.17.0 or later does not automatically fix the issue caused by PI-007330. You must complete the procedure below to resolve the authentication issue.

  1. Deploy the following .plist file to computers using a configuration profile with the Custom Settings payload configured:
    <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>disableUPNLoginHint</key>
<true/>
</dict>
</plist>
  2. When configuring the Custom Settings payload, enter the following in the Preference Domain field:

    com.jamf.management.jamfAAD