Unanswered

Posting to HTTP request trigger from Azure Function

(2) Share

Report

Posted on by joliverautomate

I am trying to post (HTTP Client POST) to our Power Automate environment from an Azure Function and can do so successfully when the option "Who can trigger a flow?" is set to "Anyone" on the Power Automate Flow. However, when I set the value to "Any user in my tenant" and try to follow the article here Add OAuth authentication for HTTP request triggers - Power Automate | Microsoft Learn I am unsuccessful. Steps I've taken are as follows:

Azure App Registration with the appropriate Power Automate Permissions was created
I am able to successfully get a bearer token for this Azure App Registration via Getting a Bearer Token in Power Automate Flow from Azure App Registration | Medium and set the scope to the recommended "aud" value from the article above (including the //.default)

When I send the bearer token along with a request in code (using HTTP client, with the appropriate headers), I am receiving a 403 - Forbidden HTTP status code with the response. When reviewing the claims associated with the token, I noticed that the "aud" value is not correct and I cannot find a way to have it set to what is required in the article posted above. I tried the steps found in this answer to no avail, https://stackoverflow.com/questions/77220479/add-oauth-authentication-for-http-request-triggers. It doesn't seem that custom values can be added to optional claims in Entra ID.

Any ideas of what I may be doing wrong?

Categories:

Using connectors

I have the same question (0)

All responses (2)

Answers (0)

Michael E. Gernaey 53,325 Super User 2025 Season 2 on at

Like (0)

Report

Hi @joliverautomate

Can you see if this helps you

https://laurakokkarinen.com/how-to-securely-call-a-logic-app-or-a-flow-from-an-azure-function-benefits/

If not please come back for more help.

If so can you please mark as such and maybe a like.

Thanks!

Was this reply helpful? Yes No
Suggested answer

joliverautomate 8 on at

Like (0)

Report

@Michael E. Gernaey while this isn't the specific answer to my question it is a nice article that explains in detail how to use the HTTP Request endpoint in Power Automate or Logic Apps. My particular issue was when you select the option, on the trigger, to only allow the request to come from within your organization, not using the SAS token URL (see below).

I was able to find the specific solution to my problem by replacing a value in the body of my request to secure a token from Entra ID. Following the two articles I posted; I needed to get a bearer token that had the correct value for audience, and it was not returning correctly using the screen shot below (from Getting a Bearer Token in Power Automate Flow from Azure App Registration | Medium):

I replaced the form field "scope" with "resource" and that did the trick. I was able to successfully retrieve an authenticated token from Entra ID with the correct audience value that Power Automate was expecting.

Was this reply helpful? Yes No