MCP

Microsoft Copilot Setup

Use Kommon Poll MCP with Copilot Studio and Microsoft 365 connector paths where supported by tenant policy.

Use Kommon Poll MCP with Microsoft Copilot Studio and Microsoft 365 Copilot connector paths where supported by tenant policy.

Last verified: confirm before publishing.

Microsoft Copilot capabilities vary across Microsoft 365 Copilot, Copilot Studio, tenant policies, admin approvals, and connector distribution models. Verify exact setup steps before publishing.

1. Copilot Options

Option Best for Notes
Copilot Studio MCP tools Building a managed agent that can call Kommon Poll tools. Usually admin or maker configured.
Microsoft 365 Copilot connector path Organization-wide discovery or federated connector experiences. Use if Kommon Poll is distributed through the supported connector model.
Power Automate or agent flows Scheduled or event-driven workflows. Useful for recurring briefs and governed handoffs.

2. Copilot Studio Setup Pattern

  1. Open Copilot Studio.
  2. Create or open the agent that should use Kommon Poll.
  3. Add an existing MCP server using the supported onboarding wizard.
  4. Enter the Kommon Poll MCP server details provided by Kommon Poll.
  5. Configure OAuth.
  6. Sign in to Kommon Poll.
  7. Select the correct team or workspace.
  8. Approve scopes.
  9. Add the Kommon Poll connection to the agent.
  10. Test a safe read-only prompt.

Use screenshots and exact field labels after the final Copilot Studio UI is verified.

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 approval.
  • OAuth policies.
  • Data loss prevention policies.
  • Environment and agent ownership.
  • Read-only vs write-capable tools.
  • Audit and logging requirements.

If write tools are introduced later, separate them from read-only analysis tools and require explicit confirmation for modifying actions.

6. Troubleshooting

Issue What to check
MCP onboarding is unavailable Confirm Copilot Studio plan, tenant policy, and region availability.
OAuth fails Confirm redirect and OAuth configuration, then reconnect.
Agent does not call Kommon Poll Strengthen agent instructions and verify the tool is enabled for the agent topic.
Data is missing Confirm Kommon Poll team selection and saved-search permissions.
Scheduled flow fails Check Power Automate run history, connector credentials, and retry policy.