> 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/remote-oauth-mcp/set-up-microsoft-copilot-studio-using-remote-oauth.md).

# Set up Microsoft Copilot Studio using Remote OAuth

## Scenario

Use this procedure to configure Microsoft Copilot Studio to securely connect to the OvalEdge Remote MCP Server via OAuth 2.0. This configuration enables Microsoft Copilot Studio agents to invoke OvalEdge MCP tools via browser-based Okta authentication, without storing OvalEdge credentials in the agent configuration.

### Prerequisites

* An OvalEdge Remote MCP Server is deployed and accessible through a public HTTPS endpoint.
* An Okta OAuth application is configured with the required Client ID and Client Secret.
* The Authorization URL and Token URL for the Okta application are available.

### Steps Involved

1. Open **Microsoft Copilot Studio** and select **Agents** from the left navigation pane.

   ![](/files/RBtemJUThEtOkLhc8fqQ)
2. Select the agent to which the OvalEdge MCP server must be added.

   ![](/files/wgzEFZfAgX4rQaTdJRJM)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>To create an agent, please click <a href="https://docs.ovaledge.com/release8.2/mcp-server/deployment-options/remote-mcp/set-up-microsoft-copilot-studio-with-remote-mcp?fallback=true#steps-involved">here</a>.</p></div>
3. Open the **Tools** tab.

   ![](/files/aqF9Yxi56VxG5QDI3Q2B)
4. Click **+ Add a tool**.
5. In the **Add tool** window, select **Model Context Protocol**.

   ![](/files/QhHgeBSbqFEdrOwv6mYe)
6. On the **Add a Model Context Protocol server** page, provide the following information:

   ![](/files/Jh7ffL7CAMdmUtHus4dQ)

   1. **Server name** – Enter a meaningful name (for example, MCP OvalEdge OAuth).
   2. **Server description** – Enter a brief description of the MCP server.
   3. **Server URL** – Enter the complete OvalEdge Remote MCP endpoint URL.
7. Under **Authentication**, select **OAuth 2.0**.

   ![](/files/K0GAjfsdUzUGKy26eFMt)
8. Under **Type**, select **Manual**.

   ![](/files/au3zivLf8XpRpEwgbMmE)
9. Enter the OAuth configuration details. Click **Create**.

   ![](/files/BzXvutRmtwCijaU80pSr)

   <table data-search="false"><thead><tr><th>Field</th><th>Value</th></tr></thead><tbody><tr><td>Client ID </td><td>Your Okta Client ID </td></tr><tr><td>Client Secret </td><td>Your Okta Client Secret </td></tr><tr><td>Authorization URL </td><td>https://YOUR_OKTA_DOMAIN/oauth2/default/v1/authorize </td></tr><tr><td>Token URL </td><td>https://YOUR_OKTA_DOMAIN/oauth2/default/v1/token </td></tr><tr><td>Refresh URL </td><td>Same as the Token URL </td></tr><tr><td>Scopes </td><td>openid profile email </td></tr></tbody></table>
10. After the tool is successfully created, copy the **Redirect URL** generated by Copilot Studio. Click **Next**.

    ![](/files/XC0WKOttOEQZuPE3mND9)

    \
    **Example**: <https://global.consent.azure-apim.net/redirect/\\><generated-slug><br>

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Copy the generated callback URL and add it to the <strong>Sign-in Redirect URIs</strong> section of the Okta application. Later, finish Create Connection/Sign-in.</p></div>
11. In the connection page, expand the **Connection** drop-down and select **Create new connection**.

    ![](/files/X0ryR7k81wvPidvr5ahk)
12. Enter a display name for the connection and click **Create**.

    ![](/files/OUyEpxE6542t08GFDsXy)
13. When prompted, sign in using the configured **Okta** account and grant the requested permissions.
14. After authentication completes successfully, verify that the connection status changes from **Not connected** to **Connected**.

    ![](/files/46xKtVVaJ4lfzRCQKEzX)
15. Return to the configured **Model Context Protocol** tool and verify that the available OvalEdge MCP tools, such as **search\_catalog\_assets, catalog\_asset\_details, glossary\_search,** and **lineage\_search**, are listed.

    ![](/files/6Pxs87JmgMRndaV5CbeK)
16. Test the agent by asking a question such as **Search Table FILM\_CATEGORY**.

    ![](/files/98JH8ck4aeqqC0TrcqQX)
17. After successful validation, click **Publish** to publish the agent.

    ![](/files/ibehiuulgHnzksep1GOn)
18. Enable the required channel, such as **Microsoft 365 Copilot** or **Microsoft Teams**, publish the agent again if prompted, and submit it for administrator approval if required.

***

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/remote-oauth-mcp/set-up-microsoft-copilot-studio-using-remote-oauth.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.