Forum Discussion

Emalf13's avatar
Emalf13
Copper Contributor
Jan 08, 2026

‎Intune connector stuck because it is no longer supported‎

Hello,

We are trying to connect our JamF Pro to Intune for compliance checks on our Macs.

Following Microsoft's (incorrect) instructions, we found that the old (legacy) method to be no longer supported by JamF. However, after entering the Enterprise AppID the connector is now stuck and we cannot clear it because it cant connect to anything at JamF.

The "Terminate" button simply produces the following error:

"{"error":{"code":"InternalServerError","message":"{\r\n \"_version\": 3,\r\n \"Message\": \"An internal server error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: f0416542-74a3-4876-a3a3-d27cc6a9bb31 - Url: https://proxy.msub02.manage.microsoft.com/StatelessOnboardingService/deviceManagement/deviceManagementPartners('007d2fff-e0dd-4b28-8595-cec005efe5cd')/microsoft.management.services.api.terminate?api-version=5025-03-20\",\r\n \"CustomApiErrorPhrase\": \"\",\r\n \"RetryAfter\": null,\r\n \"ErrorSourceService\": \"\",\r\n \"HttpHeaders\": \"{}\"\r\n}","innerError":{"date":"2025-11-20T08:33:25","request-id":"11b3ecb3-6b3c-40a1-a2ef-1259682cc5f7","client-request-id":"f0416542-74a3-4876-a3a3-d27cc6a9bb31"}}}"

We have since connected JamF Pro using their new method successfully, but our managed Macs are still NOT showing in Intune. We need to clear the old connector, which is in limbo, in case this is blocking the new one from working.

We raised a case with Microsoft support in November 2025 and despite repeated efforts to contact them, still haven't had a response.

Any ideas, please?

Connector
graph
Intune
Jamf Pro
mobile device management (mdm)

2 Replies

  • mertefekanlikilic's avatar
    mertefekanlikilic
    MCT
    Jan 09, 2026

    Hi Emalf13​ 

    This is a known issue with the legacy Jamf-Intune connector. Once Jamf dropped support for the old integration, Intune can't terminate the connection properly - the InternalServerError you're seeing is expected behavior.

    The stuck legacy connector can block your new Jamf integration even if it was set up successfully.

    While waiting for Microsoft support, you could try removing it via Graph API:

    1. Go to Graph Explorer (https://developer.microsoft.com/en-us/graph/graph-explorer)
    2. Sign in with Global/Intune Admin rights
    3. GET request:https://graph.microsoft.com/beta/deviceManagement/deviceManagementPartner
    4. Find the entry showing "partnerState": "unavailable" and copy its "id"
    5. DELETE request :https://graph.microsoft.com/beta/deviceManagement/deviceManagementPartners/{id}

    If that doesn't work Microsoft support will need to manually remove the orphaned deviceManagementPartner object from the backend. When following up with them, specifically request removal of the legacy Jamf deviceManagementPartner that's blocking the new integration.

    Once cleared, your Jamf devices should appear in Intune normally.

    Hope this helps!

    • Emalf13's avatar
      Emalf13
      Copper Contributor
      Jan 09, 2026

      Hi mertefekanlikilic​ 

      Thank you for taking the time to reply. This is very helpful and we are glad it is a known issue and can be resolved. We have gone through the steps you provided (several times), but unfortunately we can't get the deviceManagementPartner to delete. We even tried the MgGraph method. Each time we get the same error:

      "No OData route exists that match template ~/singleton/navigation/key with http verb DELETE for request 
      /StatelessOnboardingService/deviceManagement/deviceManagementPartners('DeviceManagementPartnerId').
      Status: 400 (BadRequest)
      ErrorCode: No method match route template"

      We are now about to raise a third request with Microsoft Support. We are not hopeful as the previous two have been entirely ignored. This is frustrating as we can not proceed further until this has been removed.

Resources