I’ve read most documentation and searched the forums but I’m having trouble finding out how devices that are assigned to users are kept assigned to users during and after the migration. We have 1200 Mac devices and about 4k ipads that need to keep their assigned user during the migration. We plan to use the migration tool in Jamf Pro.
Currently we are using LDAP Username and not email for the user assignment. However each user has an email brought in as well. Should we update LDAP values first in order to make the transition? Would it be better to use the API to pull all devices and users, do the migration, then put them back with new usernames?
Any insight into the migration tool and things to look out for also welcome.
Question
Jamf Pro LDAP to Azure Migration for user assigned devices
+1
+24They’ve made this transition WORLDs easier in recent years. The only thing you need to validate is your user mappings and attributes. We do some different stuff at my org, so we had to use some sketch stuff to make it work, but it’s doable. If your setup is more vanilla, then it should be an easier approach.
+36Migration expects you’re syncing your local Active Directory to Entra ID and have the same users and groups structure in both places.
All the migration assistant does is switch the pointer in the Jamf Pro database from “Active Directory” to “Entra ID” and the rest of the directory structure for each user and group object remains the same.
You can start the migration assistant and verify a lot of your mapped users and groups without having to commit to the migration at that time. Only at the very end, when you’re ready, will you commit to the migration.
If you don’t have a Jamf Cloud sandbox instance for testing, you may want to reach out to Jamf Customer Success and request one.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.