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.

   
2. Select the agent to which the OvalEdge MCP server must be added.

   

   To create an agent, please click here.

3. Open the Tools tab.

   
4. Click + Add a tool.

5. In the Add tool window, select Model Context Protocol.

   
6. On the Add a Model Context Protocol server page, provide the following information:

   

   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.

   
8. Under Type, select Manual.

   
9. Enter the OAuth configuration details. Click Create.

   

   Field

   Value

   Client ID

   Your Okta Client ID

   Client Secret

   Your Okta Client Secret

   Authorization URL

   https://YOUR_OKTA_DOMAIN/oauth2/default/v1/authorize

   Token URL

   https://YOUR_OKTA_DOMAIN/oauth2/default/v1/token

   Refresh URL

   Same as the Token URL

   Scopes

   openid profile email

10. After the tool is successfully created, copy the Redirect URL generated by Copilot Studio. Click Next.

    

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

    Copy the generated callback URL and add it to the Sign-in Redirect URIs section of the Okta application. Later, finish Create Connection/Sign-in.

11. In the connection page, expand the Connection drop-down and select Create new connection.

    
12. Enter a display name for the connection and click Create.

    
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.

    
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.

    
16. Test the agent by asking a question such as Search Table FILM_CATEGORY.

    
17. After successful validation, click Publish to publish the agent.

    
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.