Jamf incident
Self Service for iOS 11.4 prevents Device Compliance registration
Jamf experienced a major incident on November 5, 2025, lasting 14h 59m. The incident has been resolved; the full update timeline is below.
Update timeline
- identified Nov 05, 2025, 11:25 PM UTC
Details: Customers using Device Compliance with Jamf Pro on iOS may see registration fail on devices running Self Service 11.4. Current Actions: We have halted the phased release of 11.4, are verifying update/distribution paths, and are preparing a corrected build to restore registration on affected devices. Impact: Device Compliance registration on iOS for devices running Self Service 11.4. We appreciate your patience and are committed to resolving this as swiftly as possible.
- identified Nov 06, 2025, 01:28 AM UTC
Jamf engineering has identified the issue and is working towards service restoration. We have submitted a new build of Self Service for App Store approval and requested expedited review. Currently impacted customers should contact Jamf Support if more immediate remediation required.
- identified Nov 06, 2025, 03:47 AM UTC
We’ve submitted a fixed version of Self Service 11.4.1 to Apple for App Store approval and have requested expedited review. We’re currently awaiting approval and do not yet have an ETA for release. We will update this post as soon as the new version becomes available. Customers leveraging Device Compliance and managing iOS devices should disable any automatic app update workflows to prevent Self Service from updating to version 11.4. We appreciate your patience and will continue to provide updates as new information becomes available.
- identified Nov 06, 2025, 08:00 AM UTC
We are awaiting approval of Self Service 11.4.1, and have requested expedited review. We do not yet have an ETA for release, though will update this post as soon as the new version becomes available. Customers leveraging Device Compliance and managing iOS devices should disable any automatic app update workflows to prevent Self Service from updating to version 11.4. We appreciate your patience and will continue to provide updates as new information becomes available.
- monitoring Nov 06, 2025, 10:23 AM UTC
Earlier today, we identified an issue in Self Service version 11.4 that could cause registration failures when using Device Compliance with Jamf Pro on iOS. This issue was isolated to version 11.4. To resolve this, version 11.4 has been removed and replaced with Self Service 11.4.1, which is functioning as expected. We recommend ensuring that devices are now running Self Service 11.4.1, which is available as of 9:27 UTC. If you continue to experience any problems, please reach out to Jamf Support for further assistance.
- resolved Nov 06, 2025, 02:25 PM UTC
PRELIMINARY INVESTIGATION STATEMENT Incident Start Date and Time: 11/5/2025 11:18 PM UTC Incident End Date and Time: 11/6/2025 09:21 AM UTC Duration: 10h 3m Symptoms: Failed registration on devices running Self Service 11.4. Following recent architectural improvements to the iOS Self Service 11.4 application, a device compliance functionality experienced partial outage resulting in failed registration on devices running Self Service 11.4. This issue was not identified during standard regression or beta testing. A detailed root cause analysis will be published once we have completed our internal investigation. We apologize for any inconvenience this caused our customers.
- postmortem Nov 20, 2025, 02:21 PM UTC
**Incident Summary** **–** Post-Incident Review **Detailed Root Cause Analysis Report: Device Compliance Broken in iOS Self Service 11.4.0** **Incident Start Date and Time \(in UTC\):** Nov 5, 5:46 PM UTC **Incident End Date and Time \(in UTC\):** Nov 6, 9:21 AM UTC **Severity: SEV2** **Duration: 15h 35m** **Impact:** Global disruption of Microsoft Device Compliance workflow for users using iOS Self Service 11.4.0. **Summary** On 11-05-2025 a release of iOS Self Service 11.4.0 broke the Microsoft Device Compliance workflow. Impacted users could not access resources protected by Microsoft Device Compliance policies. **Root Cause & Timeline** * **Root Cause:** Incorrect configuration of keychain access group in production release of iOS Self Service 11.4.0 * **Key Events:** * November 5, 5:46 PM UTC - Self Service 11.4.0 was released * November 5, 9:50 PM UTC - Issue with Device Compliance worfklow in Self Service 11.4.0 was escalated to Jamf * November 6, 12:18 AM UTC - Self Service 11.4.1 was submitted to Apple for expedited review * November 6, 9:21 AM UTC - Self Service 11.4.1 is available for all customers and users **Business & User Impact** * Users unable to access internal company resources protected by Microsoft Device Compliance policies. * Affected Capabilities: Device Compliance **Gaps Identified** * Gap in automated and human-driven release testing coverage. **Remediation & Next Steps** · The functionality was restored with a new release of iOS Self Service 11.4.1 that reverted the changes introduced in 11.4.0. · Test automation and human-driven release test case coverage was extended to cover the affected workflow end-to-end.