> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/ai/mcp-setup/microsoft-copilot-studio-setup.md).

# Microsoft Copilot Studio Setup

Configure a Copilot agent in **Microsoft Copilot Studio** (Agent Studio) to connect to Euno's MCP server for federated data context. Once connected, the agent can explore your Euno data model and call Euno tools directly.

Copilot Studio's default MCP connection supports only a single authentication header, and it blocks custom headers that begin with `x-`. Euno normally expects an API key plus an account ID and (optionally) a persona. To work around this, you send the API key through the connector's authentication and pass the account ID and persona as **query parameters**, which you add by editing the custom connector in Power Apps. This guide walks through that setup end to end.

### Prerequisites: Euno Setup

Complete these steps in Euno first — you will not be able to finish the Copilot setup without them:

1. Create a Euno **API key** and save the token for later (see [Advanced API Key Setup](/ai/mcp-api-key-setup.md)). Keys begin with `euno-`.
2. Note and save your Euno **account ID** and a **persona ID**. The agent will use this persona for context.

### Step 1 — Create the Copilot Agent

These steps use the new Agent Studio interface.

1. Log into your Copilot Studio environment, or [create a new one](https://copilotstudio.microsoft.com).
2. Note and save your **Copilot Studio environment ID** for later — you can read it from the URL.
3. Open the **Agents** tab and click **New agent**.

<img src="/files/hOLfVBpTgLn5d3wuOPQx" alt="" height="248" width="282">

1. Edit the agent's name and description, and select an image if desired.
2. Select a model.
3. Click **Add a tool**.

<img src="/files/mgw9utjFIWv288CBLUeS" alt="" height="61" width="389">

4. In the **Add a tool** popup, click **+ Add** and select **Model Context Protocol (MCP)**.
5. Configure the tool as follows:

   | Field          | Value                                                    |
   | -------------- | -------------------------------------------------------- |
   | Server URL     | `https://api.app.euno.ai/mcp`                            |
   | Authentication | API key                                                  |
   | Parameter type | Header                                                   |
   | Header name    | `API Key`                                                |
   | Key value      | Your Euno API key — **do not** include the word `Bearer` |

<img src="/files/P5RHmmJKAZpLi32j4pCT" alt="" height="513" width="624">

9. Click **Add**. This creates a new **custom connector**.
10. Before connecting, you need to modify the connector in Power Apps. Continue to Step 2.

### Step 2 — Adjust Connection Parameters in Power Apps

To use the Euno MCP server, the connection needs the additional query parameters below. These steps add the headers/parameters Euno requires.

1. Open a new browser tab and navigate to `https://make.powerapps.com/environments/<your-environment-id>/customconnectors` (swap in the environment ID you saved earlier).
2. You should see your new custom connector in the list.

<img src="/files/QY2sHwsr4nKl48tjVNf2" alt="" height="99" width="624">

3. Edit it (the pencil icon).
4. Go to the second tab, **2. Security**, and set:
   * **Parameter label** and **parameter name** to `api_key`
   * **Parameter location** to `Query`

<img src="/files/CJqn3rIjVbbbkw21aFs4" alt="" height="89" width="534">

&#x20;

<img src="/files/7Pos4yQlnPVcYYw6g7Rd" alt="" height="477" width="624">

5. Go to the third tab, **3. Definition**, and toggle the **Swagger editor** option.

<img src="/files/quGin1wazd6m3ySeNtNf" alt="" height="52" width="624">

6. Add the following under `description`, swapping in the Euno `account_id` and `euno_persona` (persona ID) you want the agent to use. Make sure `parameters:` sits directly below and is lined up with `description:`:

```yaml
   parameters:
     - name: account_id
       in: query
       required: true
       type: string
       default: '<your_euno_account_id_here>'
       x-ms-visibility: internal
       x-ms-summary: Account ID
       description: Euno account ID
     - name: euno_persona
       in: query
       required: true
       type: string
       default: '<your_euno_persona_id_here>'
       x-ms-visibility: internal
       x-ms-summary: Persona ID
       description: Euno persona ID (optional — pins a persona)
```

7. Click **Update connector** to save.

### Step 3 — Connect Your Agent to Euno and Test

1. Back in Copilot Studio, open the connection menu and click **Create a new connection**.

<img src="/files/FUAfeSt5ISXNI5cADORK" alt="" height="250" width="348">

2. Enter your API key again here — again, no `Bearer`, just the token. (If you return to edit this later, either **user** or **maker** authentication will work. Maker is easier if end-user security is not a concern.)
3. Click **Create**, then **Add**.
4. Navigate to the **Preview** tab.
5. In the prompt editor, enter a test prompt.
6. If everything is configured correctly, you should get a response.
7. From here you can publish the agent to make it available to your organization. Open the **Publish** drop-down menu (upper-right corner) to configure the agent's options in Teams and Copilot.

<img src="/files/l5cvjkhcC4JrijUpo5qa" alt="" height="513" width="624">

8. Click **Edit details** to set options like the agent name and developer name. Enter your developer details (privacy policy, Terms of Service, etc.) under **More**.

<img src="/files/250DJ2VBY1jV8ogBe0Km" alt="" height="517" width="624">

9. After saving and publishing, click **back** to reach the direct install links for opening your agent in Copilot and Teams. It may take a few minutes to become available.
10. You may also want to add other tools, such as connections to your data warehouse or operational systems.

### Relevant Links

* Copilot Studio: <https://copilotstudio.microsoft.com>
* Power Apps custom connectors: `https://make.powerapps.com/environments/<your-environment-id>/customconnectors`

### Related Pages

* [MCP Setup Guide](/ai/mcp-setup.md) — the recommended OAuth setup for MCP-compatible clients
* [Advanced API Key Setup](/ai/mcp-api-key-setup.md) — API key and header configuration, including how to create a key
* [MCP Bridge Setup](/ai/mcp-bridge-setup.md) — local stdio bridge for clients without remote HTTP MCP support


---

# 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.euno.ai/ai/mcp-setup/microsoft-copilot-studio-setup.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.