{"id":75625,"date":"2023-06-05T13:09:40","date_gmt":"2023-06-05T17:09:40","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=support&p=75625"},"modified":"2023-06-06T16:57:29","modified_gmt":"2023-06-06T20:57:29","slug":"implement-a-zero-touch-macos-onboarding-workflow-using-jumpcloud-and-a-non-jumpcloud-mdm-provider","status":"publish","type":"support","link":"https:\/\/jumpcloud.com\/support\/implement-a-zero-touch-macos-onboarding-workflow-using-jumpcloud-and-a-non-jumpcloud-mdm-provider","title":{"rendered":"Implement a Zero-Touch MacOS Onboarding Workflow Using JumpCloud and a Non-JumpCloud MDM Provider"},"content":{"rendered":"\n
MacOS devices can be enrolled in only one Mobile Device Management (MDM) provider. You can use a non-JumpCloud MDM provider to onboard macOS devices. <\/p>\n\n\n\n
If you prefer to use a non-JumpCloud MDM provider, you can create a zero-touch macOS onboarding workflow by pairing the JumpCloud directory with a non-JumpCloud MDM solution: <\/p>\n\n\n\n
The MDM solution described in this article is not a JumpCloud MDM server. JumpCloud offers an extensible MDM workflow that leverages a custom PKG, which must be created and signed with an Apple Developer account by the JumpCloud admin. This PKG installs the JumpCloud agent after MDM enrollment and provides end users with a tailored onboarding experience. For instructions, see JumpCloud MDM PreStage user enrollment workflow<\/a>.<\/p>\n\n\n\n Before you install the JumpCloud agent on a device running macOS Monterey 12 or newer, you\u2019ll need to install a PPPC profile for JumpCloud. Use the settings described in Granting permissions for a device that is not enrolled in MDM<\/strong> in Grant Full Disk Access Permissions to the JumpCloud Agent for MacOS<\/a>.<\/p>\n\n\n\n