Microsoft Copilot Setup

Use Kommon Poll MCP with Microsoft Copilot Studio agents and Microsoft 365 Copilot plugin or connector paths controlled by tenant policy.

Platform details checked: 2026-09-02.

Copilot Studio supports connecting an existing MCP server to an agent through the MCP onboarding wizard. Microsoft documents Streamable transport for Copilot Studio MCP and notes that SSE is no longer supported there after August 2025. For Microsoft 365 Copilot plugin scenarios, MCP plugins support Microsoft Entra SSO, Dynamic Client Registration, OAuth 2.0 authorization code flow, and anonymous access; API key authentication is for API plugins, not MCP plugins.

1. Copilot Options

2. Copilot Studio Setup Pattern

1. Open Copilot Studio.
2. Create or open the agent that should use Kommon Poll.
3. Go to the agent's Tools page.
4. Select Add a tool.
5. Select New tool.
6. Select Model Context Protocol.
7. Enter the server name Kommon Poll.
8. Enter the server URL:

https://mcp.kommonpoll.com/mcp

1. Choose OAuth 2.0 authentication.
2. Use Dynamic discovery when the tenant allows DCR with discovery. Kommon Poll publishes OAuth metadata at https://kommonpoll.com/.well-known/oauth-authorization-server.
3. If manual OAuth setup is required, use:

1. Create a new connection or use an existing Kommon Poll connection.
2. Select Add to agent.
3. Open the MCP server settings page and keep only the tools the agent needs enabled.
4. Test a safe read-only prompt.

3. Agent Instructions

Add instructions such as:

Use Kommon Poll when a user asks about monitored brand, campaign, competitor, media, customer, or reputation conversation. Resolve the correct saved search before analysis when ambiguous. State the saved search, date range, filters, and limitations. Use overview analytics for quantitative claims and mentions for evidence. Do not perform external actions unless the user explicitly approves them.

4. Enterprise Workflows

Common Copilot use cases:

• Communications briefings.
• Executive summaries.
• Research agents.
• Customer-experience agents.
• Campaign review agents.
• Crisis monitoring assistants.
• Internal stakeholder update drafts.

For recurring workflows, define:

• Saved search.
• Reporting period.
• Filters.
• Output format.
• Destination.
• Failure behavior.
• Human approval requirements.

5. Governance

Coordinate with Microsoft tenant administrators for:

• Connector and plugin approval.
• OAuth policies.
• Data loss prevention policies.
• Environment and agent ownership.
• Read-only vs write-capable tools.
• Audit and logging requirements.

Keep saved-search create and update tools disabled unless the agent is approved to manage Kommon Poll configuration. Require explicit confirmation for modifying actions.

6. Troubleshooting