> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nebuly.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Nebuly MCP to Microsoft Copilot
> Set up the Nebuly MCP Server as a Copilot Studio agent with private, per-user OAuth connections
**Last verified: August 2026**
Copilot integration for Self Hosted customers requires Nebuly >= 1.101.0
This guide explains how to connect the Nebuly MCP Server to a Microsoft Copilot Studio custom agent, publish the agent to Teams and Microsoft 365 Copilot, and onboard users.
Microsoft changes labels and navigation between Copilot Studio and Power Apps releases. This guide uses the labels verified in August 2026. If a label differs in your tenant, use the Microsoft documentation linked in [References](#references) to find the equivalent setting.
## Overview
The integration lets people query Nebuly analytics and invoke Nebuly actions from an agent in Microsoft 365 Copilot or Teams.
| Microsoft object | Purpose |
| -------------------- | ----------------------------------------------------------------- |
| Copilot Studio agent | The chatbot users open in Microsoft 365 Copilot or Teams |
| Custom connector | The definition that connects the agent to the Nebuly MCP Server |
| Connection | A private authentication grant belonging to one user |
| Published channel | Makes the agent available through Teams and Microsoft 365 Copilot |
Agent-level Microsoft authentication and tool-level Nebuly authentication are separate.
Microsoft signs a user into the agent, while the private Nebuly OAuth connection authorizes that user's MCP calls.
## Prerequisites
### Microsoft tenant
**Microsoft 365 or Power Platform administrator**
Confirm the tenant has:
* A Microsoft 365 Copilot license or an applicable Copilot Studio entitlement for the agent maker. Licensing depends on the agent type and tenant billing configuration.
* A Power Platform environment in which the agent and generated connector can be created.
* Copilot Studio authoring access for the agent maker.
* Tenant policy that allows agents with AI features to be published.
* Permission to publish to the **Teams and Microsoft 365 Copilot** channel.
* Administrative approval for the organizational catalog when required by company policy.
Review [Extend Microsoft 365 Copilot with agents](https://learn.microsoft.com/en-us/microsoft-copilot-studio/microsoft-365-copilot-extend-with-agents) before choosing the tenant's publishing and distribution model.
**Agent maker**
Confirm you have:
* A Nebuly account.
* The Nebuly MCP server URL. SaaS users with non custom login page can use `https://mcp.nebuly.com/mcp`.
SaaS users with a custom authentication URL and self-hosted customers should contact their Nebuly representative to enable MCP access. Once enabled, use `https:///mcp`.
## Create the agent
**Agent maker**
1. Open [Microsoft Copilot Studio](https://copilotstudio.microsoft.com/).
2. Select **Agents**, create a new agent, and wait for its overview page to open.
3. Configure a clear name, description, model and instructions.
En example instruction could be something like this:
```text theme={null}
You are responsible for handling requests related to the Nebuly platform through the Nebuly MCP.
For each request:
* Understand the human expert’s intent and determine whether data needs to be retrieved, created, or updated.
* Select and use the most appropriate MCP tool(s) to complete the task.
* Prefer MCP tools over assumptions or manually inferred platform data.
* Use retrieved data and tool results as the source of truth.
* Perform only the actions required to satisfy the request; do not make unrelated changes.
* If required information is missing or the requested action is ambiguous, ask for clarification before making a consequential update.
* Clearly report the outcome, including any relevant results, changes made, or errors encountered.
```
## Add the MCP server
**Agent maker**
1. Open the agent.
2. Click the + icon on **Tools**.
3. Select **+ Add**, then select **Model Context Protocol (MCP)**.
4. Enter the required information, for **Authentication**, select **OAuth 2.0**
and for the OAuth type, select **Dynamic (with discovery)**.
5. Select **Add**, then select **Create new connection**.
6. Complete the Nebuly authorization flow using your own Nebuly account.
7. Click on the added MCP server and ensure that **Authentication Mode** is set to **User**
The initial connection belongs to the agent maker. It is required to finish setup and test the tool, but it must not be used as a shared runtime identity.
For current creation options, see [Extend an agent with MCP](https://learn.microsoft.com/en-us/microsoft-copilot-studio/agent-extend-action-mcp).
For the current wizard, see [Connect an existing MCP server](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent).
For the discovery protocol, see [Configure Dynamic Client Registration](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/plugin-authentication-dynamic-client-registration).
## Test and publish the agent
### Test the tool
**Agent maker**
1. Open the Copilot Studio **Preview** panel and start a new chat session.
2. Ask the agent to list the Nebuly projects available to your account.
### Publish and configure channels
**Agent maker**
1. Select the little arrow near **Publish** and enable Teams + Microsoft 365 publication.
2. **Save and publish** the agent.
3. Once published you can update the agents details to enrich details for your users
4. Click on the share icon in the top bar
5. Enable **End user access** permissions and share
6. Copy links for Copilot or Teams to share the agent with users
7. Before users can actually connect one more step is needed, head to [Microsoft Powerapps](https://make.powerapps.com/)
8. On the left bar select **Custom connectors**, if not visible select **More** and **Discover all**.
Ensure you have selected **Custom connectors** and not **Connections**.
9. Click on the three dots icon, then **Invite another user**.
10. Share the agent with the organization or target user groups, then save.
11. Users are now enabled to create new connections, they'll login with their accounts to access the Nebuly platform.
**Microsoft 365 or Power Platform administrator**
1. Review the agent, connector, requested permissions, and tenant policies.
2. Approve the agent for the organizational catalog when required.
3. Confirm the intended users can install or open the agent.
See [Publish and deploy an agent](https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-fundamentals-publish-channels), [Configure Teams and Microsoft 365 Copilot channels](https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams), and [Share agents with users](https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-share-bots).
## Onboard additional users
**End user**
1. Open the agent after it is made available to you, alternatively you can invoke the agent in a chat with @ followed by the agent selection.
2. Ask a question that uses a Nebuly tool.
3. When prompted, open **Setup connection**. The label can vary by Microsoft experience.
4. Click on **Connect** and follow the steps to create a new connection, you'll be redirect to Nebuly login page to complete the authentication.
5. Return to the agent and retry the connection.
6. You are now able to use the MCP server.
## Troubleshooting
### Publishing is blocked despite a Microsoft 365 Copilot license
This failure occurs in Microsoft 365 or Power Platform before any request reaches the Nebuly OAuth server.
**Microsoft 365 or Power Platform administrator**
1. Confirm the Microsoft 365 Copilot or applicable Copilot Studio license is assigned to the same account that authors and publishes the agent.
2. Check whether **Microsoft Copilot Studio Viral Trial** is also assigned to the account.
3. Remove the viral trial if it conflicts with the paid entitlement.
4. In the Power Platform admin center, go to **Manage → Tenant settings** and verify **Publish bots with AI features** is enabled.
5. Verify the user belongs to any security group configured under **Copilot Studio authors**.
6. Verify the user has access to the selected environment and the required environment role.
7. Sign out of Microsoft 365, Copilot Studio, and Power Apps, then sign back in after the changes propagate.
Use [Troubleshoot Copilot Studio publishing licence errors](https://learn.microsoft.com/en-us/troubleshoot/power-platform/copilot-studio/licensing/publish-license-error) for Microsoft's current checks.
### Users cannot create their own connection
First confirm that the affected user has access to the agent. Then identify the custom connector generated when the Nebuly MCP tool was created:
1. Open [Power Apps](https://make.powerapps.com/) in the same environment as the agent.
2. Open **Custom connectors**. If it isn't visible in the navigation, use the environment-specific custom-connectors page.
3. Find the connector whose name and endpoint correspond to the Nebuly MCP tool.
4. Inspect the connector's sharing permissions separately from the permissions under **Connections**.
5. Never share the agent author's personal connection as a workaround.
6. Allow time for Power Platform permission changes to propagate, then retry from a fresh browser session.
For Microsoft's normative connector-sharing behavior, see [Share a custom connector](https://learn.microsoft.com/en-us/connectors/custom-connectors/share).
### Connection changes do not take effect immediately
Power Platform permission, connector, and connection changes can take several minutes to propagate.
Use this recovery sequence:
1. Save the configuration.
2. Wait several minutes.
3. Republish the agent if the tool configuration changed.
4. Hard-refresh Copilot Studio.
5. Start a new conversation.
6. Use an InPrivate browser profile if identity caching is suspected.
7. Recreate only the affected private connection if necessary.
Avoid deleting or recreating shared agent components until the propagation and fresh-session checks are complete.
## References
* [Extend Microsoft 365 Copilot with agents](https://learn.microsoft.com/en-us/microsoft-copilot-studio/microsoft-365-copilot-extend-with-agents)
* [Extend an agent with MCP](https://learn.microsoft.com/en-us/microsoft-copilot-studio/agent-extend-action-mcp)
* [Connect an existing MCP server](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent)
* [Publish and deploy an agent](https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-fundamentals-publish-channels)
* [Configure Teams and Microsoft 365 Copilot channels](https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams)
* [Share agents with users](https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-share-bots)
* [Share a custom connector](https://learn.microsoft.com/en-us/connectors/custom-connectors/share)
* [Troubleshoot Copilot Studio publishing licence errors](https://learn.microsoft.com/en-us/troubleshoot/power-platform/copilot-studio/licensing/publish-license-error)
* [Faq Billing and Licensing](https://learn.microsoft.com/en-us/microsoft-copilot-studio/faq-billing-licensing)