MCP Dataverse server Failing to save data from teams

(0) Share

Report

Posted on by CD-24061143-0

Hi ,
I have an scenario I have created an agent to save the data on the custom entity . I have created one topic where i have the user input we know that we cant add the MCP as a tool in topic because it is dedicated to agent so i have instructed the agent to save the data given with the logical name of table and the field .
This works in copilot test but when i publish it on teams channel and try to call that agent it says it cant access MCP dataverse and create_tool . when i ask for the list of the tool it gives only custom topic and system topic it is not listing the MCP server which i added in Tools tab .

Categories:

Copilot Studio pre-built agents/templates

Building Copilot Studio chatbots in Microsoft Teams

Calling actions from Copilot Studio

Publish & channel management

Topic creation & management

Model context protocol

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Ashlesha-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,
Thanks for reaching out. The issue you're seeing is expected when publishing to Teams — here's what to check:

Turn on Generative Orchestration — MCP tools won't work without it. Go to Settings → Generative AI → Orchestration → Yes, then republish.

Check Authentication on the MCP tool — The test panel uses your credentials, but Teams runs in the end-user's context. Open the MCP tool config and set Authentication to either End user or Maker-provided based on your scenario.

Check DLP policies — If your org has Data Loss Prevention policies in Power Platform Admin Center, the MCP connector might be blocked. Ask your admin to verify it's in the Business (allowed) group.

Once all three are confirmed, republish the agent and test again in Teams.

Was this reply helpful? Yes No
Suggested answer

sannavajjala87 515 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

Thanks for sharing the details , your configuration looks correct, and what you’re experiencing is actually expected behavior with the current platform.
In Copilot Studio, MCP tools are scoped at the agent level and work as expected in the test panel/playground. However, when the agent is published to Teams, the runtime has certain limitations. MCP-based tools (like Dataverse create operations through MCP) are not fully supported in the Teams channel yet.
That’s why:

The agent works correctly in Copilot Studio

In Teams, it cannot access MCP tools

Only system and topic-based capabilities are listed

MCP tool execution is not surfaced in that channel

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
At this point, I would treat this as a platform limitation or preview issue, especially if you're using the new MCP capabilities.

The behavior you're seeing (works in Copilot Studio test but not in Teams) has been reported by other users with preview features, where the published Teams

runtime hasn't yet reached feature parity with the test environment.

If you've confirmed:

The agent is republished.

The Teams app is updated.

Authentication is configured correctly.

The MCP server is enabled in the agent's Tools.

…and the issue still occurs only in Teams, it's worth opening a Microsoft support ticket or reporting it through the Copilot Studio community, as it may be a

current product limitation rather than a configuration error.

Was this reply helpful? Yes No