JumpCloud experienced a notice incident on September 10, 2025 affecting Windows MDM, lasting 6h 33m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 10, 2025, 02:15 PM UTC
We are currently investigating an issue involving JumpCloud’s Windows MDM Service that is preventing device enrollment. We are investigating the cause of the issues currently, and will update the status event once an update is available.
- identified Sep 10, 2025, 02:49 PM UTC
We have identified the issue and are working on a fix.
- identified Sep 10, 2025, 02:57 PM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 10, 2025, 04:09 PM UTC
We're still implementing a fix for this issue. We will provide another update within the hour.
- identified Sep 10, 2025, 05:43 PM UTC
We are still working to implement a fix for this issue. We will continue providing regular updates.
- identified Sep 10, 2025, 07:02 PM UTC
We are continuing to work to implement a fix for this issue. During this time new Windows MDM device enrollments will continue to fail.
- monitoring Sep 10, 2025, 07:55 PM UTC
A fix has been implemented and we are continuing to monitor the results.
- resolved Sep 10, 2025, 08:48 PM UTC
This issue has been resolved and Windows devices are now able to successfully enroll in MDM.
- postmortem Sep 12, 2025, 06:38 PM UTC
 # Incident Report **Date**: Sep 13, 2025 **Date of Incident:** Sep 10, 2025 **Description**: **RCA for Windows MDM enrollment failures** **Summary:** On September 10, 2025, a number of customers experienced intermittent failures when attempting to enroll Windows MDM devices. User-led enrollments during this period would have seen an error message. **Root Cause:** Our MDM team was alerted to an issue with our MDM certificate issuance service, which affected the ability to enroll devices. This issue was caused by a configuration change in our backend infrastructure. The core problem stemmed from an update that inadvertently caused a critical service role to be deleted and immediately recreated. When this happened, our IaaS provider assigned the recreated role a new, unique ID. Our system, which was configured to recognize the old ID, was no longer able to access the necessary security keys. This caused certificate issuance to fail, causing the MDM enrollment failures. **Corrective Actions / Risk Mitigation:** 1. Implemented a permanent fix refactoring our infrastructure for this service - DONE 2. Refining our emergency response plan to securely restore services - IN PROGRESS 3. Updating our monitoring systems to proactively detect and alert on these types of issues, including reconfiguring our logging to ensure that critical errors are not missed - IN PROGRESS