‎Intune connector stuck because it is no longer supported‎

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!