Notice History by Release - Jamf Pro Release Notes 11.15.0

In an update to Jamf Pro 11.14.0, the Cloud Services connection was changed to be enabled by default if you are subscribed to a Jamf Standard Cloud-hosted or Jamf Premium Cloud-hosted environment. This means you no longer need to manually enable the Cloud Services connection.

To view your connection status, navigate to Global > Cloud services connection.

Additionally, the Update Credentials and Enable buttons have been removed from Jamf Pro. If you are experiencing connection issues, contact Jamf Support.

Apple announced upcoming changes to the Apple Push Notification service (APNs) Certificate Authority (CA). Organizations using APNs will be required to update their application's trust store to include the new server certificate before 24 February 2025 to prevent communication disruption.

For cloud-hosted environments, the root certificate is already trusted and validated.

For on-premise environments, you may need to download and install the new SHA-2 Root USERTrust RSA Certification Authority certificate to your server's certificate trust store if it is not already trusted on your hosting infrastructure. For more information, see How to Download & Install Sectigo Intermediate Certificates - RSA documentation from Sectigo per Apple's announcement.

Apple has a test server available to allow organizations to send push certificates to verify the correct certificate installation. For more information, see this documentation from the Apple Developer website.

As of 13 December 2024, Jamf Pro no longer supports the legacy binary protocol option for Apple Push Notification service (APNs) communication. Jamf requires the HTTP/2 protocol for your push notification certificate. If you have not transitioned to the HTTP/2 protocol by 13 December 2024, remote management commands, configuration profiles, applications, and push certificates will no longer work. For more information, see the Supporting Apple Push Notification Service (APNs) Over HTTP/2 article. For assistance, contact Jamf Support.

Microsoft has recently reviewed and lowered the permissions required for the Graph API endpoints that Jamf Pro uses for the Entra ID integration. Jamf Pro no longer requires the Group.Read.All permission to enable the Entra ID integration.

You can continue using the Entra ID integration with the original permissions granted, or you can remove the Group.Read.All permission. To remove the Group.Read.All permission, navigate to Settings > System > Cloud identity providers and click your Entra ID identity provider from the list to open the integration page. On the integration page, click Refresh Consent.