We're actual testing the migration of existing MacOS User Accounts with Jamf Connect and Azure AD. On two devices we noticed that the migration screen was skipped without asking the user which account should be linked to his Azure AD account. Instead a complete new MacOS user was created? Sadfully I wasn't able to catch the Jamf Connect Logs before the next restart was executed.
I wasn't able to reproduce the error in a testing VM. Tried it several times.
The original usernames on the devices were:
New usernames created by jamf connect were:
Jamf Connect 2.4.0
Jamf Pro 10.29.2
Issue occured at 10.15.7 and 11.4.0 Other testing devices and their corresponding users with the same configuration profile were migrated without any issues.
Does somebody have an idea what could be wrong?
Did you ever find a resolution for this? We are in the process of converting our user base and have 2 users with this same issue post conversion. We are running Jamf Connect 2.5.0 and Jamf Pro 10.30.1. Same users can log in to any other machine and migrate their profiles without issue.