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

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

You'll land on the Copilot Studio home screen.

Click Agents in the left sidebar.

You'll see a list of your existing agents. Click New agent to create a new one, or open an existing agent you want to add MedScout to.

You'll land in the agent builder with the Build tab selected. On the right side panel, you'll see sections for Model, Skills, Tools, Knowledge, Connected agents, and Memory.

Click the + button next to Tools in the right side panel.

The "Add a tool" dialog opens on the Featured tab. (The MCP tab lists servers already published for your organization, such as Microsoft 365 services — you don't need it for this step.)

Click the + Add button in the top right corner of the dialog. A dropdown appears — select Model Context Protocol (MCP).

The "Add MCP server" form appears. Fill in the following:

Under Authentication, select OAuth 2.0.

A second row of options appears labeled Configuration type. Select Dynamic (with discovery).

This is the simplest option — Copilot Studio will automatically discover MedScout's authentication endpoints. No client ID, secret, or manual URL configuration is needed.

Click Add once completed.

You'll see the "Select a connection" screen showing MedScout with a status of Not connected.

Click the Connection dropdown, then click Create new connection.

A panel appears titled "Creating a connection to use MedScout in this flow." The display name is prefilled with MedScout — you can leave it as is or change it.

Click Create.

You will be redirected to sign in with your MedScout account credentials. Complete the login process.

After logging in, you'll return to the "Select a connection" screen. The connection now shows a green checkmark, confirming it's active.

Click Add to finish adding MedScout to your agent. MedScout now appears under Tools in the agent's right side panel.

Select it to open the Edit tool dialog. Confirm that Connection shows MedScout with a green checkmark and that Authentication is set to End user account (each person signs in with their own MedScout account). Under Tool permissions, Allow all is on by default, so every MedScout tool is available; turn it off if you want to switch individual tools on or off. Click Done.

To confirm it works, open the Preview tab, ask a question that needs MedScout data, and check the activity trace to see which MedScout tool was called.

In the agent builder's right side panel, click the + button next to Channels.

On the "Add a channel" dialog, select Teams + Microsoft 365.

Under Available in, keep Microsoft Copilot and Microsoft Teams selected. Microsoft requires the agent to be available in Microsoft Copilot in order to share it (Step 11). This setting can't be changed after publishing.

Recommended: before adding the channel, open the About info tab. The developer name, website, terms of use, and privacy statement shown there are what your users see. They default to the maker's name and Microsoft links, so replace them with your organization's details.

Click Add channel.

Before publishing, make sure the agent has a name, description, and instructions (the Publish dialog lists anything that's missing) and that you've tested it in the Preview tab.

Click Publish in the top right corner of the agent builder. The Publish dialog lists the Teams + Microsoft 365 channel. Click Publish agent.

When publishing finishes, you'll see "Your agent published successfully." Click Share.

The Share dialog opens. Under Organization, Everyone in your organization starts out as "No permissions, unless specified."

Open that dropdown and select End user access (everyone in your organization can find and use the agent, but can't see its details or edit it). You can also add specific people or groups using the search box at the top (Microsoft 365 groups with

SecurityEnabled set to false can't be added).

Click Share.

You'll see "Agent shared successfully." Click Copy link (Microsoft Teams) and send the link to the people who should use MedScout. You can reopen the Share panel at any time with the Share icon next to Publish in the top menu bar. Installation links don't work in the Teams mobile app — to make the agent available to Teams mobile users, list it in your organization's agent store (Part 3).

Sharing the link in Step 11 is all your users need to install MedScout. Use these steps only if you also want the agent listed in your organization's Teams and Microsoft 365 agent store, which requires Microsoft 365 admin approval.

After publishing, you'll see the "Agent published" dialog. This is where you make the agent available to your organization. Click the Submit to org catalog button.

Scroll down to the Show in the store section and click Submit to org catalog.

A confirmation dialog appears asking "Give everyone access to this agent?" — click Yes, submit.

After submitting, the "Submit to org catalog" button will be greyed out, confirming the submission. Click Publish to finalize. The dialog won't close automatically — just click the X in the top right corner to dismiss it. The agent is now pending admin approval.

A Microsoft 365 admin needs to approve the agent before it's available to users.

Click on the agent to open its details, then click Publish to store (or, if you don't want to publish it, choose Reject submission from the … menu next to the agent name)

After clicking "Publish to store", a 4-step wizard walks you through deploying the agent:

The agent is now published and available in the admin center.

If you shared the agent by link (Step 11): users open the link you copied. Teams shows the agent's page — they click Add.

When it finishes, they choose Open to use it in Teams, or Open with Copilot to use it in Microsoft 365 Copilot.

If you listed the agent in your organization's agent store (Part 3): once deployed, users simply open Microsoft 365 Copilot and find the MedScout agent in the sidebar under their available agents.

Click on MedScout to open the agent and start using it.

On their first interaction, they'll be prompted to sign in with their own MedScout credentials. After that, the agent can access MedScout tools on their behalf. Microsoft ties connections to each user's identity, so if someone hasn't signed in yet, MedScout tools won't work for them even though the agent works for you.

These steps follow Microsoft's current documentation for the new Copilot Studio agent experience:

Contact MedScout support at [email protected].