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.

Summary Build autonomous agents that respond to email queries and generate dynamic Adaptive Cards. Use prompt tools to break down complex instructions into manageable, reusable components. Send personalized, interactive content directly via Outlook email. Learn formatting requirements and best practices for Adaptive Cards in email. Table of Contents Introduction Why Dynamic Adaptive Cards via Email Using Prompt Tools to Manage Instructions Building the Holiday Planning Agent Processing Email Queries Adaptive Card Formatting for Email Demo: Holiday Query in Action Key Takeaways References Introduction Copilot Studio enables makers to create intelligent agents that go beyond the chat interface.

Summary Autonomous agents run in the background without user prompts, so they cannot ask users to sign in during execution. Use maker-provided credentials for tools; user credentials are not appropriate for autonomous scenarios. Apply least privilege and restrict tool actions to reduce data exposure and abuse. Communicate the “runs under author’s identity” warning and govern access like any service account. Table of Contents Why Authentication Matters Autonomous Agents: What Changes Authentication Models Configure Tool Authentication Restrict Tool Actions Publishing, Warnings, and Governance Best Practices Checklist Why Authentication Matters As organizations adopt autonomous agents to perform tasks and make decisions, authentication becomes a core control.

When automating Copilot Studio agents or building custom integrations, you need to grant your Entra ID app registration the proper Power Platform API permissions. However, the Power Platform API often doesn’t appear in the standard API permissions list in the Azure Portal. This guide shows you how to enable the Power Platform API service principal and add the CopilotStudio.Copilot.Invoke permission to your app registration. Table of Contents The Problem Why Power Platform API is Missing Prerequisites Solution Overview Step 1: Verify Power Platform API Status Step 2: Enable Power Platform API Service Principal Step 3: Add API Permissions to Your App Step 4: Grant Admin Consent Alternative: Manual Manifest Configuration Verification Conclusion References The Problem While setting up automated testing for Copilot Studio agents using the Copilot Studio Kit (inspired by Matthew Devaney’s excellent video Copilot Studio Test Automation: STOP Testing Manually!

Monitoring your Copilot Studio agents is essential for understanding user interactions, identifying issues, and optimizing performance. Azure Application Insights provides comprehensive real-time monitoring and analytics capabilities for your copilot conversations. This guide walks you through connecting Application Insights to your Copilot Studio agent, enabling detailed telemetry, conversation tracking, and performance monitoring. Table of Contents Why Application Insights for Copilot Studio? Prerequisites Step 1: Create Application Insights Resource Step 2: Retrieve the Connection String Step 3: Link Application Insights to Copilot Agent Step 4: Verify Configuration Step 5: Check Metadata in Application Insights within Copilot Studio Agent Step 6: Test Step 7: Enable Enhanced Transcripts Step 8: Access the Copilot Studio Dashboard in Application Insights References Why Application Insights for Copilot Studio?

The Copilot Studio Kit is a powerful tool for managing and testing copilots in Microsoft Power Platform. However, installation requires the Creator Kit as a prerequisite dependency. This guide walks you through the complete installation process, including resolving common dependency issues. Table of Contents Overview Prerequisites Understanding the Dependency Installation Steps Step 1: Install Creator Kit Core Step 2: Install Copilot Studio Kit References Overview The Copilot Studio Kit is a managed solution that provides components and utilities for building, testing, and managing copilots in Power Platform.

Introduction When building agents in Microsoft Copilot Studio, you’re faced with a fundamental choice: Classic Orchestration or Generative AI Orchestration. Understanding the differences between these approaches is crucial for making the right architectural decision for your chatbot project. Enabling Generative AI unlocks dynamic capabilities where responses are intelligently crafted using available tools and knowledge sources as needed. In contrast, Classic Orchestration restricts responses to only the predefined content and behaviors explicitly configured in your agent’s topics.

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.

Introduction When building solutions in Copilot Studio, you may use Adaptive Cards to collect multi-choice input from users. The selected values from a multi-select field are stored as a table variable. However, if you want to pass these values to an Agent Flow (for example, to create a SharePoint list item), you need to convert the table variable into a single string. This post shows how to concatenate the selected values from a multi-choice Adaptive Card field into a semicolon-separated string using the concat function in a Set Variable value action within your topic.

When you create an Agent within Copilot Studio, a corresponding App registration is automatically generated. These app registrations are named after the Agent, suffixed with “(Microsoft Copilot Studio)”. You can view these app registrations in the Azure Portal under App registrations > All applications. Agent Certificates and Federated Identity Each app registration associated with a Copilot Studio Agent includes three certificates and two federated credentials as of January 2025. These components enable secure communication between agents and your data sources and services.