Skip to content

Incident detail

Windows MDM - Device Enrollment Failing

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time JumpCloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    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.

  2. Identified

    We have identified the issue and are working on a fix.

  3. Identified

    The issue has been identified and a fix is being implemented.

  4. Identified

    We're still implementing a fix for this issue. We will provide another update within the hour.

  5. Identified

    We are still working to implement a fix for this issue. We will continue providing regular updates.

  6. Identified

    We are continuing to work to implement a fix for this issue. During this time new Windows MDM device enrollments will continue to fail.

  7. Monitoring

    A fix has been implemented and we are continuing to monitor the results.

  8. Resolved

    This issue has been resolved and Windows devices are now able to successfully enroll in MDM.

  9. Resolved

    ![](https://jumpcloud.com/wp-content/themes/jumpcloud/assets/images/jumpcloud-press-kit/logos/02-jc-richblack-tm.png)

    # 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

Keep exploring

More from JumpCloud

Neighboring incidents on JumpCloud's timeline and the rest of their record on OutageDeck.