Trying to use HTTP request to get user data - failing

[elbent]

Hi all. I am trying to use the Microsoft 365 Groups Send HTTP Request connector to get user information for my organization. I need to filter users by job title to get a specific person. Below is my request URI:

https://graph.microsoft.com/v1.0/users/?$filter=jobTitle eq 'Chief Innovation and Technology Officer'

Response: 

URI path is not a valid Graph endpoint, path is neither absolute nor relative or resource/object is not supported for this connector. Resources: groups. Uri: https://graph.microsoft.com/v1.0/users/?$filter=jobTitle%20eq%20'Chief%20Innovation%20and%20Technolo...'

I read past posts and added a slash before the question mark and it still fails. I have also tried with and without the dollar sign. I also read information about using the premium connector, however I do not have access to the authentication credentials it requires, and it would be a whole political process to get them. Any advice is appreciated. Thanks.

[FLMike]

Hello,

I am going to validate this as well, but wanted to share this.

Graph Explorer | Try Microsoft Graph APIs - Microsoft Graph

It allows you to test your queries etc. I tested yours in my organization and it works fine, so I now will test it in the connector you are referring too and see if I cannot get it to work for you.

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[elbent]

I tried testing it there but it said I didn't have sufficient permissions to make the request, and I am unsure how to get said permissions.

[FLMike]

If your account doesn't have privileges to do it, someone in the AAD team would have to grant them 

On the maybe bright side I reproed the issue and am looking at it now

[FLMike]

Hello,

I switched connectors and some queries work, but yours still does not. Same error. I think its simply a problem of these are not supported segements in the query from that connecto or the other I tried (which is another office 365 group connector).

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[elbent]

Thanks for your help. Any ideas why this query wouldn't work when I see very similar other queries on these forums?

[FLMike]

You have to read the docs (which are terrible) lol. It simply makes it appear it’s not supported. 

I can’t answer as to why they decided to block those segments, you’d have to ask the product team that made both connectors, seems… silly I agree but it’s just what it is. 

How things are stored in graph and how segments and filters are supported are not based simply on the “likeness” of queries unfortunately. In our heads it makes sense to work but whomever made the decision lol decided not. 

[VictorIvanidze]

Hi @elbent,

they (MS) have limited the functionality of these actions to force you to spend extra money for a premium connector.

To do what you want you have to use the "old" Microsoft 365 Groups Send HTTP Request (version 1).

The only way to use the old action v1 instead of new v2 is copypasting technique.

[elbent]

Hi,

Thanks for your reply. What is the premium connector that I would need to get this working? My company is willing to spend the money. 

elbent

[VictorIvanidze]

Two ones: "HTTP" and "HTTP with Azure AD".

[FLMike]

Hi

Between HTTP and the HTTP azure with AD as @VictorIvanidze  mentioned. And depending on how you do it you may need to register An App so you have the client secret etc to use in the cal. 

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey