Microsoft Copilot

Connect Microsoft 365 Copilot to your Clawnify workspace. Copilot can then look up records in your workspace’s apps, read your Company Knowledge, and hand tasks to your agents, from Copilot Chat and from Copilot in Outlook, Word, Excel and PowerPoint.

Microsoft calls this a custom federated connector. Copilot asks the Clawnify MCP gateway each time you use it, and nothing from Clawnify is copied into Microsoft 365.

Before you start

• A Copilot licence for each person who uses it. Custom connectors need a Microsoft 365 Copilot licence (for example Microsoft 365 Copilot Business). The free Copilot Chat that comes with Microsoft 365 can’t use them.
• A Microsoft 365 admin, once. Someone with the Global Administrator or AI Administrator role does the setup below, in about 15 minutes.
• Your workspace’s MCP address. In Clawnify, open Knowledge, expand Use this knowledge in ChatGPT, Claude, Codex & Copilot, and copy it from the Microsoft Copilot row. The address is https://mcp.clawnify.com/mcp, or one ending in /c/…/mcp if you belong to more than one workspace. That one always points at the workspace you have open.

Set up (Microsoft 365 admin)

1. Get a Clawnify client for Microsoft

Email support@clawnify.com from the address you use in Clawnify and ask for a Microsoft Copilot client, naming your workspace. We reply with a Client ID and a Client secret made for your organization. Paste the secret only into the Teams Developer Portal in step 2, and don’t forward it.

2. Register the client in the Teams Developer Portal

Open dev.teams.microsoft.com, go to Tools → OAuth client registration, and select Register client. Fill it in:

The endpoints are the ones the gateway publishes at https://mcp.clawnify.com/.well-known/oauth-authorization-server.

Select Save and copy the OAuth client registration ID it shows.

3. Create the connector in the Microsoft 365 admin center

1. In admin.microsoft.com, go to Copilot → Connectors → Gallery. On Create a new connector, select Add, then Add under Connect to MCP server.
2. Fill in:
   • Display name: Clawnify
   • Description: for example, Our Clawnify workspace: its apps (orders, customers, invoices), Company Knowledge, task board and AI agents. Use it to look up or update records, read company knowledge, list tasks, and hand a task to an agent. Copilot uses this text to decide when to call Clawnify.
   • MCP endpoint URL: your workspace’s MCP address
   • Developer name: Clawnify
   • Website URL: https://www.clawnify.com
   • Privacy policy URL: https://app.clawnify.com/privacy
   • Terms of use URL: https://app.clawnify.com/terms
3. Set Authentication type to OAuth 2.0, paste the registration ID from step 2 into Reference ID, and select Authorize. Sign in to Clawnify and approve. The Reference ID gets a green check.
4. Tick the notice and select Create.

By default everyone in your tenant’s User access setting gets the connector. To limit it, open Copilot → Connectors → Your connections → Clawnify → Staged rollout. Changes can take up to 10 minutes to reach users.

4. Each person connects once

In Copilot Chat, open … → Settings → Sources, find Clawnify, select Connect, then Continue to Clawnify, and approve. Copilot now acts as that person in Clawnify: it sees and changes only what their Clawnify account can.

Verify

In a new Copilot chat, ask:

Using Clawnify, list the apps in our workspace.

Copilot shows Connecting to Clawnify… and then answers with your apps, citing Clawnify as a source.

What Copilot asks before it changes anything

Copilot sorts Clawnify’s tools into two groups, under Settings → Sources → Clawnify:

• Read tools run without asking: listing apps, reading a record, searching Company Knowledge.
• Write/Delete tools need approval: creating or deleting an app, writing to an app, publishing a document, creating or completing a task. Copilot shows a card with Allow once, Allow for conversation, Always allow or Cancel. Nothing is sent to Clawnify until you choose.

We suggest keeping the delete tools on Needs approval. You can reset a tool you set to Always allow on the same screen.

Microsoft notes that these approval settings apply to Copilot Chat. It doesn’t say how approvals behave when you use the connector from Copilot in Outlook, Word, Excel or PowerPoint.

Limits

• Copilot shows the connector with its initials, not the Clawnify logo.
• Every person who uses it needs a Copilot licence (see Before you start).
• What Copilot reads from Clawnify is processed by Microsoft under your Microsoft 365 agreement, like the rest of your Copilot data.

Troubleshooting

• Copilot says it has no Clawnify connector. The person hasn’t connected yet under Settings → Sources, the connector was created less than 10 minutes ago, they are outside its staged rollout or User access, or they have no Copilot licence.
• Save stays greyed out in the Developer Portal. Existing Teams app is selected without an app ID. Choose Any Teams app.
• Authorize fails. Check the Client ID and secret from step 1, the two endpoints, and that the client password method is Request body parameters.
• Copilot works in the wrong workspace. If you belong to several workspaces, use the /c/…/mcp address of the one you want.