Connect Nebuly MCP to Microsoft Copilot

​

Overview

​

Prerequisites

​

Microsoft tenant

• 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.

• A Nebuly account.
• The Nebuly MCP server URL. SaaS users with non custom login page can use https://mcp.nebuly.com/mcp.

​

Create the agent

1. Open Microsoft Copilot Studio.
2. Select Agents, create a new agent, and wait for its overview page to open.
3. Configure a clear name, description, model and instructions.

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

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

​

Test and publish the agent

​

Test the tool

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

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
8. On the left bar select Custom connectors, if not visible select More and Discover all.

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.

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.

​

Onboard additional users

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

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.

​

Users cannot create their own connection

1. Open Power Apps 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.

​

Connection changes do not take effect immediately

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.

​

References

• Extend Microsoft 365 Copilot with agents
• Extend an agent with MCP
• Connect an existing MCP server
• Publish and deploy an agent
• Configure Teams and Microsoft 365 Copilot channels
• Share agents with users
• Share a custom connector
• Troubleshoot Copilot Studio publishing licence errors
• Faq Billing and Licensing