Working with Microsoft Graph API call for Properties Catalog in Intune - deviceManagement/inventoryPolicies

Question

Working with Microsoft Graph API call for Properties Catalog in Intune - deviceManagement/inventoryPolicies

Barbara Wallner 0

Hi everyone,

I’ve been trying for months to retrieve data from the Properties Catalog in Intune (via PowerShell) using the Graph API. But I still get the following message when using PowerShell or Graph Explorer:
User's image

When I try to search for documentation online, I can’t find anything. Can anyone help me and tell me what permissions I need to set on my Enterprise Application to be able to use the “deviceManagement/inventoryPolicies” endpoint?

According to reverse engineering, the call should be possible:
User's image

Thanks for your help!

Vasil Michev 127.3K Reputation points MVP Volunteer Moderator

2026-07-13T10:33:47.2066667+00:00

Get the token out of the captured browser request and decode it via a tool such as jwt.ms to see which permissions are in play. Or reuse it directly.

2 answers

Your answer

Vasil Michev 127.3K Reputation points MVP Volunteer Moderator

2026-07-13T10:33:47.2066667+00:00

Get the token out of the captured browser request and decode it via a tool such as jwt.ms to see which permissions are in play. Or reuse it directly.

Answer 1

Vasil Michev 127.3K MVP Volunteer Moderator

Looks like there might be some further permissions required, or the endpoint is limited to specific client apps only. See this thread and the comments therein for additional details: https://learn.microsoft.com/en-us/answers/questions/2281401/graph-beta-url-is-giving-403-even-after-adding-rel

Barbara Wallner 0 Reputation points

2026-07-14T05:24:41.3566667+00:00

Thanks for adding this information - I've already added those permissions upfront but this does not change anything at all, unfortunately.
Vasil Michev 127.3K Reputation points MVP Volunteer Moderator

2026-07-14T06:16:54.1566667+00:00

I'm not having any luck with the endpoint either, and judging from the comments in the thread above, same applies to others (which is why I shared it). At this point, we can assume the endpoint is not working as expected/documented.
Barbara Wallner 0 Reputation points

2026-07-14T06:20:34.2133333+00:00

Totally agree with you - this endpoint is definitely not working as expected.

Answer 2

Barbara Wallner 0

Thanks @Vasil Michev for the hint. Now I know which permissions I need—they've been set—but I'm still getting the same error as before.

0 comments