Intune integration 403 error

[HarryLogiq]

Hello,

We are having an issue with our intune integration recently.

It will import the devices with no issues, however, it will not import the assigned_to user.

When checking the logs, I can see it is getting a 403 error followed by a 200 code.

The URL's are slightly different with the error being:
https://graph.microsoft.com/v1.0/deviceManagement/managedDevices/[DeviceID]/users

And the working URL being:

https://graph.microsoft.com/beta/deviceManagement/managedDevices/[DeviceID]?$select=hardwareInformat...

This is using the out of the box intune integration and service graph connector.

I have configured all of the permissions to match that of the docs here:

https://docs.servicenow.com/bundle/vancouver-integrate-applications/page/administer/integrationhub-s...

Is this a known error and an issue with the URL?

Thanks

[AJ-TechTrek]

Hi @HarryLogiq ,

Please check the Intune graph Connector version that should be more than 2.2.1.

we are using version 2.2.1 and no longer see the issue. Using IntegrationHUB ETl and the internal mapping within for Computer 1 to CMDB_CI_COMPUTER we see the user data available to map now.

Also you can refer the below.

https://www.servicenow.com/community/cmdb-forum/intune-integration-with-servicenow/m-p/2555215

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[SK Chand Basha]

Hi @HarryLogiq Oauth token not getting

You can test to see if an Oauth token can be received by creation a credentials record. From the application navigator search for Credentials and select the option under Connections & Credentials. Create an OAuth 2.0 Credentials credential type using the OAuth entity profile we made in this tutorial. Use the related link UI Action Get OAuth Token. If the details are correct, you'll get a successful message in the popup window.

Mark it Helpful and Accept Solution!! If this helps you understand.

[Eduard T]

Hi @HarryLogiq 

Did you manage to solve the issue?

[HarryLogiq]

Yes,

Issue was it needed Application permissions for User.ReadWriteAll

It might be because of the setup of our system, but delegate permissions didn't work.