Use the new Agent 365 tooling servers to bring Microsoft 365 Copilot Search, SharePoint & OneDrive, Outlook Mail, Outlook Calendar, Word and more directly into your Copilot Studio agents.
Why most Copilot Studio agents don't need manual authentication, and the myths keeping you from simpler configurations.
Essential techniques for managing session state, handling updates, and ensuring reliable performance when deploying Copilot Studio Agents to Microsoft Teams.
How to provide additional context and influence agent behavior through instructions, including specific tools and knowledge consultation.
Surface Anthropic reasoning process as informative activities via the Microsoft 365 Agents SDK and render summarized reasoning steps in your app.
Resources in MCP: How Copilot Studio Uses Them If you’re building MCP (Model Context Protocol) servers for Copilot Studio, here’s something important to understand: Copilot Studio’s orchestrator a...
Custom Headers in MCP Connectors The Model Context Protocol (MCP) allows Copilot Studio agents to connect to external servers that provide tools (and prompts as of recently). While MCP connectors ...
Passing Files from Copilot Studio to Agent Flows, Connectors and Tools Passing files from your Microsoft Copilot Studio (MCS) agent to downstream systems using Agent Flows (or Power Automate) and ...
Triggering Copilot Studio Agents with HTTP Calls Sometimes you want to trigger an autonomous Copilot Studio agent with HTTP requests from an external source. This post shows two complete paths to ...
Custom Knowledge Sources in Copilot Studio While Copilot Studio offers built-in knowledge sources like SharePoint and Dataverse, you might need to connect to your own search endpoints - perhaps a ...