______________________________________________________________

Anonymous · ‎04-27-2022

Hi Community,

I am trying to use a GET method in a HTTP call to a child flow, but get the following response to the parent flow run:

The request must be authenticated only by Shared Access scheme.

I can get the HTTP request to work if I use the POST method, or if I use the "Run a Child Flow" action with the GET methods specified. So I do have a workaround, but I wanted to see if I can get the parent-child call to work properly with the HTTP action and the GET method.

The limitation on using the GET method with the 'Run a Child Flow" action is that you can't specify query parameters, something I wanted to do in the HTTP call to the child flow to pass a single parameter for the child flow to use.

I suspect it has something to do with the environment set up because I have managed to make this approach work in a different Tenant under my control.

Any suggestions gratefully received.

Cheers, Innes

Rhiassuring · ‎05-01-2022

Hi there,

I went looking around for some answers, and it seems like this fellow had the same issue and the answer was to "copy the URL from the original source".

https://stackoverflow.com/questions/58551088/directapiauthorizationrequired-with-microsoft-flow-call...

I guess it somehow retains the old auth information? Unsure, but, seems like it might be helpful? Let us know.

Cheers,

Rhia

(And, as an aside, I'm sure you've already seen this? https://flow.microsoft.com/en-us/blog/build-nested-flows/ )

______________________________________________________________

Did this answer your question? Please mark it as the solution.
Did it contribute positively towards finding the final solution? Please give it a thumbs up.

I answer questions on the forum for 2-3 hours every Thursday!

Anonymous · ‎05-03-2022

Hi Rhia, Thanks for your reply and link. I did try this suggestion, but got the same result. On a completely separate tenant I got the HTTP action to work with a GET, so suspect it's a policy/restriction set on the problem tenant. I've worked around it, but would still like to do it the correct way with a GET as opposed to a POST. Cheers, Innes

Anonymous · ‎01-25-2024

I had a similar issue and i changed the HTTP action to the below setup, however you need to make sure to copy the generated link once again as it changed when i updated that option. After that it worked.