- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2023 06:33 AM
Our InTune integration with ServiceNow was working perfectly. However, the latest InTune Spoke has caused an major issue with our use of this partnership. Previously we were able to pull the user from our InTune environment and populate the assigned to on our computer CI's. Now that specific information is not available. We do NOT see data in that field within the mapping options in IntegrationHub ETL. ALL the other fields have data populated that we can map. Is anyone else experiencing this problem?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2023 05:26 AM
@Harsha Pappala , 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2023 05:26 AM
@Harsha Pappala , 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2023 02:07 PM
Sorry for the delay in reply. I did find a solution after working with one of the ServiceNow techs. looks like the Intune azure app requires an additional role with the new plugin from ServiceNow.
Added user.readwrite.all to the Azure app within Azure.
After adding the above role, the Intune OAuth token needs to be refreshed.
Easiest way it to go to oauth_2_0_credentials and then select Intune credential then select the hyperlink to Get OAuth Token.