---
title: "AI Activate - Connecting Microsoft Copilot Studio"
slug: "ai-activate-connecting-copilot-studio"
description: "Connect Microsoft Copilot Studio to Nasuni AI Activate MCP server using Dynamic Client Registration for seamless OAuth 2.0 setup."
updated: 2026-10-01T15:03:16Z
published: 2026-10-01T15:03:16Z
canonical: "docs.nasuni.com/ai-activate-connecting-copilot-studio"
---

> ## 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 Copilot Studio

## Overview

This guide covers connecting a Microsoft Copilot Studio agent to the Nasuni AI Activate MCP server.

Microsoft Copilot Studio supports automatic Dynamic Client Registration (DCR) through the "**Dynamic discovery**" OAuth 2.0 option. Because AI Activate supports DCR, use “**Dynamic discovery**”: the connector discovers the OAuth endpoints and registers itself automatically, so you do not enter a Client ID, client secret, or scopes.

Copilot Studio also offers a **Manual** OAuth option for servers without DCR. If “**Dynamic discovery**” does not work against the AI Activate endpoint, use **Manual** instead, which uses the same one-time registration described in [AI Activate - Connecting MCP Clients that do not Support Automatic DCR](/v1/docs/aia-connecting-nodcr).

Two points are specific to Copilot Studio and worth noting up front:

- Connectivity runs through Power Platform custom connectors. Adding the MCP server creates a custom connector in your Power Platform environment, so environment selection and Data Loss Prevention (DLP) policies apply. Because tenant DLP policies often block custom connectors in the default environment, avoid the default environment.
- Copilot Studio currently supports only the Streamable transport type. Since SSE transport is deprecated, Copilot Studio no longer supports SSE for MCP.

The steps below summarize Microsoft's documentation. Microsoft's UI does change, so defer to Microsoft's pages for the authoritative current steps.

**Microsoft's documentation**:

- [Connect your agent to an existing MCP server](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent): This page documents the connection and OAuth setup, including **Dynamic discovery** versus **Manual**.
- [Add tools and resources from an MCP server to your agent](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-components-to-agent): After you connect an existing MCP server to Copilot Studio, you can add the server to an agent as a tool. You can access the server tools and resources.

## Endpoint

| Setting | Value |
| --- | --- |
| MCP server URL | `https://preview.mcp.nasuni.com` |
| Transport | Streamable (not SSE) |
| Authentication | OAuth 2.0, Dynamic discovery (DCR) No Client ID, client secret, or scopes to enter. |

## Step 1: Start the MCP Onboarding Wizard

For details, see [Use the MCP onboarding wizard](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent#option-1-use-the-mcp-onboarding-wizard-recommended).

1. Select the Power Platform environment that you want to use. Do not select the default environment. Use the environment picker in the upper-right corner. Alternatively, click **Manage** in the left column, then click **Environments** to display the available environments.
2. Open your agent and go to the **Tools** page.
3. Select **Add a tool**, then **New tool**, then select **Model Context Protocol**. The Model Context Protocol onboarding wizard starts. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-WZRHV57S.png?sv=2026-02-06&spr=https&st=2026-10-15T01%3A53%3A18Z&se=2026-10-15T02%3A53%3A18Z&sr=c&sp=r&sig=7TLcU4tI9U7YJdJo%2B%2Fd%2FVj%2Bsk6yV%2Bf%2F6qY9y0S%2FIG0o%3D)
4. Enter the server details:
  - **Server name**: A descriptive name for the server, such as "Nasuni AI Activate".
  - **Server description**: A short description of the purpose of the server.
  - **Server URL**: The MCP server URL endpoint from the [Endpoint](/v1/docs/ai-activate-connecting-copilot-studio#endpoint) table above.

## Step 2: Configure Authentication (Dynamic Discovery)

1. Under **Authentication**, select **OAuth 2.0**.
2. For the authentication **Type**, select **Dynamic discovery**.
3. Click **Create**.

With Dynamic discovery, the connector finds the authorization and token endpoints in the server metadata and automatically registers through DCR. You do not enter a Client ID or secret.

## Step 3: Create the Connection and Add to the Agent

1. On the **Add tool** dialog, select **Create a new connection**, then select **Create**.
2. When the sign-in window appears, complete the OAuth sign-in.
3. Select **Add** and configure to finish adding the MCP server as a tool.

The agent lists the server's tools on the **Tools** tab. You can turn individual tools on or off using the **Allow all** toggle and the per-tool toggles. For details on adding the server to the agent and managing the server’s tools and resources, see Microsoft's [Add tools and resources from an MCP server to your agent](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-components-to-agent).

> ## *Notes*
> 
> - *Connectivity uses Power Platform custom connectors, so Power Platform environment and DLP policies govern access. Use a non-default environment that DLP policies do not block.*
> - *Use* ***Streamable*** *transport. Copilot Studio does not support SSE.*
> - *Because Microsoft's UI can change, always defer to the linked Microsoft documentation for the authoritative and most current setup steps.*