Introduction During a discussion in a WhatsApp community group, a question arose about configuring a Copilot Studio agent for HR-related queries. The scenario involved country-specific policies stored in separate SharePoint folders. The challenge was ensuring that the agent dynamically retrieves content relevant to the user’s location. For example, if someone from the UK asks about maternity leave, the agent should only pull information from the UK folder, not from other countries.

Introduction Copilot Studio allows users to enhance agent functionality by integrating existing Power Automate flows. These flows can be added directly to topics or utilized as tools within an agent. This post explains how to add Power Automate flows as tools and use them effectively within Copilot Studio. Adding Power Automate Flows to Topics Within a topic added to an agent, existing agent flows can be seamlessly integrated. This approach enhances the agent’s capabilities as well as introducing more probablistic behaviour to the agent.

Introduction Copilot Studio creates different types of flows based on whether they are created as a trigger (autonomous agent) or as part of action within Topics or elsewhere. These flows leverage Power Automate in the background. This post explores the distinctions between trigger flows and agent flows, their advantages, and how they integrate with Copilot Studio. Types of Flows in Copilot Studio Trigger Flows Trigger flows created within Copilot Studio Agents are assigned the Power Automate plan.