Intentwise AI Gateway Setup Guide for Microsoft Copilot

Prerequisites

• An active Microsoft Copilot Studio license (standalone or as part of Microsoft 365 Copilot)
• Access to create or edit agents in Microsoft Copilot Studio
• An active Intentwise account 

Connection Details

Gather the following Intentwise OAuth 2.0 credentials before starting.

Setup Steps

Phase 1 — Add the Intentwise MCP server as a tool

Prerequisites: Copilot Studio user license, an environment you can author in, and generative orchestration turned on for the agent (MCP doesn’t work with classic orchestration).

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 (this becomes the custom-connector display name — must be unique in the environment)
   • Server description: short, clear sentence about what Intentwise does. The orchestrator uses this to decide when to call your server, so make it specific (e.g. “Commerce observability platform for Amazon and retail-media advertising — query campaigns, accounts, ad performance, and run optimizations”).
   • Server URL: https://mcp.intentwise.com/mcp
4. Under authentication, select OAuth 2.0, then Dynamic discovery as the OAuth 2.0 type. This tells Copilot Studio to do DCR + 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 once (this is the maker’s connection, used for authoring/testing only — not shared with end users). Then Add and configure.
   

 If it fails: the most common cause is a stale orphaned custom connector from a prior attempt. Go to make.powerapps.com → same environment → Custom Connectors → delete anything named after your MCP, wait a couple of minutes, retry.

 

Phase 2 — Create the agent

1. In Copilot Studio, Create → New agent. Use the guided builder or “skip to configure.”
2. Set the basics: name, description, and a clear system instruction. Something like: “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.”
3. Under Tools for the agent, add the Intentwise MCP tool you created in Phase 1. The agent will auto-discover all Intentwise tools and resources exposed over MCP.
4. Go to Settings → Security → Authentication and leave Authenticate with Microsoft on (this is the default for new agents and is required if you want the agent to appear in Microsoft 365 Copilot and Teams). Leave Require users to sign in on.
5. Test in the right-hand Test your agent pane. Ask something that exercises Intentwise tools. The first invocation will prompt you to connect — that’s expected, you’re connecting your own account for testing.

Phase 3 — Publish so everyone in the org can access it

1. Click Publish on the agent. Publishing is required before any sharing is possible — every change you make later 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 puts the agent in front of org users inside the apps they already use).
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 a specific Microsoft 365 / Entra security group if you want narrower rollout — recommended for a first release).
5. If your tenant has restricted sharing policies (most enterprise tenants do): the share request goes into an admin queue. Your IT admin reviews and deploys it to the org catalog from the Microsoft 365 admin center. Until they do, no end user sees it.
6. Once deployed, the agent shows up under Agents in Microsoft 365 Copilot and in the Teams app catalog for everyone in scope.

Phase 4 — End-user first-run with their own Intentwise credentials

it’s a per-user flow, not something the admin can pre-provision. The experience is:

1. User opens Microsoft 365 Copilot (or Teams), goes to Agents, finds Intentwise in the org catalog, and clicks Add.
2. User starts a chat with the agent and asks something that needs Intentwise data (e.g. “Show my top 5 campaigns by spend last week”).
3. The agent attempts the tool call, sees there’s no connection for this user, and replies with a Connect card in the chat.
4. User clicks Connect. A browser popup opens, redirects to auth.intentwise.com (or wherever your Intentwise authorization endpoint lives), and shows your standard Intentwise sign-in screen.
5. User authenticates against Intentwise — their own username/password, SSO, whatever you support — and grants consent on the OAuth consent screen.
6. Popup closes, Copilot Studio stores the access + refresh token in that user’s connection. User goes back to the chat and re-asks (or clicks “Try again”); the tool call now succeeds, scoped to their Intentwise identity and org permissions.
7. On subsequent days, refresh tokens keep the connection alive silently. If the token is revoked or expires beyond refresh, the connection shows Expired and the user gets the Connect card again.

One thing to tell your users up front: each person has to do the connect step once, on first use. There’s no admin button that does it for everyone. If you have customers asking “why am I being asked to log in to Intentwise from inside Copilot,” the answer is that this is the standard, per-user OAuth model — and it’s the right thing for audit and tenant isolation.

Available Intentwise Tools

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

Copilot Troubleshooting