Start Jamf device registration from Self Service, not Company Portal

Source facts

Microsoft’s Jamf Device Compliance guidance directs users to the registration policy in Jamf Self Service. Starting registration through the deployed Company Portal app instead produces AccountNotOnboarded. Jamf-managed devices in this integration do not appear in Intune’s device list. After registration, their initial Entra state is noncompliant; Jamf’s configured compliance smart group supplies the subsequent status through the connector. Microsoft Learn.

Applicability

Use this distinction for Jamf Pro Device Compliance integration, not the older Conditional Access integration. Confirm the intended registration policy, applicable users, connector assignment, and compliance smart group before sending onboarding instructions.

DSE recommendation

Write the user handoff around the exact Self Service policy and its approved description. Treat Company Portal installation as a separate preparation item, not the instruction to launch registration. Give the support desk a decision path that distinguishes a wrong entry point from an incomplete registration or missing compliance-group membership. Avoid directing users through repeated registration attempts without identifying which path they used.

Verification

On an approved pilot Mac, follow the documented Self Service policy and inspect the resulting Entra device record. Check the user’s connector-scoped group and the device’s compliance smart-group membership when the expected state does not arrive. Record the entry point and observed status transitions. Do not search only the Intune device list or infer a failed integration solely from the initial noncompliant state.

Official references

Microsoft Learn: Jamf Managed Device Compliance with Microsoft Entra ID.