Unanswered

Call Graph API with filter in query string

(0) Share

Report

Posted on by kubalaml

I'm trying to use the HTTP action to make a call to the Microsoft Graph API to query all active AD users using a certain filter. I've setup the application and bearer token already. It works if I make a call to just the users endpoint (https://graph.microsoft.com/v1.0/users) like this:

But when adding in a filter like this:

https://graph.microsoft.com/v1.0/users?$filter=endsWith(mail,'company.com') and JobTitle ne null&$select=userPrincipalName

It says "Enter a valid URI"

I've added this URI to a variable to get around the error, but when it runs it says "Unsupported Query"

"error": {

"code": "Request_UnsupportedQuery",

"message": "Unsupported Query.",

I see that there is a Queries section on the HTTP action, but I haven't figured out what format to put my query in to get it to work.

Also I already tested this query in the graph explorer and it works so the problem is not there.

Thanks for your help.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

abm abm 32,865 Most Valuable Professional on at

Like (0)

Report

Hi @kubalaml

You need to add a new string variable and enter the below as value

?$filter=endsWith(mail,'company.com') and JobTitle ne null &$select=userPrincipalName

Map this under the end of url

Please see this article explains about the issue

Combining Microsoft Graph and Flow for Better Office 365 Adminstration - Office 365 for IT Pros (office365itpros.com)

Was this reply helpful? Yes No
Verified answer

kubalaml 88 on at

Like (0)

Report

So part of the issue is that you need to use a variable for the URL. You can do the whole URL or just the query string as suggested above. The other bigger issue is that there seems to be a bug with Power Automate and how it handles filters. If I use 'endswith' or do a comparison against null (ex: 'mail eq null'), then it throws an error, but these works just fine using the Graph Explorer. My work around was to just run the query using the filters that do work, then use the Filter Array action to filter the contents further.

Was this reply helpful? Yes No