A Microsoft 365 Copilot federated connector makes Cloverleaf a read-only data source for everyday Copilot answers. After an admin adds the connector, each user connects their own Cloverleaf account. Copilot Chat and Researcher can then use Cloverleaf coaching data when it is relevant to a question.

The admin center does not use the words "federated connector" in its menus. You create the connector from Create a new connector and chooseConnect to MCP server. Only the form's help panel calls it a "custom federated connector".

This guide covers the custom federated connector that an admin adds in their own tenant. It is not the same as the full Cloverleaf agent for Microsoft Copilot.

What you'll learn

How to add the Cloverleaf connector in the Microsoft 365 admin center
How to control who sees the connector
How each user connects their Cloverleaf account in Copilot
How to confirm the connection worked

Who can do this

Part 1 (admin): a Microsoft 365 Global Administrator or AI Administrator. You also need a Cloverleaf org admin to turn on MCP.
Part 2 (each user): any user with a Microsoft 365 Copilot license who is in the connector's rollout group.

Federated connector vs. the other Cloverleaf options

	Federated connector	Read-only Copilot Studio tool	Full agent
Who sets it up	M365 admin, in the admin center	Copilot Studio maker	Published by Cloverleaf
Where it works	Copilot Chat, Researcher	Copilot Chat, Researcher, Excel (through a named agent)	Copilot Chat (as a named agent)
Access	Read-only	Read-only	Read and write, with interactive widgets
MCP server URL	`https://app.cloverleaf.me/api/mcp/federated`	`https://app.cloverleaf.me/api/mcp/federated`	`https://app.cloverleaf.me/api/mcp`

Before you start

Turn on MCP in Cloverleaf. In Cloverleaf, open Organization settings > Configuration > Integrations, find the Model Context Protocol (MCP)card, and click Enable. If the card shows Disable, MCP is already on, and you can skip this step.
Get the OAuth reference ID for the Cloverleaf connector from your Cloverleaf account team.

Part 1: Add the connector (admin)

Step 1: Create a new connector

Go to the Microsoft 365 admin center.
In the left menu, click Copilot > Connectors.
Stay on the Gallery tab. Under Categories, click Created by your org.
On the Create a new connector card, click Add.
The Custom connector panel opens. On the Connect to MCP servercard, click Add. Do not choose Sync from data source. That option copies data into Microsoft 365, and Cloverleaf does not support it.

Step 2: Fill in the connector details

The Connect to MCP server form opens. The help panel on the right saysCustom federated connectors [MCP], which confirms you are in the correct form.

Fill in the fields below. The Display name field starts with the text "External". Delete that text before you type the name.

Field	Value
Display name	Cloverleaf
Description	see the recommended text below
MCP endpoint URL	`https://app.cloverleaf.me/api/mcp/federated`
Developer name	Cloverleaf
Website URL	`https://cloverleaf.me`
Privacy policy URL	`https://cloverleaf.me/privacy`
Terms of use URL	`https://cloverleaf.me/terms`

Copilot uses the description to decide when to use Cloverleaf. We recommend this text:

Cloverleaf personality-centered coaching data: DISC and other assessment insights for you and your teammates, relationship dynamics, daily coaching, and coaching history.

The MCP endpoint URL must end in /federated. The other Cloverleaf URL (/api/mcp) does not work for this connector.

The form with the Cloverleaf details filled in

For Authentication type, choose OAuth 2.0.
In Reference ID, paste the reference ID from your Cloverleaf account team. The Authorize button turns on.

Step 3: Authorize Cloverleaf

Click Authorize. A Cloverleaf window opens.
Sign in to Cloverleaf the same way you usually do. If you are already signed in, Cloverleaf skips this screen.
Review the permissions and click Authorize. The window closes.

The form now shows a green check mark in the Reference ID field, and theAuthorize button changes to Edit.

Reference ID accepted, with a green check mark and the Edit button

Step 4: Create the connector

Read the Notice and select the checkbox.
Click Create. When Microsoft finishes, you see Success withCreated connection and Linking data source both checked.
Click Done.

Step 5: Choose who gets the connector

Important: a new connector is visible to all users in your organization as soon as you create it. To start with a small group, change the rollout right away.

Open the Your Connections tab and click Cloverleaf. The details panel opens.
Next to Staged rollout, click Change.
Choose All users, No users, or Specific users/groups. To start small, choose Specific users/groups and add yourself or a test group.
Click Save.

Rollout changes can take up to 15 minutes to reach users. To change the description later, click Edit description in the details panel.

To stop the connector for a time, use Disable, not Delete. Disablekeeps the configuration. Delete removes it permanently.

Part 2: Connect your Cloverleaf account (each user)

Step 6: Connect Cloverleaf in Copilot

Go to m365.cloud.microsoft/chat.
In the message box, click +, then click Change data sources.
Search for Cloverleaf and click Connect.
Copilot shows Connect Cloverleaf. Click Continue to Cloverleaf.
If Cloverleaf asks you to sign in, sign in the same way you usually do.
Review the permissions and click Authorize. The window closes.

You do this one time. Copilot keeps your Cloverleaf sign-in for later chats.

You'll know it worked when...

Cloverleaf shows as on in Select sources, and Copilot answers with your real Cloverleaf data.

Try one of these prompts in Copilot Chat:

"What's my daily coaching from Cloverleaf today?"
"What's Jamie's DISC profile, and how should I work with them?"
"Find my last few coaching conversations in Cloverleaf."

Copilot answering with Cloverleaf data and a Cloverleaf citation

What can I do once connected?

Copilot can search and read your Cloverleaf data when it helps answer your question. For example, it can use a teammate's DISC profile while you draft an email to them. The connector is read-only. It cannot start an assessment or change anything in Cloverleaf. For those, usethe full agent.

Copilot's Connect dialog says that Copilot can "read and write" your content. Microsoft shows that text for every connector. The Cloverleaf connector only reads.

Troubleshooting

Symptom	Likely cause	What to do
Copilot asks you to connect again and again, with no error	The OAuth registration does not match the endpoint URL, or the sign-in is stale	Make sure the MCP endpoint URL is exactly `https://app.cloverleaf.me/api/mcp/federated`. Then sign out of Cloverleaf at app.cloverleaf.me and connect again.
Cloverleaf is not in Select sources	You are not in the staged rollout, or the rollout is not live yet	Ask your admin to add you to the rollout. Wait up to 15 minutes after a change.
Cloverleaf is connected, but Copilot does not use it	Copilot did not pick Cloverleaf for the question	Name Cloverleaf in the prompt, for example "from Cloverleaf". Admins can make the connector description more specific (Step 2 or Step 5).
The sign-in fails with `invalid_redirect_uri`	The OAuth registration uses a redirect URI that Cloverleaf does not know	Send a screenshot of the error to your Cloverleaf account team.

If none of these fix it, contact your Cloverleaf account team with a screenshot of what you see.

How do I add Cloverleaf as a federated connector in Microsoft 365 Copilot?