How to Connect Microsoft Copilot to OnePlan Using the MCP Server

  • Updated

Direct Answer: How to Connect Microsoft Copilot to OnePlan Using the MCP Server

In Microsoft 365, OnePlan is added as a Model Context Protocol tool on an agent built in Copilot Studio. Create a confidential app registration in OnePlan under profile avatar > Register Custom Apps, then add the OnePlan MCP Server to your agent in Copilot Studio with OAuth 2.0 > Manual authentication. Copy the callback URL that Copilot Studio generates back into the OnePlan app registration, connect, test, and publish the agent to Microsoft 365 Copilot and Microsoft Teams.

Note: The OnePlan MCP Server is available in preview to approved customers. To request access, contact your Customer Success Manager.

What This Article Covers: Connecting Microsoft Copilot to OnePlan

This article explains how administrators and Copilot Studio makers connect a Copilot Studio agent to OnePlan through the OnePlan MCP Server so users can reach OnePlan from Microsoft 365 Copilot or Microsoft Teams.

What you will accomplish By the end of this article, you will have registered Copilot Studio as an app in OnePlan, added OnePlan as an MCP tool on an agent, and published the agent to Microsoft 365 Copilot and Microsoft Teams.

Before You Begin: Connecting Microsoft Copilot to OnePlan

Before you begin, make sure you have:

  • OnePlan MCP Server preview access approved for your organization
  • A OnePlan group administrator to create the app registration
  • Copilot Studio maker access, with permission to publish agents in your Microsoft 365 tenant
  • A Microsoft 365 administrator, if your organization requires agents to be approved in the Microsoft 365 admin center
  • The OnePlan MCP Server address for your region:
Region Server address {region} value
Global https://my.oneplan.ai/mcp my
Canada https://ca.oneplan.ai/mcp ca
Australia https://au.oneplan.ai/mcp au
Europe https://eu.oneplan.ai/mcp eu

Note: Copilot Studio uses Power Platform connectors for MCP. If your tenant has Power Platform data loss prevention (DLP) policies, they also apply to the OnePlan tool.

Why This Matters: Connecting Microsoft Copilot to OnePlan

Context: How Copilot Reaches OnePlan

Microsoft 365 Copilot reaches MCP servers through agents. Users can’t add OnePlan directly in Copilot chat. Instead, they chat with the agent you publish, and the agent calls OnePlan tools on their behalf using each user’s own OnePlan sign-in.

Context: Why the Callback URL Is a Placeholder at First

Copilot Studio only shows its callback URL after you create the MCP tool. You create the OnePlan app registration with a temporary placeholder, then replace it with the real callback URL once Copilot Studio generates it.

Step-by-Step: Connecting Microsoft Copilot to OnePlan

Task: Create an App Registration in OnePlan

Follow How to Create an App Registration for the MCP Server in OnePlan with these values:

  • Application Name — Microsoft Copilot, or the agent’s name
  • Callback URL(s) — https://localhost (temporary placeholder)
  • Scope — Group, or Organization to share across groups
  • Public client — Cleared. Copilot Studio requires a Client Secret.

Copy the Client ID and Client Secret.

Task: Add OnePlan as a Tool in Copilot Studio

For Microsoft’s own instructions, see Connect your agent to an existing MCP server.

Starting from Copilot Studio:

  1. Open your agent or create a new one.

  2. Go to Tools, then select Add a tool > New tool > Model Context Protocol.

    Copilot Studio Add a tool dialog with the Model Context Protocol option under Add

  3. Enter the server details: - Server name — OnePlan

    • Server description — Search, read, and update OnePlan plans, resources, financials, work items, and approvals. The agent uses this description to decide when to call OnePlan.
    • Server URL — The OnePlan MCP Server address for your region

  4. For Authentication, select OAuth 2.0, then Manual. OnePlan doesn’t support dynamic client registration yet, so manual settings are required.

  5. Enter the OAuth details, replacing {region} with my, ca, au, or eu: - Client ID — From the OnePlan app registration - Client secret — From the OnePlan app registration - Authorization URL — https://{region}.oneplan.ai/authorize - Token URL template — https://{region}.oneplan.ai/token - Refresh URL — https://{region}.oneplan.ai/token - Scopes — Leave blank

  6. Select Create.

  7. Copy the Callback URL that Copilot Studio displays. Copilot Studio Add MCP server form with OnePlan server details and manual OAuth 2.0 settings

Task: Update the Callback URL in OnePlan

Starting from any page in OnePlan:

  1. Select your profile avatar > Register Custom Apps.
  2. Select Edit (pencil icon) on the app registration you created for Copilot.
  3. Replace https://localhost with the Copilot Studio callback URL. It must match exactly.
  4. Select Update.

Task: Connect and Add the Tool to the Agent

Starting from the Copilot Studio tool wizard:

  1. Select Next.
  2. On Add tool, select Create a new connection, then sign in to OnePlan and choose your group.
  3. Select Add to agent.

Task: Test the Agent

Starting from your agent in Copilot Studio:

  1. Open the test pane.
  2. Ask: “Show me 5 plans in my OnePlan portfolio.”
  3. If prompted, sign in to OnePlan.

Task: Publish the Agent

Starting from your agent in Copilot Studio:

  1. Select Publish.
  2. Go to Channels and add Teams and Microsoft 365 Copilot.
  3. If your organization requires it, have a Microsoft 365 administrator approve the agent in the Microsoft 365 admin center.
  4. Share the agent’s name with your users, along with How to Connect Your AI Assistant to OnePlan Using the MCP Server.

Each user signs in to OnePlan the first time the agent calls a OnePlan tool.

Task: Improve the Agent (Optional)

  • Instructions — Add agent instructions, such as “Always preview financial and resource changes before saving. Ask the user to confirm before approving or rejecting approvals.”
  • Starter prompts — Add 3 to 5 prompts from MCP Server Use Cases in OnePlan - Overview.

Task: Remove Copilot Access

  • To remove OnePlan from the agent: in Copilot Studio, open Tools, select OnePlan, and remove it.
  • To stop all Copilot sign-ins to OnePlan: in OnePlan, select Revoke on the app registration under Register Custom Apps.

Frequently Asked Questions: Connecting Microsoft Copilot to OnePlan

Q: Can users add OnePlan directly in Microsoft 365 Copilot chat? A: No. Microsoft 365 Copilot reaches the OnePlan MCP Server through agents built in Copilot Studio. Users chat with the agent your organization publishes.

Q: Why does sign-in fail with a redirect error when connecting Copilot to OnePlan? A: In OnePlan, the callback URL on the app registration must match the callback URL Copilot Studio shows, exactly. Select Edit on the app registration under Register Custom Apps and paste the URL again.

Q: Why does Copilot Studio need a Client Secret for OnePlan? A: Copilot Studio Manual OAuth requires a Client Secret. In OnePlan, create the app registration as a confidential client by leaving Public client cleared.

Q: Do Power Platform DLP policies apply to the OnePlan tool in Copilot Studio? A: Yes. Copilot Studio uses Power Platform connectors for MCP, so your tenant’s data loss prevention (DLP) policies also apply to the OnePlan tool.

What to Do Next: Connecting Microsoft Copilot to OnePlan

Get started with related tasks:

Learn about related topics:

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.