> For the complete documentation index, see [llms.txt](https://ai-security-docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/ai-agent-security/microsoft-copilot-studio.md). # Microsoft Copilot Studio [Microsoft Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/fundamentals-what-is-copilot-studio) is a low-code platform for building and deploying conversational AI agents and copilots. Akto integrates with Copilot Studio in three ways — pick the one that matches your use case, or combine them.

Integration	Description
Connect to Akto (Async Mode)	Poll conversation transcripts from Microsoft Dataverse on a recurring schedule. No agent changes required. Detection-only — Akto observes traffic after the conversation has ended.
Connect to Akto (Block Mode)	Inline request and response guardrails added directly inside the Copilot Studio agent topics. Blocks malicious prompts and scans AI responses in real time.
Proxy MCP Server via Akto	Route MCP server tool calls made by the agent through Akto's `agent-proxy` for inspection and policy enforcement on every MCP request and response.

## Which option to choose * **Async Mode** — fastest to set up, zero agent changes, good for visibility and red-team analysis. Detect-only; cannot block. * **Block Mode** — required if you want to **block** prompt-injection, PII leaks, or policy violations before the model or user sees them. Requires editing each agent's topics. * **Proxy MCP Server via Akto** — required if your agent calls external **MCP servers** as tools and you want every MCP request and response to flow through Akto. All three can run side-by-side on the same agent.