Support tip: Transitioning Jamf macOS devices from Conditional Access to Device Compliance

Updated 08/15/24 – The end of support date for the legacy Jamf Pro Conditional Access feature has been extended to January 31, 2025. We encourage you to start migration now to ensure there are no blocking issues.

Microsoft Intune has been working with Jamf  to make it easier for Jamf Pro users to transition macOS devices from Jamf Pro’s Conditional Access integration in Intune to the newer Device Compliance integration in Intune. As also communicated under MC671804, we’re sharing this awareness on behalf of Jamf to assist customers during the transition. The Device Compliance integration uses the newer Intune partner compliance management API, which involves a simpler setup than the partner device management API and brings macOS devices onto the same API as iOS devices managed by Jamf Pro. The platform Jamf Pro’s Conditional Access feature is built on will no longer be supported after January 31, 2025.

A migration path to Device Compliance is now available for all of these environments. If you have questions, contact Jamf Customer Success.

• Jamf Pro environments hosted in Jamf Cloud, including Jamf Cloud Premium Plus.
• Jamf Pro on-premises deployments.
• Microsoft 365 Government Community Cloud (GCC) and GCC High.

In Jamf Pro 11.7, an issue (PI119904) related to internal proxies was identified that might prevent some customers from migrating from Jamf Pro Conditional Access to Jamf Pro Device Compliance. This issue will be resolved in Jamf Pro 11.9, and this fix is available to test in the 11.9 beta. Customers who are not using an internal proxy are not blocked and should proceed with their migration. You can go to Jamf’s Known Issues page for more information about PI119904. 

How to prepare for the transition

If you’re using Jamf Pro’s Conditional Access integration for macOS devices, follow Migrating from macOS Conditional Access to macOS Device Compliance – Jamf Pro Documentation to transition your devices to Device Compliance integration.

After the Device Compliance integration is complete, some users may see a one-time prompt to enter their Microsoft credentials.

If you need additional help with the transition, contact Jamf Customer Success.

More information can be found in Jam's blog: Conditional Access deprecation update (jamf.com)

Post updates:
08/31/23: Updated to include reference to MC671804.

09/08/23: Updated to include Jamf's: Conditional Access deprecation update (jamf.com) blog post.

04/25/24: Updated to note Jamf plans to provide a migration path for the three environments that cannot be initially transitioned.

06/24/24: Jamf Pro 11.6, released on June 11, 2024, now supports Device Compliance for on-premises environments.

08/05/24: Updated to note that a migration path to Device Compliance is now available for a few environments.

08/15/24: The end of support date for the legacy Jamf Pro Conditional Access feature has been extended to January 31, 2025.