Expose HTTP Request-Triggered Power Automate Flow in Azure API Management-Part 2

Views (23)

N__A

Like(2)

Report

To proceed with this part, you need to first review Part I and then complete the remaining steps.

Next, let’s go ahead and update the Inbound policy to apply the “rewrite-url” and “forward-request” policies. Select the “Send SMS” operation and then click on the Inbound edit button:

Add the highlighted policies below and click Save:

Now that we are done with the configurations, let’s test the whole thing. Go to Test, edit the request body then click the Send button at the bottom:

To add an additional security layer, configure your flow trigger for either “Any user in my tenant” or “Specific users in my tenant” to restrict it to be triggered by authenticated users only. In this mode, you’ll need to pass a bearer token in the header of the request to trigger the flow.

Comments

CU31070505-0
Posted at

Expose HTTP Request-Triggered Power Automate Flow in Azure API Management-Part 2

Thank You for giving this helpful solution to solve my problem.

I'll try it.

Like (0)

Report

Community site session details

Expose HTTP Request-Triggered Power Automate Flow in Azure API Management-Part 2

Comments

Forum hierarchy changes are complete!

Ajay Kumar Gannamaneni – Community Spotlight

Congratulations to the November Top 10 Community Leaders!