Please confirm:
Problem Statement
For Apple Automated Device Enrollment, CIPP can list, sync and delete enrollment profiles (ListAppleEnrollmentProfiles, ExecSyncDEP, ExecRemoveEnrollmentProfile). It cannot create one, assign it or set it as default, and there is no standard or baseline definition for it.
What we ask: deploy a macOS ADE enrollment policy from CIPP, with its settings stored once (as a standard or baseline definition), assign it to the token's devices and set it as the token's default policy.
Benefits for MSPs
Every Mac bought through Apple Business Manager gets its first-run experience from this policy. Today it is built by hand in every tenant, and CIPP cannot tell whether it exists or matches. One definition would remove that manual step and make the difference visible, the same way CIPP already creates the Autopilot profile for Windows through the AutopilotProfile standard.
Value or Importance
Important for any MSP that onboards Macs through Apple Business Manager. Configuration profiles and compliance already deploy from CIPP; the enrollment policy is the remaining manual step. Building it on Enrollment policies rather than on the legacy profiles avoids shipping a feature on an object Microsoft is retiring.
Please confirm:
Problem Statement
For Apple Automated Device Enrollment, CIPP can list, sync and delete enrollment profiles (ListAppleEnrollmentProfiles, ExecSyncDEP, ExecRemoveEnrollmentProfile). It cannot create one, assign it or set it as default, and there is no standard or baseline definition for it.
What we ask: deploy a macOS ADE enrollment policy from CIPP, with its settings stored once (as a standard or baseline definition), assign it to the token's devices and set it as the token's default policy.
Benefits for MSPs
Every Mac bought through Apple Business Manager gets its first-run experience from this policy. Today it is built by hand in every tenant, and CIPP cannot tell whether it exists or matches. One definition would remove that manual step and make the difference visible, the same way CIPP already creates the Autopilot profile for Windows through the AutopilotProfile standard.
Value or Importance
Important for any MSP that onboards Macs through Apple Business Manager. Configuration profiles and compliance already deploy from CIPP; the enrollment policy is the remaining manual step. Building it on Enrollment policies rather than on the legacy profiles avoids shipping a feature on an object Microsoft is retiring.