Set up EDITED in Microsoft Copilot

Making EDITED available in Copilot comes in two parts — a one-time setup and then everyday use:

• Set up — once, by a maker or admin (this page): build an agent in Copilot Studio that connects to EDITED, and publish it.
• Use — everyone, every day: pick the published EDITED agent, sign in to EDITED once, and ask. That half is simple and lives on Using EDITED in chat — end users never touch agent setup.

EDITED MCP
    ↓
Copilot Studio agent
    ↓
Publish the agent
    ↓
Microsoft 365 Copilot and/or Teams

Everything above is the one-time setup — this page. After that, people just use the published agent. The guiding idea: you don't "turn EDITED on in Teams" — you connect EDITED to an agent, then publish the agent. People use the agent; the agent uses EDITED.

Who sets this up

A maker or administrator, once, for the team — not each person who wants to ask a question. If you just want to chat with EDITED data, you're waiting on whoever owns your Copilot agents; this page is for them.

You'll likely need:

• A Copilot Studio environment you can build agents in.
• Permission to add a connection to an agent and to publish it.
• Admin approval to publish into Microsoft 365 Copilot or Teams — most tenants gate this.
• Your EDITED connection details (below).

Which licences and approvals apply varies by tenant — check with your Microsoft admin.

What you're connecting to

This is the EDITED side, and it doesn't change:

Server	EDITED MCP — https://mcp.edited.com/mcp/v1 (UK/EU) or https://mcp-us.edited.com/mcp/v1 (US)
Authentication	OAuth — you sign in to EDITED; no keys to paste
What appears	EDITED's market-data tools — retailer, brand, pricing, assortment and trend search

Set up the agent in Copilot Studio

The supported path is a Copilot Studio agent. Microsoft's screens move as their product does and may look different in your tenant, so treat these as goals, not exact clicks — follow Microsoft's own documentation for the detail, and use the EDITED values from the table above.

1. Open or create an agent in Copilot Studio.
2. Add EDITED as an MCP server on the agent, using the endpoint above. Microsoft's MCP onboarding wizard is the recommended path; choose OAuth 2.0 (dynamic discovery) as the authentication type.
3. Authorize the connection over OAuth — you'll be prompted to sign in to EDITED.
4. Confirm EDITED's tools appear on the agent. That's setup done — test it next.

Check it works before you publish

Before you publish to the whole team, confirm the agent can actually reach EDITED:

1. Check EDITED's tools are listed on the agent — retailer, brand, pricing, assortment and trend search.
2. Ask a question you know the shape of — for example, "Which retailers do you track for activewear in the UK?" — and expect a list of named retailers, not an apology or an empty answer.

If the tools are listed but the agent can't answer, that's usually not your setup — see If setup is blocked. If something looks off, tell us rather than assume you've got it wrong.

Publish to Microsoft 365 Copilot and Teams

When the agent passes that check, publish it and make it available in the Microsoft surface your team uses — Microsoft 365 Copilot (web and desktop) and/or Teams. Most tenants require an admin to approve it first. Publishing targets and the approval flow are Microsoft's; follow their documentation for your tenant.

What your users will see

Once the agent is published and approved, everyday use needs none of the setup above. Your team picks the EDITED agent in Microsoft 365 Copilot or Teams, signs in to EDITED the first time, and asks in plain language:

Someone asks the agent
    ↓
The agent calls EDITED
    ↓
EDITED returns live market data
    ↓
The agent answers

The first-time sign-in can look a little different from one tenant to the next. The full user-facing version lives on Using EDITED in chat — point your team there; they never see any of the setup on this page. If a user gets stuck, the end-user fixes are in Troubleshooting a chat connection.

If setup is blocked

Some setup problems are on EDITED's side to clear, not yours.

invalid_redirect_uri when you add the connection. As you connect the agent to EDITED, sign-in fails with an error like:

Failed to login. GetDynamicClientRegistrationResultAsync failed.
Status Code: BadRequest, Response: {"error":"invalid_redirect_uri",
"error_description":"a redirect_uri is not in this gateway's allowlist"}

This shouldn't happen, and when it does there's nothing you can fix in Copilot Studio — you haven't misconfigured anything. As it connects, Copilot registers with EDITED's gateway, which only accepts sign-in redirects on an allowlist we maintain. That allowlist is meant to be inclusive; if you've hit this, there's a gap on our side to close.

What to do: email support@edited.com — a screenshot of the full error (it contains the redirect_uri we need), plus your Microsoft tenant and the surface you're setting up. We add the address to the allowlist and tell you when to retry. There's nothing to change on your end.

Other ways to connect

Microsoft supports other models beyond Copilot Studio. We're noting them, not documenting them step by step yet:

• Declarative agents via the Microsoft 365 Agents Toolkit — a developer-oriented, source-controlled route for teams already building in that toolkit.
• Organizational MCP registration — an emerging enterprise model where an MCP server is registered once, centrally, and reused across many agents and teams, with central governance and approval. This is the direction we're most interested in validating for larger customers; it isn't ready to document as a how-to.

If one of these fits you better than Copilot Studio, tell your EDITED contact — that feedback shapes what we support next.

Help and feedback

• Stuck or blocked? Email support@edited.com with the Microsoft surface you're using (Copilot Studio, M365 Copilot, Teams), your tenant and admin situation, and the email on your EDITED account.
• Tell us what you learn. Redirect URIs, admin approvals, licensing surprises, cross-tenant behaviour — those are exactly what we're trying to pin down.

Landed here but you just want to chat?

If your team already has an EDITED agent, or you're on Claude or ChatGPT, you don't need this page — connecting is a one-time sign-in. See Using EDITED in chat.