Reset Search
 

 

Article

KB45095 - Could not connect to MDM web service with error stating please verify Tenant ID/ClientID. Enable MDM API Trace event to help determine problem

« Go Back

Information

 
Last Modified Date4/1/2022 3:35 PM
Synopsis
This article provides information about MDM Auth server type "Microsoft Intune"
 
Problem or Goal
Administrator would like to configure MDM Auth server and when clicked "Test Intune Connection" received the error as
"Could not connect to MDM web service. Please verify Tenant ID/ClientID. Enable MDM API Trace event to help determine problem "
and get the below logs in user access logs
2022-02-11 13:20:58 - ive - [127.0.0.1] System()[] - JTI-MDM-MS-Intune Request 94595119: POST /705d07a3-2eea-4f3b-ab59-65ca29abeb26/oauth2/token resource=https://graph.windows.net/&client_secret=******&client_id=f62ecddf-7b72-4309-91ed-a63e68f149f5f62ecddf-7b72-4309-91ed-a63e68f149f5&grant_type=client_credentials
2022-02-11 13:20:58 - ive - [127.0.0.1] System()[] - JTI-MDM-MS-Intune Response 94595119: Status: 400:

                                                               User-added image


 
Cause
Solution
This issue is due to legacy graph APIs(window.net) on Pulse Connect Secure versions 9.1R14 & below uses, which will be deprecated in June 2022.
Issue will be fixed in PCS OS 9.1R15 as we have implemented the new Graph API(Microsoft Graph) in 9.1R15 (due to be released in April’22),hence Customer have to upgrade to 9.1R15 once it is available to continue using Microsoft Intune integration.
 
Related Links
https://docs.microsoft.com/en-us/graph/use-the-api
https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq
https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-request-differences
 
Attachment 1 
Created ByAshish Kumar

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255