Hi,
Jamf can talk back to your internal LDAP, this is normally setup to use an LDAP Proxy and the Jamf Infrastructure Manager.
Using LDAP allows you to let users login to Jamf Pro with their AD credentials and assign devices to users in AD.
The LDAP connection between Jamf Pro and Active Directory does not let you login to the Macs.
You would need to bind the machines to your domain and they need to be local.
That being said......you can use Jamf Connect to create local accounts based on your credentials from your IDP (Azure, OKTA etc). You can even have Jamf Connect sync password back to AD via ADFS.
Hope this makes sense
Simon
You want to use AD credentials to log in to your managed Macs? Is that right?
You can take a look at NoMAD and NoMAD Login. NoMAD allows a Mac user to authenticate to AD and get a Kerberos ticket. Add NoMAD Login, which replaces the native Mac login method, and you get a login method that is similar to AD login on Windows.
We use the combination to allow students to log in to computer labs, and are expanding adoption for our one to one assigned computers. We do not bind our Macs to AD, so NoMAD + NoMAD Login has given us the ability to set up computers before we know who is going to receive them, and to control the type of account a user will get when they log in for the first time and their profile is created.