Jamf Incident History

The issue has been resolved. The Jamf Trust app will no longer be unexpectedly deactivated on devices. Remaining Customer Impact: For Jamf Trust apps that had been previously deactivated, they will need to be reactivated. Depending on deployment configuration this may be automatic or require manual reactivation. For assistance with reactivating devices, please login to the Jamf Account portal and create a ticket (Contact Support) referencing Jamf Trust app deactivation. While the Jamf Trust app is deactivated, its protections — including Zero Trust Network Access (ZTNA) and content filtering — are not enforced. This affects devices on all platforms: iOS, macOS, Android, and Windows. We apologize for any inconvenience.

The fix in production continues to hold, and no additional devices are being affected. We are still compiling the list of impacted customers and preparing the remediation instructions for devices where the Jamf Trust app was deactivated.

A fix is now in production and has stopped the issue from spreading, so no additional devices will be affected. Devices where the Jamf Trust app was already deactivated may not be resolved automatically — some may recover on their own, but others will require additional remediation steps. We are compiling a report of impacted customers and are working to reach affected accounts directly with step-by-step instructions to reactivate their devices and restore protections, including Zero Trust Network Access (ZTNA) and content filtering. We will also post those instructions here so they are available to everyone affected.

We are aware of an issue causing the Jamf Trust app to be deactivated on customer devices. While the app is deactivated, its protections — including Zero Trust Network Access (ZTNA) and content filtering — are not enforced. This affects devices on all platforms: iOS, macOS, Android, and Windows. Our engineering team has identified the cause and fix is being deployed to production. Once the fix is live, affected devices will need to be reactivated, which may require end-user or administrator action. We will post more details here as soon as the fix is confirmed.