> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/mcp-server/deployment-options/remote-mcp/set-up-microsoft-copilot-studio-with-remote-mcp.md).

# Set up Microsoft Copilot Studio with Remote MCP

## Scenario

Integrating the OvalEdge Remote MCP (Model Context Protocol) Server with Microsoft Copilot Studio enables Microsoft 365 Copilot (chat and desktop applications) and Microsoft Teams users to securely access governed metadata from OvalEdge through AI-assisted conversations. After the integration is complete, users can search catalog assets, retrieve metadata, explore glossary terms, analyze lineage, discover data sources, and access other supported MCP capabilities directly from Microsoft 365 Copilot. 

### Prerequisites

Before starting the integration, ensure that:

* Microsoft Copilot Studio access is available.
* The OvalEdge Remote MCP Server URL is available.
* The OvalEdge Token and Secret have been generated.
* The authentication value is available in the format TOKEN::SECRET.
* Permission is available to create and publish Microsoft Copilot agents.

### Steps Involved

1. Open [Microsoft Copilot Studio](https://copilotstudio.microsoft.com/environments/Default-c717a2aa-3648-46e2-aae6-a5f4a51947db/home) and sign in with a Microsoft account that has permission to create Copilot agents.

   <div align="left"><img src="/files/5NyHHHY3XEyJICMLokuq" alt=""></div>
2. From the left navigation pane, click **Agents**. Click **Create blank agent**.

   <div align="left"><img src="/files/313KdF6yd37DxKMCrqui" alt=""></div>
3. Enter the **Agent Name**, and then click **Create**.

   <div align="left"><img src="/files/7TOl31WEkxrCgEJdDEOL" alt="" height="226" width="601"></div>
4. Wait until Microsoft Copilot Studio completes provisioning the new agent. Select the preferred AI model for the agent.

   ![](/files/UO6Pg4QFMXBR7r4Mmc8u)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>By default, the Claude Sonnet 4.6 AI model is selected.</p></div>
5. Click the **Tools** tab. Click **Add Tool**.

   ![](/files/FjAK6qH6062IZ2bnxIT7)
6. Select **Model Context Protocol (MCP)** as the tool type.

   ![](/files/xfpeqSGizQD3JiLiMala)
7. Enter the **Server Name**, **Server Description**, and **OvalEdge Remote MCP Server URL**  for the MCP server.

   ![](/files/nlvzFoaRIpCW1kQaXubh)
8. Select **API Key** as the authentication type. Select **Header** as the API Key location. Enter **X-OvalEdge-Credentials** as the header name. Click **Create** to register the MCP server.

   ![](/files/Qco3ViuroJFslM4IHO8S)
9. Verify that the newly created MCP server appears as below.

   ![](/files/6zjMGgX9zDl2eVb7XAXz)
10. Click **Create New Connection** for the MCP server.

    ![](/files/hFYsTnQaokM5Lk6U1etY)
11. Enter the authentication value using the format **TOKEN::SECRET**.

    ![](/files/QzH7jL9uOtHcB3rH7CuI)
12. Click **Create** to establish the MCP connection.
13. Verify that the connection status changes to **Connected** after the connection is created.

    ![](/files/z7Uktbd1Rmwvi2kPzgTx)
14. Click **Add and Configure** to retrieve the tools exposed by the OvalEdge MCP Server.
15. Review the available MCP tools displayed in the tool list.

    ![](/files/jw2igKDhWpUDY88rZ3vF)

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>By default, all MCP tools are selected, but users can customize it to enable only the required tools and disable those that are not required. Only selected MCP tools will be available to the agent.</p></div>
16. Click **Save** to save the selected MCP tools.

    ![](/files/jsxEBJpDGt53a7zAMLg0)
17. Navigate to **Settings** for the agent.

    ![](/files/ksmuvPwIOBks3ulMHFZS)
18. Select **Generative AI**. Click **Orchestration**. Enable **Use Generative AI Orchestration** by setting it to **Yes**.

    ![](/files/YMVtoSxgX8BlSGOkKoRH)
19. Navigate to the **Test** panel. Enter a sample prompt to verify the MCP integration. Click **Send** to submit the prompt.

    ![](/files/JlHcuzditCgbb9pa66aQ)
20. If prompted to authenticate, click **Open Connection Manager**.

    ![](/files/diIRD01CBkX6nHiKLs6N)
21. Review the available MCP connections. Verify that the OvalEdge MCP connection is listed.
22. If the connection is not active, select the OvalEdge MCP connection. Click **Connect**.

    ![](/files/0ol5tfObkoqbWBvnX3UX)
23. Select the required connection and click **Submit**.

    ![](/files/9Yo9sRdHY1v87uui5AIb)
24. Wait until the connection status changes to **Connected**.

    ![](/files/BrAOUx3jnqhbAYxXm0yB)
25. Return to the **Test** panel. Click **Retry** to execute the original prompt again.

    ![](/files/57UocPqk1R18bdfwmGPC)
26. Verify that the **Activity Map** displays the MCP tool execution. Review the tool execution details, including the request and response payload.

    ![](/files/PlehC6645B5jIZqMDkc3)

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Verify that the execution status is successful and no errors are returned. Review the metadata returned from the OvalEdge MCP Server. Confirm that the returned metadata matches the requested catalog object.</p></div>
27. Navigate to the **Channels** tab. Under **Microsoft Channels**, select **Microsoft 365 and Microsoft Teams**.

    ![](/files/4RXto3tI8aZPKwFkN02E)
28. Enable **Make agent available in Microsoft 365 Copilot**. Click **Add Channel**.

    ![](/files/f15RZlTC6IkFKN230VAq)
29. Verify that the ‘Microsoft 365 and Microsoft Teams’ channel is successfully added to the agent.

    ![](/files/ICTkXq2v0UQEQ4lo7D7S)
30. Click **Publish**. In the **Publish Agent dialog**, enable **Force newest version**.

    ![](/files/cfIIB84lawCSIqkzGd4d)
31. Click **Publish** to publish the latest version of the agent.
32. Wait until the publishing process completes successfully. Verify that the agent status changes to **Published**.

    ![](/files/sGf9xVMAg9YZ2CtIl74a)
33. Navigate to **Microsoft 365 and Microsoft Teams** under the **Channels** page.

    ![](/files/uA1zsLUZaigCY9fudQLW)
34. Click **See agent in Microsoft 365** to open the published agent directly in Microsoft 365 Copilot.

    ![](/files/AY7Tt3cOrrzFiCwIPFQb)
35. Verify that the published OvalEdge MCP agent opens successfully in Microsoft 365 Copilot. In Microsoft 365 Copilot, review the **Agent Store** and locate the published OvalEdge MCP agent.

    ![](/files/vo9cd4OF3JheYxlGqOXN)
36. Click **Add** to add the OvalEdge MCP agent to Microsoft 365 Copilot.

    ![](/files/d9xw1IqInvJ7Lu1JRpo0)
37. Wait until the agent is added successfully.
38. Open the newly added OvalEdge MCP agent.

    ![](/files/T133ThK1eN0Dv5Ofyfao)

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Users can pin the created Agent(s), and the pinned Agent(s) will be displayed under the ‘Agents’ section from the left menu.</p></div>
39. Enter a sample metadata query in the prompt box. Click **Send** to submit the query.

    ![](/files/vxYJeuie0MoPpntc3fD2)

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Ensure that users select only the created agent from the ‘Agents’ section (here ovaledgeMCP2 Agent) before prompting.</p></div>
40. If prompted for authentication, click **Open Connection Manager**.

    ![](/files/Ux1hLfDqH1A3nqtxqaZc)
41. In the **Manage your Connections** page, locate the OvalEdge MCP connection.

    ![](/files/Vxm4uyBMVEzbwCoA44QU)
42. Click **Connect** for the OvalEdge MCP connection.

    ![](/files/ntCkc5HrwghjHJMl1ZYQ)
43. In the **Create or Pick a Connection** dialog, select the previously created OvalEdge MCP connection.

    ![](/files/wjQuyQzAN10VY6vJHVV7)
44. Click **Submit** to authenticate the connection.
45. Wait until the connection status changes to **Connected**.

    ![](/files/I0L8ZMTq54vWOBetEfJz)
46. Return to the Microsoft 365 Copilot conversation window. Click **Retry** to execute the previously submitted prompt.

    ![](/files/QKy5BnX4SclxcWHAP0ZO)
47. Wait for Microsoft 365 Copilot to invoke the OvalEdge MCP tools.
48. Review the returned response and verify that the metadata has been successfully retrieved from the OvalEdge MCP Server.

    ![](/files/PpyBMaRDqEMAawcaPknW)

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# 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.ovaledge.com/release8.2/mcp-server/deployment-options/remote-mcp/set-up-microsoft-copilot-studio-with-remote-mcp.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.