NewFree course: Learn how to runRun Amazon with Claude
DataDoe as a Copilot Studio tool

Copilot Studio MCP for Amazon, in Teams and M365 Copilot

Build one Copilot Studio agent, add DataDoe as its MCP tool and publish it where the team already works. Brand, finance and agency people ask about Seller Central, Vendor Central and Amazon Ads in a chat. IT decides who gets the agent and what it may call.

Start free trialSee the setup
Built from:Copilot Studio agentMCP toolTeams channel
• Which Copilot?

Microsoft has several Copilots. One route reaches Amazon.

“Microsoft Copilot MCP” searches mix up three products. The route that works today runs through Copilot Studio: you build the agent once, and Teams and Microsoft 365 Copilot are where people talk to it.

Step 1

DataDoe MCP server

mcp.datadoe.com/mcp/v1. Seller Central, Vendor Central and Amazon Ads in one schema, over Streamable HTTP.

Step 2

Copilot Studio agent

Added as a Model Context Protocol tool. Its description tells the orchestrator when to call DataDoe.

Step 3

Teams and Microsoft Copilot channel

One channel publishes to both. Tick “Make agent available in Microsoft Copilot” when you add it.

Step 4

Your people

Install it from the Teams app store, @mention it in Microsoft 365 Copilot, or add it to a team channel.

Not this route
Personal Microsoft Copilot app

Microsoft documents no way to add your own MCP server to Copilot on a personal Microsoft account. Sign in with a work or school account and use the agent.

Not supported
Microsoft 365 Copilot connectors

Synced connectors index outside content into Microsoft Search; federated ones are an early preview. DataDoe isn’t in that gallery, and the agent answers the same questions directly.

Different product
GitHub Copilot

For developers in VS Code, the CLI and GitHub’s cloud agent the setup is a JSON file, not an agent: GitHub Copilot MCP for Amazon.

Other page

Team not on Microsoft 365? The same DataDoe login works in ChatGPT with Amazon data, in Claude for Amazon sellers, and in any other MCP client.

• Copilot Studio MCP setup

Five steps in the MCP wizard.

Copilot Studio connects to a remote MCP server from its own onboarding wizard. A Power Apps custom connector also works, but the wizard is the way Microsoft recommends, and DataDoe needs nothing else.

  1. In Copilot Studio, open your agent and go to Tools → Add a tool → New tool → Model Context Protocol. The MCP onboarding wizard opens.
  2. Name the server and write its description 1. The orchestrator reads it to decide when to call DataDoe, so name the data it holds. Paste the server URL 2.
  3. Choose how it signs in 3. OAuth 2.0 → Dynamic discovery lets each person sign in to DataDoe with their own account. API key → Header with the name datadoe-mcp-key uses one key from Integrations → MCP.
  4. Select Create, then Create a new connection, sign in or paste the key, and Add to agent.
  5. Ask the agent something in the test pane, publish, then open Channels → Teams and Microsoft Copilot and add the channel.

Two requirements from Microsoft: generative orchestration must be switched on for MCP tools, and the server must speak Streamable HTTP, since Copilot Studio dropped SSE in August 2025. DataDoe’s endpoint meets both.

• Governance

Four people hold the keys. None of them is the agent.

An AI agent with access to Amazon is a question for IT before it is a question for the brand team. In Microsoft 365 the answer is split across admin centers, so here is who controls what.

Who controls a Copilot Studio agent that uses DataDoe, and where
ControlWhat it does for the Amazon agentWhere
Power Platform admin
Data policyThe DataDoe MCP tool rides on a Power Platform connector, so a data policy can allow it, block it, or keep it in the same data group as the connectors it may work with.Power Platform admin center → Security → Data and privacy → Data policy
Sign-in requiredBlock “Chat without Microsoft Entra ID authentication in Copilot Studio” and nobody reaches the agent without a work identity.Same data policy
Whose credentialsAllow end-user credentials only and every tool call runs as the person asking, never on the maker’s stored connection.Environment → Settings → Features → Control maker credential options
ChannelAllow or block publishing through “Microsoft Teams + Microsoft 365 Channel in Copilot Studio”.Same data policy
Teams admin
Org-wide listingAgents submitted for approval appear in “Built for your org” only after an admin approves them.Teams admin center → Teams apps → Manage apps
Pinned for a teamAn app setup policy can install and pin the agent for the marketplace team only.Teams admin center → Teams apps → Setup policies
Agent maker
Tool by toolTurn off “Allow all” on the DataDoe tool and switch on only what this agent needs. New tools then arrive switched off.Copilot Studio → Tools → DataDoe
Who can chatShare the agent with a security group instead of the whole tenant.Copilot Studio → Share
DataDoe owner
WritesActions start switched off per type, the Amazon account must be set to read and write, every change can run as a dry run first, and live Actions are capped at 500 per organization.DataDoe → Integrations and Actions
The recordThe Action log keeps each change and what Amazon answered.DataDoe → Actions

Data policies take effect immediately: a blocked connector shows as unavailable to makers, and an agent that breaks a policy can’t be published.

• Before you publish

Give the agent a brief. Then take tools away.

An agent the whole company can open should know its job and nothing more. Two settings in Copilot Studio do most of the work.

  • The description picks the toolCopilot Studio’s orchestrator reads the server description to decide when DataDoe is the right call. List the data it holds, not just “Amazon”.
  • Instructions set the house styleCurrency, date ranges, when to hand over a file instead of a long table. Agency teams add which client accounts the agent covers.
  • Switch off what it shouldn’t callTurn off Allow all and the agent can still read everything while actions_start stays off. A second agent, shared with fewer people, can hold the write tool.
• In a team channel

One channel, four jobs. Everyone sees the answer.

Allow users to add the agent to a team and anyone in the channel can @mention it. The reply lands in the thread, so finance, the agency lead and the vendor manager stop forwarding screenshots.

Marketplace › Amazon · EU
TK
Tomasz K.Mon 08:41

@Amazon Ops last week’s settlements by marketplace, with referral, FBA and ad fees in their own columns. Excel, please.

Amazon OpsMon 08:41

Week 41 across the EU marketplaces. Net proceeds €61,904 after €23,118 in fees. Germany is 58% of the total; FBA fees rose 9% on the oversize SKUs.

settlements-eu-week41.xlsxDataDoe export · 5 sheets
Reply

Test sign-in in a channel before rollout. Microsoft limits some end-user authentication in group chats and channels, and those replies are visible to everyone in the team, so consider a read-only agent there and 1:1 chat for anything else.

• Changes on Amazon

Drafted in chat. Approved in Teams.

Writes in DataDoe start switched off, Action type by Action type. When you do switch one on, put a named approver between the chat and Amazon, in the app they already use for expenses and leave.

  1. In the chat

    The agent prepares the change with actions_start and dryRun set. DataDoe validates the payload; Amazon sees nothing.

  2. In Approvals

    An agent flow, built in Copilot Studio with Power Automate’s Approvals connector, sends the dry-run summary to the approver in the Teams Approvals app and waits.

  3. On Approve

    The flow sends the same Action live through the DataDoe REST API. Your data policy has to allow the HTTP connector for this step.

  4. Afterwards

    Teams keeps the approval history. DataDoe’s Action log keeps the change and Amazon’s answer.

• Licences

Two bills. Here is each line.

Procurement asks this before anyone builds anything. Microsoft charges for the agent, DataDoe charges for the Amazon data and actions behind it, and neither bill includes the other.

Microsoft sideCopilot Studio and its channels
  • To buildOne of: a Copilot Studio user license, a Microsoft 365 Copilot license, or the Copilot Studio author role your admin assigns.
  • TrialA Copilot Studio trial lets you build and test in the test pane. It can’t publish to Teams.
  • To runAgent use is metered in Copilot Credits: prepaid packs, pay-as-you-go through Azure, or a prepurchase plan.
  • Licensed usersSome agent use by Microsoft 365 Copilot users is zero-rated. Check the Copilot Studio licensing guide for how tool calls are counted.
Billed byMicrosoft
DataDoe sideAmazon data and Actions
  • PlanThe Base Plan, $97 a month after a 14-day free trial, with unlimited Amazon connections.
  • SeatsWith OAuth, each person signs in to DataDoe, so each needs a DataDoe seat. One seat is included; extra seats are $29 a month.
  • One keyWith an API key the agent uses one shared connection, and per-person access is managed on the Microsoft side.
  • UsageMCP calls draw on the AI Tokens in your plan, the same as from any other AI client.
Billed byDataDoe

Microsoft’s terms change often; the Copilot Studio licensing guide is the source of truth for that column. Every DataDoe organization also gets one free 30-minute consultation with the Deltologic team each month.

FAQ

What IT asks before it says yes.

Yes. On the agent’s Tools page choose Add a tool, New tool, Model Context Protocol, then enter the server name, a description and the URL https://mcp.datadoe.com/mcp/v1. Pick OAuth 2.0 with Dynamic discovery, or an API key in the datadoe-mcp-key header, create the connection and add it to the agent.

Not that Microsoft documents. Personal Microsoft accounts have no setting for adding your own MCP server. The route is a Copilot Studio agent, used with a work or school account in Teams or Microsoft 365 Copilot.

Publish the agent, open Channels and choose Teams and Microsoft Copilot. Keep “Make agent available in Microsoft Copilot” ticked and add the channel. People then @mention the agent in Copilot chat or install it in Teams. For everyone in the organization, submit it for admin approval.

Yes. MCP tools in Copilot Studio rely on Power Platform connectors, so data policies in the Power Platform admin center govern them like any other connector. Admins can also require Microsoft sign-in, force end-user credentials per environment and decide who can install the agent in Teams.

OAuth when each person should sign in with their own DataDoe login. An API key when the agent should use one shared connection, for example a read-only reporting agent. With OAuth, every person who chats with the agent needs a DataDoe seat.

Microsoft bills agent usage in Copilot Credits under your Copilot Studio licensing. DataDoe bills separately: $97 a month for the Base Plan after a 14-day free trial, plus any extra seats. MCP calls use the AI Tokens in that plan.

Only if you allow it twice: the DataDoe Action type has to be switched on for an account set to read and write, and the agent needs the actions_start tool. You can preview changes as a dry run first, and send live ones through an approval flow in Teams.

No. Microsoft 365 Copilot connectors bring outside content into Microsoft Search and Copilot, mostly by indexing it. DataDoe is an MCP tool on an agent: it queries Seller Central, Vendor Central and Amazon Ads when someone asks, and nothing is copied into your Microsoft 365 index.

One per client is easier to govern. Give each client its own DataDoe organization and its own agent, with its own sharing list and, if you want, its own environment and data policy. One DataDoe login reaches every Amazon account in its organization, so separate organizations are what keep one client’s numbers out of another client’s channel.

Rolling this out across the tenant?

Book the free 30-minute monthly session with the Deltologic engineers behind DataDoe. Bring your admin, and we’ll walk through the wizard, the data policy and a first approval flow.

Book a demo
• Get started

Your Amazon numbers, one @mention away.

Connect Seller Central, Vendor Central and Amazon Ads to DataDoe, add it to a Copilot Studio agent, and let Teams and Microsoft 365 Copilot answer under the rules IT already enforces.

Start your free trial Book a demo
  • Copilot Studio MCP tool
  • Teams and Microsoft 365 Copilot
  • Writes off by default
  • $97 a month, 14 days free