jamf | CONNECT : Do I still need a directory service set up in jamf | PRO?

Wouldn't you want it to do LDAP lookups for device records, scoping policies, and smart group creation?

But can't I get that info from the local jamfadmin installed on all devices that are enrolled?

This is what LDAP does for you.

Otherwise you need to create all the accounts manually in the JSS users section. I mean i guess you could write an API script that would take the user name and full name from the machine and enter it into the user section but it is simpler to just use LDAP services as you are already using them for Jamf connect. Is it some kind of security issue your worried about or do you just not want to setup an LDAP account in the JSS?

Hmm that makes sense.

Does this means that eventhough Azure AD with jamf | CONNECT doesn't require AD anymore for the endpoints, and is all cloud-based.
jamf PRO itself still requires on-prem DS as a general setup?

Ideally I want it all Cloud-based!

Yep. That's where I started actually. It was this article that made me wonder how far I would get if I didn't do this and let CONNECT and PRO do it all for me. But you made me realise that I will then loose the connection between the user services vs the device services.

Which is actually something to consider when you think about stuff like GDPR i think...

But thanks. I think you did give me the answer that I was looking for. It might not be the one I hoped for, but I still have learned something interesting and valuable.

I’m just jealous I wish my company could afford Jamf Connect. Good luck with everything.

Thank you. I now feel privileged to have jamf | CONNECT.