Introduction Refer to blog post Triggering a Power Automate HTTP Trigger from External Applications - testing with Postman for the initial Power Automate flow set up and testing with Postman. In this post, I’ll show you how to build a Microsoft 365 Copilot declarative agent that invokes a Power Automate flow with an HTTP trigger using Microsoft 365 Agents Toolkit. This approach enables you to extend Copilot’s capabilities by orchestrating complex workflows without writing custom code.

Triggering a Power Automate HTTP Trigger from External Applications For production environments, manually triggering a Power Automate flow via an HTTP trigger from external applications (.NET, React, or Agents Toolkit) requires Entra ID authentication if only users within the tenant can trigger it. If set to ‘anyone’ the Url of the workflow contains a sig parameter which is required to call the flow. This guide walks through the setup and testing process for only ‘any user in my tenant’.

Converting a HTTP Trigger into a Child Workflow in Power Automate Using a HTTP trigger requires Premium licence and with the Child Workflow in a solution alleviates the need of premium license. Other advantages using a solution: Application Lifecycle Management: Facilitates deployment. Child Workflow: Allows for a more modular and manageable flow structure. Easier Ownership Management: Simplifies updates to the flow owner. I recreated the child workflow within the solution selecting the Manually trigger a flow trigger and updated the parent flow to use the flow as child workflow.