This guide walks you through connecting the MedScout MCP server to your Microsoft Copilot Studio agent and deploying it to your organization. Once complete, your team can use MedScout's provider intelligence and targeting tools directly within Copilot and Teams.

Prerequisites

• A Microsoft Copilot Studio license with admin access — this setup only needs to be done once by an admin
• A MedScout account with valid credentials
• Access to the Microsoft 365 admin center (only needed if you also list the agent in your organization's agent store — see Part 3)
• The agent's user authentication set to Authenticate with Microsoft — Microsoft requires this before an agent can be shared (Step 11). To check it, open the … menu in the agent toolbar → Settings → Safety & access tab → Authentication
• Your organization must allow users to access and install agents, or they won't be able to install the agent from a link. In the Microsoft 365 admin center, check Agents → Settings → User access and Agent and plugin access (Microsoft's older instructions refer to the Teams admin center for this)
• Per Microsoft's sharing documentation, people you share the agent with need a Copilot Studio per-user license (or a trial)

Billing note: agents built in the new Copilot Studio experience use usage-based billing — building, testing, and using the agent can consume Copilot Credits.

Already set up? If your Copilot Studio admin has already added MedScout to your agent, you don't need to follow these steps. You'll simply be prompted to sign in with your MedScout credentials on first use. If you see a "Not connected" message when trying to use MedScout, check with your admin to confirm the setup is complete.

Part 1: Create the Agent

Step 1: Open Copilot Studio

Go to copilotstudio.microsoft.com and sign in with your Microsoft 365 account.

You'll land on the Copilot Studio home screen.

Step 2: Create or open an agent

Click Agents in the left sidebar.