Microsoft 365 Copilot

Make Cakewalk available inside Microsoft 365 Copilot by building a Copilot Studio agent on Cakewalk's MCP Gateway and publishing it to your company.

Microsoft 365 Copilot does not connect to a remote MCP server on its own. To bring Cakewalk into Microsoft 365 Copilot for your employees, you build a small agent in Copilot Studio on Cakewalk's MCP Gateway and publish that agent to the Microsoft 365 Copilot and Microsoft Teams channels. Copilot Studio is only the build tool here. The product your employees use is Microsoft 365 Copilot.

Each employee signs in to Cakewalk with their own account the first time they use the agent, so every tool call runs with that person's own access. Cakewalk's gateway supports OAuth 2.0 Dynamic discovery, which registers Copilot Studio automatically through Dynamic Client Registration. There is no Client ID or Client Secret to paste.

If you only want to add Cakewalk to an agent you build and use inside Copilot Studio, without publishing it to Microsoft 365 Copilot, follow Microsoft Copilot Studio instead.

Requirements

• A Copilot Studio license, with permission to create tools and agents in your Power Platform environment.

• A Microsoft 365 Copilot license, required to make the agent available to employees inside Microsoft 365 Copilot.

• A Power Platform environment where MCP connections are not blocked by a data policy.

Install Method

Custom form in Copilot Studio, published to the Microsoft 365 Copilot and Microsoft Teams channels. Each employee creates their own connection and signs in to Cakewalk through the OAuth consent flow when they first use the agent.

If you see a New Copilot Studio experience banner with a Try now button, stay on the current experience for now. The newer experience is still being completed and may hide the Tools and New tool options this guide uses. If those options are missing, switch to the previous Copilot Studio experience when the system offers the legacy option, then continue.

Step 1: Create the Cakewalk MCP tool

1. Go to Copilot Studio.

2. Open Tools and select + New tool.

3. Select Model Context Protocol.

4. Fill in the fields:

   • Server name: Cakewalk MCP

   • Server description (minimum 30 characters):

     MCP Gateway to access to all the tools accepted by your company

   • Server URL:

     https://mcp-gateway.getcakewalk.io/mcp

   • Authentication: OAuth 2.0

   • Type: Dynamic discovery

5. Select Create.

Copilot Studio warns that the MCP server must support OAuth 2.0 Dynamic Client Registration and expose a valid registration_endpoint. Cakewalk's gateway supports this, so you can proceed on Dynamic discovery. Do not use Manual, which needs a Client ID and Client Secret that Cakewalk does not issue on a self serve basis today.

Step 2: Create an agent

1. Go to Agents.

2. Select + Create blank agent (top right).

3. In Name your agent, enter a name, for example Cakewalk MCP Agent, and select Create. You do not need to open Agent settings yet.

Step 3: Add the agent instructions

Open the agent's Instructions and paste the following, then select Save:

You are an internal company agent that helps employees use third party apps through the Cakewalk MCP Gateway.

Use Cakewalk tools only when they are relevant to the user's request.

For each message received from the user, generate a unique UUID and a short summary of the user's request. Pass them to the __cwPromptId and __cwPromptDescription parameters on the Cakewalk MCP Gateway tools.

Never claim that an action succeeded unless the Cakewalk tool result confirms it.

If a tool is unavailable, tell the user they may not have permission or the tool may not be enabled for them.

__cwPromptId and __cwPromptDescription are two parameters the Cakewalk gateway adds to every tool. They let Cakewalk group all of an agent's tool calls back to the single employee request that triggered them in its audit log. The gateway strips both values before forwarding the call, so no prompt text reaches the third party app. The instructions above remind Microsoft 365 Copilot's model to fill them in.

Step 4: Add the Cakewalk tool to the agent

1. Open the agent's Tools tab.

2. Select + Add a tool.

3. Select Model Context Protocol, then search for the name you gave the tool (Cakewalk MCP) and select it.

4. Select Not connected, then Create new connection, then Create.

5. Sign in with your Cakewalk account to authorize the connection.

6. Select Add.

This connection is only to verify the agent works for you. It is not shared with other employees. Each person who uses the published agent creates their own connection and signs in to Cakewalk with their own account, so every tool call runs with that person's own access.

Step 5: Add the Microsoft channels

1. Open the Channels tab.

2. Select Microsoft 365 and Microsoft Teams.

3. In the panel, confirm Make agent available in Microsoft 365 Copilot is checked.

4. Select Add channel.

Step 6: Share the agent with your company

1. Select the three dots button next to Settings and Share.

2. Select Everyone in organization and End user access.

At this point the agent works from inside Copilot Studio.

Step 7: Publish to Microsoft 365 Copilot

To make the agent available inside Microsoft 365 Copilot for everyone you shared it with:

1. Select Publish.

2. Leave Force newest version checked so employees on persistent channels like Microsoft Teams receive the latest version right away.

3. Select Publish.

Verify it works

In the agent's chat, ask a Cakewalk shaped question, for example "Show me my pending access requests in Cakewalk." Confirm the agent calls a Cakewalk tool and returns the expected result.

In Cakewalk, the Microsoft 365 Copilot card on My Agents flips to Connected after the first call.

Data policies

Power Platform data policies regulate MCP connections in Copilot Studio. If a data policy restricts the connector category that MCP traffic uses, the connection to Cakewalk is blocked even after the OAuth flow completes. Confirm with your Power Platform admin that MCP connections are allowed in the target environment.

Troubleshooting

• Tools or New tool do not appear: you are likely on the newer Microsoft 365 Copilot UI. Switch to the previous Copilot Studio experience (the legacy option) and try again.

• Dynamic discovery option does not appear: confirm Copilot Studio is on a release that supports OAuth 2.0 Dynamic Client Registration with discovery. Contact Cakewalk support if you need to fall back to a manual configuration.

• OAuth flow returns an error: confirm the user has a Cakewalk account with at least the User role and that their Power Platform environment permits MCP connections.

• Cakewalk tools do not surface in the agent: confirm the tool was added on the agent's Tools tab. Reload the agent if the tool list looks stale.

• The agent says an action succeeded but nothing changed: the instructions in Step 3 tell the agent never to claim success without a confirming tool result. Confirm the instructions were saved.

Learn more

• Connect your agent to an existing MCP server from Microsoft.

• Publish agents to Microsoft 365 Copilot from Microsoft.

• Configure a data policy in the Power Platform admin center from Microsoft.