> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Microsoft 365 Copilot

> Deploy the hosted Enginy MCP server as a Federated Copilot Connector for your whole tenant.

## Before you start

Microsoft 365 Copilot connects to Enginy through a **Federated Copilot Connector** — a different shape from
the developer-tool clients. A tenant admin sets this up once for the whole org; individual users do not
configure anything themselves.

You'll need:

* Global Administrator or AI Administrator permissions in the Microsoft 365 admin center
* Access to the Teams Developer Portal, to register an authentication method

## Set up the connector

1. In the [Microsoft 365 admin center](https://admin.microsoft.com/), go to **Copilot → Connectors →
   Gallery** and select **Create a new connector**.

2. Choose **Connect to MCP server** and enter:

   * **Base URL**: `https://openapi.enginy.ai/mcp/reduced`

   <Warning>
     Microsoft Copilot Studio and Microsoft 365 Copilot connectors refuse to load MCP servers that expose more
     than **70 tools** ("Limiting number of tools to 70"), and the full Enginy catalog is larger than that.
     The `/mcp/reduced` endpoint serves a curated set of the 70 most-used Enginy tools — contacts, companies,
     lists, campaigns, AI Finder, inbox, tasks, AI variables/messages, and enrichment actions runs — so the
     connector loads correctly. Clients without a tool cap should use `https://openapi.enginy.ai/mcp` to get
     the full catalog.
   </Warning>

   <Info>
     Use the **path form** (`/mcp/reduced`), not the equivalent `?toolset=reduced` query parameter: Microsoft
     connector configurations split URLs into host + base path and silently drop query strings, so a
     query-parameter Base URL ends up pointing at the full catalog again.
   </Info>

3. Register an authentication method in the Teams Developer Portal — either **Microsoft Entra SSO** or
   **OAuth 2.0** — and enter the resulting registration ID on the connector.

   <Info>
     Enginy's hosted OAuth flow is a public-client PKCE flow with no client secret by default. If Microsoft's
     OAuth 2.0 registration requires a client ID and secret, contact your Enginy admin to have one issued for
     this connector.
   </Info>

4. Use **staged rollout** to test with specific users or groups before selecting **Deploy to all users**.

## What end users see

Once deployed, users interact with Enginy from Copilot Chat, Word, or Teams like any other connected data
source — no per-user setup, sign-in, or config file required.

<CardGroup cols={2}>
  <Card title="Client support matrix" icon="table-list" href="/mcp/client-support-matrix">
    Compare support levels and setup shapes across every Enginy MCP client.
  </Card>

  <Card title="Security and troubleshooting" icon="triangle-exclamation" href="/mcp/security-troubleshooting">
    Review the auth flow and common failure modes.
  </Card>
</CardGroup>