Verifying correct JAmf Connect install end state via intune

[arnolyuna]

Using ABM, Intune and Jamf Connect, things are happy and deploying I think correctly but could use a second opinion on the Connect installation.

On first boot, Mac os laptops ask to sign in via SSO (Azure AD), then it still asks me to create a local account. That local account once all the config profiles and Jamf menu bar install get back ground synced and the password to log into laptop becomes the AzureAD passwords. Jamf Connect is registered to correct user in menu bar etc after signing in once local user is created. Is this correct? should we still have to create a local user?

[bwoods]

Keep doing this the way you are doing it now. If you skip account creation and let Jamf Connect create the account, you lose the ability to deploy user level configuration profile and the first account created loses volume ownership and the secure token.

[bwoods]

This is a jamf document, but it describes what happens when you skip account creation. 

MDM-Enabled Local User Accounts - Jamf Pro Administrator's Guide | Jamf