This guide explains how to connect Oversai to Microsoft Copilot through a Copilot Studio agent, so the agent can use Oversai tools to get coachings, QA evaluations, interactions, scorecards and AI analytics. Once connected, you can publish the agent to Microsoft Teams and Microsoft 365 Copilot so your team can use it there. Oversai can't be connected directly to the Microsoft Copilot app or to Microsoft 365 Copilot Chat. The connection is made in a Copilot Studio agent, which then reaches Teams and Microsoft 365 Copilot when you publish it.
Before you start
Access to Microsoft Copilot Studio with permission to create or edit agents in a Copilot Studio environment. You also need maker permissions in that environment to create connections.
The full Copilot Studio, with a Copilot Studio license. The lite agent builder in Teams and Microsoft 365 Copilot doesn't support MCP tools.
Generative orchestration turned on for the agent. MCP tools don't work with classic orchestration.
An Oversai account with access to the data you want the agent to use.
If your organization applies Power Platform data policies (DLP), the MCP connector must be allowed by those policies. MCP servers in Copilot Studio run through Power Platform connectors, so connector policies also apply to them.
To publish to Teams, Power Platform apps must be allowed in Teams. Your Teams admin manages this in the Teams admin center.
Oversai MCP details
MCP Server URL: https://mcp.oversai.com/mcp
Transport: Streamable HTTP (the only transport Copilot Studio supports)
Authentication: OAuth 2.0, using your Oversai sign-in
Step 1: Create or open an agent in Copilot Studio
Go to Microsoft Copilot Studio and sign in with your Microsoft work account.
Open the agent you want to connect to Oversai, or create a new one. A name such as "Oversai QA Assistant" works well.
Step 2: Add the Oversai MCP server
In the agent, open the Tools page.
Select Add a tool, then New tool.
Under Create new, select Model Context Protocol. The MCP onboarding wizard opens.
Fill in the fields:
Server name: Oversai
Server description: Oversai QA and Voice of the Customer data: coachings, QA evaluations, interactions, scorecards and AI analytics.
Server URL: https://mcp.oversai.com/mcp (include /mcp at the end)
Under Authentication type, select OAuth 2.0.
Under Type, select Dynamic discovery. No other fields are needed.
Select Create, then Next.
Figure 1. The MCP onboarding wizard in Copilot Studio. Source: Microsoft Learn.
Figure 2. OAuth 2.0 with Dynamic discovery selected. Source: Microsoft Learn.
Note: Choose Dynamic discovery, not Dynamic or Manual. If the server was created with the wrong authentication type, delete it and add it again instead of editing it. The agent uses the Server description to decide when to call Oversai, so keep it specific.
Step 3: Create the connection and sign in to Oversai
In the Add tool dialog, under the connection field, select Create a new connection.
Select Create. A sign-in window opens.
Sign in to Oversai, review the requested permissions and select Allow. You are redirected back to Copilot Studio.
Check that the connection shows a green checkmark, then select Add to agent (or Add and configure).
Step 4: Choose which Oversai tools the agent can use
Open the Oversai tool's details page in the agent. Copilot Studio loads the list of tools that Oversai provides.
Open the Tools tab and use the toggles to turn on the tools you want the agent to use. Turn on only the tools your team needs. Copilot Studio recommends about 25 to 30 tools per agent.
In the tool's settings, check that the connection uses end-user credentials, so each person signs in with their own Oversai account and only sees the data that account can access. If it uses the maker's credentials, everyone sees the data of the person who set up the agent.
Select Save.
Step 5: Test the connection
Open the Test pane in Copilot Studio.
Ask a question that needs Oversai data, for example: "Show me the latest QA evaluations for my team" or "Summarize this week's coachings".
If the agent replies that you need to connect first, select Open connection manager, then Connect and Submit. Sign in again if asked, then select Retry in the test pane.
Step 6: Publish the agent to Microsoft Teams and Microsoft 365 Copilot
Select Publish to publish the agent. It must be published at least once before it can be added to Teams.
On the top menu, select Channels, then the Microsoft 365 and Microsoft Teams tile.
To make the agent available in Microsoft 365 Copilot as well as Teams, select Make agent available in Microsoft Copilot. Leave it cleared for Teams only.
Select Add channel.
Select See agent in Teams, then Add, to install it for yourself and try it.
Figure 3. Adding the agent in Microsoft Teams. Source: Microsoft Learn.
To share the agent with others, use Availability options:
Copy link: share an installation link with people who already have access to the agent.
Show to my teammates and shared users: the agent appears under "Shared with you" in the Microsoft 365 Agent Store.
Show to everyone in my org: select Submit to org catalog. A Microsoft 365 or Teams admin must approve it before it appears in the org catalog.
In Microsoft 365 Copilot, type @, select the Oversai agent and ask your question. Each user signs in to Oversai the first time the agent needs Oversai data, and only sees the data their Oversai account can access.
Troubleshooting
"Model Context Protocol" or "Add a tool" is not available: your Copilot Studio environment or role may not allow it. Ask your Power Platform admin.
Sign-in fails or the connection never turns green: delete the Oversai tool from the agent and add it again with OAuth 2.0 and Dynamic discovery.
The connector is blocked: a data policy (DLP) is blocking it. Ask your Power Platform admin to allow it.
The agent doesn't appear in Teams: check that the agent was published, that it was shared with you, and that Power Platform apps are allowed in the Teams admin center.
The agent doesn't call Oversai: make the server description more specific and check that the tools you need are turned on.
The tools never load or the agent doesn't use them: check that generative orchestration is turned on in the agent's settings. MCP tools don't work with classic orchestration.
The wizard shows "Enter the complete server path to continue": check that the Server URL is exactly https://mcp.oversai.com/mcp, including /mcp at the end.
The sign-in window doesn't open or closes with an error: your browser may be blocking pop-ups or third-party cookies. Allow them for Copilot Studio or try a new browser profile.
Every user sees the same data: open the Oversai tool's settings and check that it uses end-user credentials, not the maker's credentials (see Step 4).
If you still have issues, write to [email protected] or reach out to your Account Manager. We'd be glad to help.