A practical guide for agent builders, admin users and end users — 2026 edition
Getting Talkpush MCP working inside Microsoft 365 Copilot takes three roles working together: someone creates and submits an agent, an admin approves it for the organization, and end users chat with it once it's available. The three sections below walk through each part.
Not set up on the Talkpush MCP yet? Head to Getting Started with Talkpush MCP first to understand what it does and grab your credentials.
Microsoft 365 Copilot
The Microsoft 365 Copilot app doesn't let end users connect directly to an MCP server. Instead, it allows users to interact with organization agents (agents built and published by your organization) that are granted access to MCP servers.
In this context, the Talkpush MCP configuration doesn't take place in the Copilot app but in Copilot Studio (a separate agent-building tool). The Talkpush MCP is added as a tool in Copilot Studio, and that tool gets attached to an agent you build. Then, the agent gets published and shows up for users inside the Microsoft 365 Copilot app where they can start conversations and ask the agent to use the MCP.
The work has three stages: build the agent and its Talkpush tool, get it approved for the organization, and then anyone with access can open it inside Microsoft 365 Copilot and start asking questions.
Licenses you'll need
To create and submit the agent: a Copilot Studio User License, assigned to whoever builds the agent, plus an active Copilot Studio tenant license for the organization (the tenant admin acquires this one; it isn't assigned per user).
To approve and publish the agent: no extra license beyond normal Microsoft 365 admin center access.
To use the published agent: a Microsoft 365 Copilot license, plus access to the Power Platform environment where the agent was created. A Power Platform admin needs to add the users (or their security group) to that specific environment to let them generate Talkpush MCP connections.
Creating and submitting the agent
This is an agent creator task, done inside Copilot Studio.
Open Copilot Studio and confirm you're in the right environment (top-right corner).
Go to Tools → New tool → Model Context Protocol.
Fill out the form with the values provided in the Integration Setup section of the Talkpush MCP portal, under Set up your platform → Microsoft 365 Copilot.
Under Authentication, select OAuth 2.0 → Manual. Fill in the required fields with values from the same instructions. Leave Scopes blank.
Select Create. Refresh the page to confirm the tool now appears.
Go to the Agents section and use the chat input at the top to describe the agent to the Agent Builder. Paste the agent creation prompt from the Talkpush MCP portal's instructions and press the send arrow.
Once the agent is created, go to its Tools tab and select Add a tool. Filter by Model Context Protocol, then search "Talkpush" and press Send; the Talkpush tool should appear. Select it.
Under Connection in the tool's profile, you'll see it shows as Not connected, since you haven't created one yet. Select it, then choose Create new connection from the options that appear. This opens a new modal; select Create to trigger the MCP authentication popup, and sign in with the MCP credentials generated in previous steps from the Talkpush MCP portal. Back on the tool's profile, finish with Add and configure.
Copilot Studio currently selects only the first 70 tools listed in the MCP. We're evaluating ways to let you narrow down which tools are available to a given connection.
Once the Talkpush tools are listed on screen, test the agent in the right-hand test panel. Send a simple prompt such as "List the Talkpush companies I have access to".
The agent will reply with a request to authenticate the tools it needs to complete the task (Talkpush MCP in this case). Select the Open connection manager link, which opens a new browser tab. There, select Connect, then Submit; the connection status should show Connected. Close the tab, go back to the agent, and press Retry to get a real response.
At this point the agent works. You can include additional instructions or modify settings to tailor the agent to your needs. However, it only works for you. To make it available to the rest of the organization, it needs to be published and submitted for approval:
On the top menu bar of your agent, press the Publish option. A confirmation panel will open, select Publish again, close the modal and wait for the agent to be published.
Once published, navigate to the Channels tab and select the Microsoft 365 and Microsoft Teams tile.
Make sure Make agent available in Microsoft 365 Copilot is selected, then select Add channel.
After the channel is successfully added, open Availability options. Select Show to everyone in my org, review the requirements, and select Submit to org catalog. Confirm with Yes on the prompt that follows.
Show to everyone in my org is the less restrictive option. You can switch to the Show to my teammates and shared users if you want stricter access.
The agent now shows a pending status. An admin needs to approve it before anyone else in the organization can see it; that's covered in the next section.
Approving the agent for your organization
This is an admin task, done in the Microsoft 365 admin center.
Sign in to the Microsoft 365 admin center with an admin account.
Go to Agents → All agents → Requests.
Select the requested agent and review its details: capabilities, data sources, and the custom actions it can invoke (this is where the Talkpush tool shows up).
If everything looks right, select Publish to store to open the publishing wizard.
Choose which users or groups can install the agent, or select everyone. Optionally, choose users or groups who should get the agent pre-installed automatically instead of finding it themselves.
Select Next, choose a policy template (default is fine unless your organization has a custom one), and select Next again.
Review the permissions the agent is requesting and grant admin consent if everything looks correct.
Select Next, then Publish.
If you'd rather not publish it, select Reject submission instead (next to the Publish to store option).
Once published, the agent becomes available to the audience you selected, in the Built for your org section of the Teams app store and the Microsoft 365 Agent Store.
Using the Talkpush MCP within Microsoft 365 Copilot
These are the steps to follow if you're just the end user, and the agent has already been published by an admin.
If you're the same person who created the agent, you may already have a connection from an earlier step and see a shorter reconnect flow. First-time users go through the steps below.
Open Microsoft 365 Copilot. If the agent was pre-installed for you, it appears directly in the left-hand agent panel; otherwise, find it in the agent catalog and install it first.
Select the agent to open a chat with it and send a simple prompt such as "List the Talkpush companies I have access to".
The agent will reply with a request to authenticate the tools it needs to complete the task (Talkpush MCP). Click the Open connection manager link, which opens a new browser tab. There, select Connect next to the Talkpush tool to see your existing connections for it. Since you don't have one yet, it shows as Not connected; select it, then choose Create new connection from the options that appear.
This opens a new modal; press Create to trigger the MCP authentication popup and sign in with the MCP credentials generated in previous steps from the Talkpush MCP portal. Once authenticated, press Submit, close the browser tab, go back to the Copilot conversation, and press Retry to get a real response.
Done! You can now use the Talkpush MCP from conversations with this agent.
