̽»¨´óÉñ

MacOS devices can be enrolled in only one Mobile Device Management (MDM) provider. You can use a non-̽»¨´óÉñ MDM provider to onboard macOS devices. 

If you prefer to use a non-̽»¨´óÉñ MDM provider, you can create a zero-touch macOS onboarding workflow by pairing the ̽»¨´óÉñ directory with a non-̽»¨´óÉñ MDM solution: 

• Zero-touch macOS onboarding workflows that leverage the ̽»¨´óÉñ directory let you fully automate onboarding, set up, and configuration of macOS devices and the user accounts provisioned to these devices.
• You can pre-stage settings for onboarding macOS devices within MDM and pre-stage settings and resource access for new users in the ̽»¨´óÉñ directory.
• Local device and ̽»¨´óÉñ user accounts can activate during the device onboarding process, which leads to time savings and efficiency gains for IT teams.
• For devices running macOS Monterey and later, you’ll need to configure a Privacy Preference Policy Control (PPPC) profile to let ̽»¨´óÉñ apps access certain files used for system administration, and allow access to application data. For more detail on this type of privacy preference, see Apple’s .

The MDM solution described in this article is not a ̽»¨´óÉñ MDM server. ̽»¨´óÉñ offers an extensible MDM workflow that leverages a custom PKG, which must be created and signed with an Apple Developer account by the ̽»¨´óÉñ admin. This PKG installs the ̽»¨´óÉñ agent after MDM enrollment and provides end users with a tailored onboarding experience. For instructions, see .

Before you install the ̽»¨´óÉñ agent on a device running macOS Monterey 12 or newer, you’ll need to install a PPPC profile for ̽»¨´óÉñ. Use the settings described in Granting permissions for a device that is not enrolled in MDM in Grant Full Disk Access Permissions to the ̽»¨´óÉñ Agent for MacOS.