Skip to content
  • There are no suggestions because the search field is empty.

Intentwise AI Gateway Setup Guide for Microsoft Copilot

Everything you need to connect your Microsoft Copilot Studio to your Amazon data, personalize your experience, and start generating reports using Intentwise AI Gateway.

Connect Microsoft Copilot Studio to your Intentwise data so your Copilot agent can answer questions about Amazon Ads, DSP, Seller Central, Vendor Central, and Search Query Performance — grounded in your real numbers and scoped to each end user's Intentwise permissions.

Copilot setup is more involved than Claude or ChatGPT because Copilot is built around organization-wide agents with per-user OAuth. Plan on 15–20 minutes for the maker, plus a one-time admin review if your tenant has restricted sharing.

What is MCP?

Model Context Protocol (MCP) is the open standard that lets AI assistants like Microsoft Copilot connect to external data sources and tools. The Intentwise MCP server gives your Copilot agent real-time, permissioned access to your advertising and retail data, plus the Intentwise tools your team already uses for optimization.

Before you start

You'll need:

  • An active Microsoft Copilot Studio license (standalone or bundled with Microsoft 365 Copilot).
  • Permission to create or edit agents in Copilot Studio in the target environment.
  • Generative orchestration enabled on the agent. MCP does not work with classic orchestration.
  • An active Intentwise account.
  • If your tenant restricts agent sharing, expect a one-time admin review before the agent reaches end users.

Connection details

Setting Value
MCP Server URL https://mcp.intentwise.com/mcp/
Authentication OAuth 2.0 (Dynamic discovery)
Refresh URL https://api.intentwise.com/mcp/oauth/token

The trailing slash on the MCP Server URL is required. Connections without it will fail.

Phase 1 — Add Intentwise as a tool

  1. In Copilot Studio, open or create your agent and go to the Tools page.
  2. Click Add a tool → New tool → Model Context Protocol. The MCP onboarding wizard opens.
  3. Fill in: - Server name: Intentwise — becomes the custom-connector display name and must be unique in the environment. - Server description: Commerce observability platform for Amazon and retail-media advertising — query campaigns, accounts, ad performance, and run optimizations. Copilot's orchestrator uses this description to decide when to invoke Intentwise, so keep it specific. - Server URL: https://mcp.intentwise.com/mcp/
  4. Under Authentication, select OAuth 2.0, then choose Dynamic discovery as the OAuth 2.0 type. This tells Copilot Studio to perform DCR and RFC 8414/9728 discovery against Intentwise.
  5. Click Create. Copilot Studio probes the discovery endpoints, registers itself via DCR, and provisions a Power Platform custom connector behind the scenes.
  6. On the Add tool dialog, choose Create new connection, sign in with your Intentwise account (this is the maker's connection, used for authoring and testing only), then click Add and configure.

If creation fails: the most common cause is a stale custom connector left behind by a previous attempt. Go to make.powerapps.com → same environment → Custom Connectors, delete anything named after your MCP tool, wait two minutes, and retry.

Phase 2 — Create the agent

  1. In Copilot Studio, click Create → New agent. Use the guided builder or skip ahead with Configure.
  2. Set the agent's name, description, and system instruction. A working starter prompt:

You are an Intentwise assistant for Amazon and retail-media advertising. Use Intentwise tools to answer questions about campaigns, accounts, and performance. Never fabricate metrics — always call a tool.

  1. Under the agent's Tools section, add the Intentwise MCP tool you created in Phase 1. The agent auto-discovers all tools and resources Intentwise exposes over MCP.
  2. Go to Settings → Security → Authentication and leave Authenticate with Microsoft on. This is required for the agent to appear in Microsoft 365 Copilot and Teams. Leave Require users to sign in on.
  3. Test in the right-hand Test your agent pane. The first invocation prompts you to connect — this is expected; you're connecting your own Intentwise account for testing.

Phase 3 — Publish for your organization

  1. Click Publish on the agent. Publishing is required before any sharing is possible, and every later change also needs a re-publish to take effect.
  2. Go to Channels and confirm Microsoft 365 Copilot and Teams is enabled. This is the channel that surfaces the agent inside the apps your team already uses.
  3. From the agent's overview page, click Share (or Make the agent available to others on the Publish page).
  4. Choose Everyone in your organization, or — recommended for the first release — a specific Microsoft 365 or Entra security group.
  5. If your tenant restricts sharing, the request goes into an admin queue. Your IT admin reviews and deploys it from the Microsoft 365 admin center. Until they do, no end user sees the agent.
  6. Once deployed, the agent appears under Agents in Microsoft 365 Copilot and in the Teams app catalog for everyone in scope.

Phase 4 — End-user first-run

Each user connects their own Intentwise account on first use. There's no admin button that pre-provisions this — it's the standard, per-user OAuth model, and it's what keeps each user's Copilot session scoped to their own Intentwise permissions.

The end-user experience:

  1. Open Microsoft 365 Copilot or Teams, go to Agents, find Intentwise in the org catalog, and click Add.
  2. Start a chat and ask something that requires Intentwise data — for example, "Show my top 5 campaigns by spend last week."
  3. The agent attempts the tool call, sees there's no Intentwise connection for this user, and replies with a Connect card.
  4. Click Connect. A browser popup redirects to the Intentwise sign-in page.
  5. Sign in with Intentwise — username/password or SSO — and grant consent on the OAuth screen.
  6. The popup closes, Copilot stores the access and refresh token in that user's connection, and the original question now succeeds.

After first connect, refresh tokens keep the session alive silently. If the token is revoked or expires beyond refresh, the connection shows Expired and the user sees the Connect card again.

Tip: Let users know in your rollout note that they'll see a one-time prompt to sign in to Intentwise. Without that heads-up, "why am I being asked to log in from inside Copilot?" is the most common support question.

Available Intentwise tools

Once connected, the Intentwise MCP server exposes these tools to your Copilot agent:

Tool What it does
get_organization Retrieves your Intentwise organization details.
get_intentwise_accounts Lists every advertising account linked to your organization.
search_schema Discovers available data tables, columns, and metrics.
get_insights Runs natural-language queries against your advertising and retail data.

The agent decides which tools to call based on each user's question. You don't need to wire prompts to specific tools.

Example prompts to test with

Goal Try asking
Performance overview "How did my ads do last month?"
Campaign analysis "What are my top campaigns by revenue this month?"
Period comparison "Compare my spend this month vs. last month."
Wasted spend "Which keywords are burning money with no sales?"
Inventory-aware action "Which products are about to stock out but still running ads?"

For a deeper set of prompts — by outcome, with expected output and follow-ups — see the AI Gateway Use Case Library.

Troubleshooting

Issue Resolution
Tool creation fails partway through Phase 1 A stale custom connector from a prior attempt is blocking the new one. Delete it under make.powerapps.com → same environment → Custom Connectors, wait two minutes, retry.
The Intentwise sign-in popup doesn't appear Allow popups for copilotstudio.microsoft.com and your Teams/Copilot host. Confirm the Authorization URL in the connector settings is correct.
"Redirect URL mismatch" error Copy the Callback URL from your Copilot Studio MCP settings and share it with your Intentwise account manager — they'll allowlist it.
Token expired / session timeout Confirm the Refresh URL is set to https://api.intentwise.com/mcp/oauth/token.
"Server not reachable" error Confirm the MCP Server URL is https://mcp.intentwise.com/mcp/ (trailing slash required) and that your tenant's egress firewall allows it.
No tools discovered Disconnect and reconnect the server in the agent's Tools panel. If it persists, contact support.
Agent doesn't use Intentwise tools Confirm the Intentwise tool is enabled in the agent's Tools panel. Strengthen the agent's system instruction with explicit guidance to use Intentwise for any advertising or retail data question.
Users in the org can't see the agent Confirm you've Published the latest version, the Microsoft 365 Copilot and Teams channel is on, and — if applicable — your IT admin has deployed the agent from the Microsoft 365 admin center.

Still stuck? Email aigateway@intentwise.com and include the agent name, environment, and a screenshot of the error.