> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/destinations/categories/ai/ms_copilot_studio/faq.md).

# FAQ

<details>

<summary>What is Microsoft Copilot Studio?</summary>

Microsoft Copilot Studio is a platform for building and extending AI agents that answer questions and take action. When connected to Coupler.io through an MCP (Model Context Protocol) tool, your agents can access business data from any supported source and answer questions about it in plain language.

</details>

<details>

<summary>How does my data get to the agent?</summary>

Coupler.io exposes your data through an MCP server. You add that server to your Copilot Studio agent as a tool, and the agent calls it on demand when you ask about your data. When you run a data flow with Microsoft Copilot Studio as the destination, the data becomes available to the agent through this tool.

</details>

<details>

<summary>Do I need a client ID or secret to connect?</summary>

No. The Coupler.io MCP tool uses **OAuth 2.0** with **Dynamic discovery**, so Copilot Studio registers itself with Coupler.io automatically. The first time someone uses the tool, they see a consent card in chat and sign in to Coupler.io once.

</details>

<details>

<summary>Why doesn't my agent use the Coupler.io tool automatically?</summary>

The agent needs **generative orchestration** enabled to decide when to call MCP tools on its own. This is the default for new agents. If it's turned off, enable it on the agent's settings so it can use the Coupler.io tool.

</details>

<details>

<summary>Which data flows are available to the agent?</summary>

Only data flows that use the **Microsoft Copilot Studio** destination are available to the agent. Data flows sent to other destinations won't appear.

</details>

<details>

<summary>Can I send data from multiple sources to one agent?</summary>

Yes. A single Coupler.io data flow supports multiple sources, and you can combine them using **Join** or **Append** transformations before the data reaches the agent. You can also run several data flows with the Microsoft Copilot Studio destination.

</details>

<details>

<summary>How do I keep the agent's data up to date without re-running manually?</summary>

Once your data flow has completed a successful manual run, set up a **schedule** in Coupler.io to refresh the data automatically — hourly, daily, or at a custom interval. The agent will then have access to fresh data whenever it queries the tool.

</details>

{% hint style="info" %}
For help setting up specific data sources for Microsoft Copilot Studio, see the individual source articles in the **Sources** section of this Help Center.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/destinations/categories/ai/ms_copilot_studio/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.