Skip to main content

172: Evaluate macOS management with Intune + JAMF

Implementation Effort: High
User Impact: Low to Medium

Overview​

Some organizations use Jamf Pro for deep macOS lifecycle management while relying on Microsoft Entra ID, Intune, and Conditional Access for identity, access, and compliance-driven resource protection. The integration should be evaluated as an intentional architecture choice, not merely as a way to delay management standardization.

For Zero Trust, the key question is whether the combined design produces trustworthy device identity, timely compliance information, and supportable operational ownership across the Apple and Microsoft admin teams.

Implementation Guidance​

Evaluate whether a dual-tool model is justified​

  • Use Jamf plus Intune only when there is a clear operational or feature reason, such as existing Jamf investment, specialized macOS workflows, or a staged migration.
  • Define which platform owns enrollment, configuration, app deployment, compliance state, and support workflows so administrators do not make conflicting changes.
  • Map the desired device trust signal into Microsoft Entra Conditional Access before implementation begins.

Implement the integration carefully​

  • Configure Jamf Pro and the Microsoft integration according to current vendor guidance so devices register correctly with Microsoft Entra ID and can contribute compliance signals.
  • Deploy Company Portal or other required components only where they are actually needed for the chosen integration pattern.
  • Pilot certificate, SSO, and app access paths with real users to ensure compliance decisions arrive in time and do not produce authentication loops.

Govern the ongoing model​

  • Establish joint operational ownership for connector health, certificate rotation, device registration issues, and Conditional Access failures.
  • Review whether Intune has reached feature parity for your use cases often enough that the long-term need for dual management can be reassessed.
  • Keep app and security policy duplication to a minimum so troubleshooting remains straightforward.

Reference​