Copilot Studio and Microsoft 365 Copilot

Microsoft 365 Copilot and Copilot Studio have been available since late 2023. Copilot Studio lets you build business agents without code; Microsoft 365 Copilot makes them available in Teams, Outlook and SharePoint.

Copilot Studio accepts MCP servers directly as tools: you give a name, a description (which the agent reads to know when to use the tool) and the address. The OAuth sign-in can use “Dynamic discovery”: Copilot Studio registers itself with Mailpro.

Connections go through Power Platform connectors: your admin's data loss prevention (DLP) policies also apply to Mailpro.

DeveloperMicrosoft, Redmond (United States)
Copilot StudioAgent › Tools › Add a tool › New tool › Model Context Protocol
Sign-inOAuth 2.0 with “Dynamic discovery” (automatic registration)
TransportStreamable HTTP only
Microsoft 365 CopilotVia a declarative agent (Microsoft 365 Agents Toolkit), deployed by the admin

Copilot agents that actually send

A customer service agent

It confirms an appointment or an order by SMS, within the cap you set for that agent.

A marketing agent in Teams

The team asks it for the monthly newsletter; it prepares it in Mailpro, where it waits for your approval.

A reporting agent

It reads the sending statistics and posts a summary every Monday.

In your existing processes

The agent is triggered by your Power Platform flows and uses Mailpro like any other tool.

Example requests to Microsoft Copilot

  • →“Send the SMS confirmation to the customer on case 4512.”
  • →“Prepare the December internal newsletter for the Employees list.”
  • →“How many follow-up emails went out this week?”
  • →“Add the webinar attendees to the Leads 2026 list.”

Add Mailpro to a Copilot Studio agent

1

In Copilot Studio, open your agent, Tools page, then Add a tool › New tool › Model Context Protocol.

2

Fill in Server name, Server description (“send and track Mailpro emails and SMS”) and Server URL: the server address shown in your Mailpro account, on the AI Assistants (MCP) page.

3

Authentication OAuth 2.0, type Dynamic discovery; Create, Next, then Create a new connection and sign in to Mailpro.

4

Click Add to agent. In Mailpro, set how this agent sends: with approval or direct, with a daily cap.

For Microsoft 365 Copilot and Teams, publish the agent: Channels › Microsoft 365 and Microsoft Teams, check Make agent available in Microsoft Copilot; rolling it out to the whole organization goes through the admin. the step-by-step guide.

Good to know with Microsoft Copilot

The description matters

The agent picks its tools by reading their descriptions: a precise description keeps it from using Mailpro out of context.

DLP policies apply

If your admin blocks custom connectors, they will need to allow the Mailpro one in the environment's data policy.

One agent = one assistant in Mailpro

Each connected agent appears separately in Mailpro, with its own cap and its own log.

On the Mailpro side, the rules are the same for every assistant: by default, each send waits for your approval, or goes out directly within a daily cap; a log keeps track of everything, and one click suspends all sends. The details.

Microsoft Copilot and Mailpro: frequently asked questions

Does Copilot Studio support the Mailpro server?+

Yes: Copilot Studio requires the Streamable HTTP transport and OAuth 2.0, which the Mailpro MCP server uses.

Do I need a specific license?+

You need Copilot Studio to build the agent; use in Microsoft 365 Copilot depends on your Microsoft licenses.

Can an agent send overnight with nobody around?+

Yes, if you allow direct sending, with a daily cap; otherwise, its sends wait for your approval.

All questions: AI assistants FAQ.

Your Copilot agents and Mailpro, in a few minutes.

Create a free Mailpro account, connect your assistant from the AI Assistants page of your account, and stay in control of every send.