Hey all,
We’re currently testing Jamf Connect Login as part of a move to improve our remote deployment process.
We haven’t previously used Jamf Connect at login. Currently, devices enrol via ADE, IT enters the user’s name and password, and setup begins with macOS Onboarding. This then installs the Jamf Connect menu bar app for password syncing, which works well - but we’re aiming for a more seamless experience, especially when sending laptops directly to staff. The goal is to let users authenticate directly with Entra ID (Azure AD) during setup, allowing the account creation process to be automated, reduce mistakes, and speed things up.
After that first login, we’d like the Mac to:
-
Revert back to the native macOS login window
-
No longer use Jamf Connect Login
-
Keep the Jamf Connect menu bar app (Self Service+) running for password sync, SSO token refresh, etc.
I’ve tested removing the config profile and LaunchAgent, which removes the settings — but the login window still shows “Powered by Jamf” unless I run:
/usr/local/bin/authchanger -reset
That fixes the login UI, but it seems to disable the menu bar unless and all config.
So I’m wondering:
-
Has anyone implemented a workflow like this?
-
Is there a best practice for cleanly switching back to native login after account creation?
-
Any risks in this setup? trying to avoid account corruption and just keep that good old 'Apple Mac' feeling on the devices, rather than a mobile account login.
Would love to hear how others are approaching this with Entra setups or any advice.
Thanks!
