--- title: "AI Activate - Connecting Microsoft 365 Copilot" slug: "ai-activate-connecting-microsoft-365-copilot" description: "Learn how to integrate AI Activate with Microsoft 365 Copilot." tags: ["AI Activate", "Configuration", "Permissions"] updated: 2026-10-01T14:43:42Z published: 2026-10-01T14:43:42Z canonical: "docs.nasuni.com/ai-activate-connecting-microsoft-365-copilot" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.nasuni.com/llms.txt > Use this file to discover all available pages before exploring further. # AI Activate - Connecting Microsoft 365 Copilot ## Overview of AI Activate in Microsoft 365 Copilot This guide covers how to make the Nasuni AI Activate MCP server available in Microsoft 365 Copilot (the Copilot chat app at [copilot.cloud.microsoft](http://copilot.cloud.microsoft)). Microsoft 365 Copilot differs from Copilot Studio, which is the agent builder. Microsoft 365 Copilot does not connect directly to an MCP server. Instead, you build an agent in Copilot Studio that connects to AI Activate, publish the agent, and add the agent to the Teams and Microsoft 365 Copilot channels. End users then add the published agent inside Microsoft 365 Copilot and use the agent in chat. Because Microsoft 365 Copilot connects through a Copilot Studio agent, configure the MCP connection once in Copilot Studio. The steps in this guide reuse the Copilot Studio MCP connection. Follow [AI Activate - Connecting Microsoft Copilot Studio](/v1/docs/aia-connecting-copilot-studio) for the connection itself, and use this guide for the extra steps that expose the agent in Microsoft 365 Copilot. This guide is a companion to [AI Activate - Connecting MCP Clients That Do Not Support Automatic DCR](/v1/docs/aia-connecting-nodcr). ### Why AI Activate Setup Is Simpler Than Microsoft’s Entra-Based Example Microsoft's guide for this flow, [Connect to MCP server via Microsoft 365 Copilot](https://learn.microsoft.com/en-us/power-pages/configure/mcp-connect-clients), describes the Power Pages MCP server, which is secured by Microsoft Entra. Much of the material in that guide exists only because of that Entra dependency: creating a third-party Entra app registration, configuring redirect URIs, entering a Client ID and secret, and using Manual OAuth with an `api://.../mcp` scope. However, Microsoft Entra does not secure AI Activate. AI Activate uses an OAuth server that supports Dynamic Client Registration (DCR). For AI Activate, you therefore skip the entire Entra app-registration track and use Copilot Studio's Dynamic discovery option, which removes most of the prerequisites in Microsoft's guide. You do not need a Microsoft Entra app registration, a manually created Client ID or secret, or an `api://` scope for AI Activate. ## Prerequisites for Microsoft 365 Copilot Integration - A Power Platform environment that DLP policies do not block (which is not the default environment). See the [Copilot Studio guide](/v1/docs/aia-connecting-copilot-studio). - Permission to create and publish an agent in Copilot Studio. - A Microsoft 365 Copilot license for each end user who uses the agent. ## Step 1: Create the Copilot Studio Agent and Connect AI Activate 1. Sign in to [Microsoft Copilot Studio](https://copilotstudio.microsoft.com/). 2. Navigate to the **Agents** page. 3. Click **New Agent.** This agent becomes the interface that Microsoft 365 Copilot users add. 4. Enter a descriptive name for the agent. 5. Click **Tools**. 6. On the **Add a tool** page, click **Add**, then click **Model Context Protocol (MCP)**. The **Add MCP server** page appears. 7. Enter a **Server name** and **Server description**. 8. Enter the **Server URL**. 9. Connect the AI Activate MCP server to the agent as a Tool, using **OAuth 2.0** with **Dynamic discovery**. ![Form to add a Model Context Protocol server with fields for server details and authentication.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/Screenshot 2026-07-01 at 15.03.20.png?sv=2026-02-06&spr=https&st=2026-10-15T01%3A24%3A01Z&se=2026-10-15T02%3A24%3A01Z&sr=c&sp=r&sig=dFxTex%2FDuGLJBE7egCTTcEx%2BFOTb%2Fz8HlYjIxp7EyeE%3D) 1. Click **Publish**, then click **Save and publish**. If Dynamic discovery is unavailable or fails, use the Manual fallback described in [Connecting Copilot Studio](/v1/docs/aia-connecting-copilot-studio). Note that, even in Manual mode, you use Nasuni's OAuth endpoints and a Client ID obtained from the registration procedure. You do not use a Microsoft Entra app registration. ## Step 2: Publish and Share the Agent 1. If not already published, on the agent configuration screen, click **Publish**. 2. Select the menu button (three dots) at the top right, then click **Share**. 3. Select the users or groups who should have access, assign the **Viewer** role so that the users or groups can chat with the agent, then select **Update**. Before sharing the agent, give the agent a clear name, description, and branding so that users understand the agent’s purpose. ## Step 3: Add the Teams and Microsoft 365 Copilot Channel 1. Select **Channels**, then click **Teams** and **Microsoft 365 Copilot**. 2. In the pane that appears, click **Add channel**. 3. After you add the channel, access links for Microsoft 365 Copilot appear. For detailed channel and permission guidance, see Microsoft's [Connect and configure an agent for Teams and Microsoft 365](https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams). ## Step 4: End Users Add and Use the Agent in Microsoft 365 Copilot 1. The user signs in to [Microsoft 365 Copilot](https://copilot.cloud.microsoft/). 2. The user adds the agent from the left pane. The agent appears in the left pane, and the agent’s chat interface opens. 3. The user enters a query for their AI Activate content. First-time users establish individual connections through the Connection Manager: 1. When prompted, select **Open Connection Manager**. 2. Select **Connect**, then the menu button (three dots), then **Add new connection**. 3. Sign in and select **Submit**. 4. Return to the chat and select **Retry** to resubmit the query. Each user signs in individually, which supports AI Activate’s permission-aware model: AI Activate runs each query under the user’s identity and returns only content for which the user has authorization. > ## *Notes* > > - *The MCP connection resides in the Copilot Studio agent. This guide only covers publishing and using the agent in Microsoft 365 Copilot.* > - *AI Activate does not require a Microsoft Entra app registration. The Entra steps in Microsoft's Power Pages guide apply only to Entra-secured servers.* > - *The same server-side open items noted in* [*Connecting Copilot Studio*](/v1/docs/aia-connecting-copilot-studio) *and the canonical hub apply here, including the transport path (root versus* `/mcp`*) and the OAuth discovery endpoints that Dynamic discovery relies on.* > - *For the authoritative and most current setup steps, always defer to the linked Microsoft documentation, since the Microsoft UI can change.*