Hello Jamf Nation!
This post is to provide you with an update related to the Microsoft and Jamf Device Compliance integration and the Conditional Access deprecation timelines.
As of Jamf Pro 11.6 and 11.7.1, the Microsoft and Jamf Device Compliance integration can be fully leveraged in these environments.
- Jamf Pro environments hosted in Jamf Cloud, including Jamf Cloud Premium and 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.
- For a step-by-step guide on how to migrate from Conditional Access to Device Compliance for macOS, check out our Learning Hub article.
Last but not least, Microsoft and Jamf will be extending the Partner Device Management API (PDM) deprecation and removal date. To ensure all customers can successfully migrate, Conditional Access will now deprecate on 31 January 2025. Previous, release notes and documentation stated that Conditional Access would be deprecated 01 September 2024. If you have computers enrolled under the legacy Conditional Access integration, you must migrate the computers to the device compliance integration before the new deprecation date.
With this extension, we encourage admins to migrate as soon as possible to ensure you have adequate access to support.
Thank you,
Travis
Jamf Product Management