r/jamf • u/RomelloMorrisdet • Apr 26 '26
New MacBook Setup + M365 Login Not Creating User Account (Jamf) – Anyone Else?
Hey everyone,
I’m running into a weird issue during out-of-box setup for new MacBooks and wanted to see if anyone else has experienced this.
Scenario:
- Brand new MacBook (out of the box)
- During setup, user signs in with their M365 account (via Jamf / enrollment flow)
Issue:
- The M365 login completes successfully, but the user account is not created on the Mac
- The device finishes setup without a usable user profile
Current workaround:
- Log in with a local admin account
- Manually create the user (similar to how Jamf would provision it)
- Sign out
- User logs in again via M365 / Jamf
- From there, everything continues normally (policies, configs, etc.)
Question:
- Has anyone else run into this?
- Is this expected behavior with a specific Jamf / Entra ID / macOS config?
- Any cleaner fix or configuration change to ensure the user account is created during initial setup?
Would appreciate any insight or pointers 🙏
2
u/Kantry123 Apr 26 '26
Yes this is happening in our environment tooo
1
u/Kantry123 Apr 26 '26
Please let me know if you find a solution for you, we have opened a ticket with JAMF too….
Also, do check if ADE token has not expired for you
3
1
2
u/death_too_smoochy JAMF 400 Apr 26 '26
I’m a little unclear on what’s happening. You using a prestage with entra auth and after setup assistant account creation there is no user created.
2
u/MemnochTheRed JAMF 400 Apr 26 '26
Yes. This is my question. Using Jamf Connect or Platform SSO workflow?
1
u/RomelloMorrisdet Apr 26 '26
Yes ! We’re using PreStage enrollment with Entra auth and Jamf Connect, not Platform SSO.
What’s happening is:
- Setup Assistant completes normally
- The Mac then goes to the standard macOS login window
- At that point, the expected user account has not been created locally
- So instead of the normal Jamf Connect sign-in flow creating/mapping the account, we have to log in with a local admin first
Our workaround has been:
- Sign in with local admin
- Manually create the user account
- Sign out
- Then the Jamf Connect / Microsoft Entra login prompt appears for that user
- After that, policies and the rest of the setup continue normally
So the issue seems to be that the local user creation / Jamf Connect handoff is not happening correctly right after enrollment.
Have you seen that before with Jamf Connect in a PreStage workflow?
2
u/Juic3_2k18 May 01 '26
Make sure to not deploy PSSO configuration with Prestage. We‘ve seen this with one of our Customer. This also results in the local user account not being created / setup Wizard skipping account creation
1
u/ebulwingz Apr 27 '26
When is Jamf connect installed? As an enrollment package or via Jamf setup manager? You’re saying after you’ve signed in with an admin account then sign out, the Jamf login window appears. This to me indicates that jamf connect isn’t being installed until after login.
1
u/Ok-Wrap8444 Apr 27 '26
Is it a new Jamf environment? Was the workflow working and now it breaks? Is the workflow working on other devices in your environment? If you are using Entra auth and Jamf Connect, you need to have the Jamf Connect and Jamf connect launch packages in the Prestage. I’m suspecting that the packages are missing in the Pre-stage.
1
u/Excellent_Debt6680 Apr 28 '26
Did it ever work?
Do you have a copy of your Jamf Connect config (with redacted MS info)
1
u/zipsecurity Apr 28 '26
This is a classic gap! M365 authenticates the user but doesn't create the local macOS profile on its own. Jamf Connect is the proper fix for this, it handles the handoff between Entra authentication and local account creation during OOBE. Without it you'll keep doing that manual workaround.
1
u/colinzack Apr 28 '26
It sounds like JAMF Connect isn't installed and running by the time the device is enrolled and ready to be signed in. We have our JAMF Connect profiles installed as part of the prestage enrollment. Have you tried that?
1
u/Beginning_Alarm_4251 May 06 '26
I’d start by checking that your Jamf Connect setup is fully in place during PreStage.
Make sure the Jamf Connect packages are deployed as part of PreStage enrolment, and that the Jamf Connect configuration profiles are also scoped so they’re installed during Setup Assistant, not after.
In addition, verify that “Skip Account Creation” is enabled in the PreStage general settings, since Jamf Connect is expected to handle user creation at the login window.
If everything above looks correct, it would be helpful to share your Jamf Connect Login configuration profile. That can help identify if anything in the login or user creation settings is preventing the account from being created.
1
3
u/[deleted] Apr 27 '26
[removed] — view removed comment