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’.

Summary SharePoint MCP (Model Context Protocol) tools may be missing in Copilot Studio due to Copilot Frontier access settings. Enable SharePoint MCP tools by configuring access in Microsoft 365 Admin Centre under Copilot Control System. Grant “All Users” access to Web Apps in Copilot Frontier settings. Tools typically appear in Copilot Studio within minutes after enabling. Table of Contents The Problem What Are SharePoint MCP Tools Solution: Enable Copilot Frontier Access Step-by-Step Configuration Verification References The Problem When building agents or custom copilots in Copilot Studio, you may find that SharePoint MCP tools are missing from the available connectors or tools list.