Microsoft 365 Copilot

Two ways to reach edisyl from Microsoft 365 Copilot. A Copilot Studio agent works with edisyl’s standard sign-in and takes a few minutes. An admin center connector puts edisyl in every user’s Copilot but needs credentials issued by edisyl first.

https://api.edisyl.com/mcp

Option 1: Copilot Studio agent

Build an agent with edisyl as a tool and publish it to Microsoft 365 Copilot and Teams. Each user signs in with their own edisyl account the first time they use it.

1. In Copilot Studio, open your agent (or create one) and go to Tools.

2. Select Add a tool → New tool → Model Context Protocol.

3. Fill in Server name (edisyl), a Server description the orchestrator can match on (for example, “Ask, teach, and task edisyl Knowledge Packs”), and the Server URL above.

4. Under authentication choose OAuth 2.0, then Dynamic discovery. Select Create.

5. Select Create a new connection, sign in with your edisyl account, then Add to agent.

6. Publish the agent to Microsoft 365 Copilot or Teams from Channels.

Users open the agent in Copilot or Teams and are prompted to connect to edisyl on first use.

Note

Copilot Studio reaches MCP servers through Power Platform connectors, so any data policy that governs connectors in your tenant governs this one too.

Option 2: Admin center connector

A Global or AI Administrator adds edisyl as a custom federated connector in the Microsoft 365 admin center and rolls it out to users. Copilot then uses edisyl’s tools directly in chat.

Requires credentials from edisyl

Microsoft does not support dynamic client registration here. You need a client ID and secret registered with edisyl’s sign-in server, with Microsoft’s redirect URL allowed. Ask your edisyl contact for these before you start. Microsoft also expects federated connectors to expose read-only tools; ask and list_packs fit that, so confirm with your admin whether teach and task should be enabled for this path.

1. In the Teams Developer Portal, select Tools → OAuth Client Registration → + New OAuth connection. Enter the client ID and secret from edisyl, and:

   Field	Value
   Authorization endpoint	https://auth.edisyl.com/auth/v1/oauth/authorize
   Token endpoint	https://auth.edisyl.com/auth/v1/oauth/token
   Refresh endpoint	https://auth.edisyl.com/auth/v1/oauth/token
   Scopes	openid profile email

   Enable PKCE, save, and copy the OAuth client registration ID.

2. In the Microsoft 365 admin center, go to Copilot → Connectors → Gallery, and under Created by your org select Create a new connector → Add.

3. Under Connect to MCP server, select Add. Enter a display name (edisyl), the server URL above, and the registration ID from step 1. Save.

4. From Your Connections, use Staged rollout to test with a group, then Deploy to all users.

Changes take up to 15 minutes to reach users.

Next: Working with a pack from chat.