Share via

Copilot connectors versus Power Platform connectors as knowledge sources

This article helps you understand and make informed decisions about integrating external knowledge sources into Copilot Studio agents. It provides a clear comparison between Copilot connectors (formerly Microsoft Graph connectors) and Power Platform connectors as knowledge sources in Copilot Studio.

It explains how Copilot connectors index non-Microsoft data into Microsoft Graph for broad, searchable knowledge and semantic grounding across Microsoft 365. This approach contrasts with Power Platform connectors. These connectors enable real-time API access for reading, writing, and triggering actions from thousands of systems. This ability makes them ideal for up-to-date facts and transactions without data replication.

Summary

  • Copilot connectors (formerly Microsoft Graph connectors): Index non-Microsoft data into Microsoft Graph so Copilot and agents can ground answers with that content across Microsoft 365. This option is best for broad, searchable knowledge that benefits from semantic indexing, citations, and reuse across Microsoft experiences.

  • Power Platform connectors: Calls APIs in real-time to read and/or write data and trigger actions from thousands of systems. In Copilot Studio, you can use them as tools or actions, and as real‑time knowledge with no data movement (currently in preview). Great for up‑to‑date facts and transactions.

Mental model

Think of Copilot connectors as a search and index. They copy and semantically index external content into Microsoft Graph, making it discoverable to Copilot, Microsoft Search, and your agents.

Think of Power Platform connectors as live API bridges. They connect Copilot Studio agents to SaaS and line-of-business systems at runtime to fetch or change data and can now power real‑time knowledge without replicating data.

Side‑by‑side comparison

Dimension Copilot connectors Power Platform connectors
Primary purpose Ingest and index non-Microsoft content into Microsoft Graph for grounding search across Microsoft 365 (including Copilot). Real‑time knowledge with no data movement, or real‑time access to services for read and write operations with tools and actions.
Where it lives Microsoft Graph (semantic index). Power Platform connections (per environment).
How agents use it Added as a knowledge source; agent retrieves and synthesizes answers with citations. Added as a real‑time knowledge source to ground answers live. Or call as a tool or action in topics or at the agent level.
Data movement Yes. Content is copied and indexed into Microsoft 365 and Microsoft Graph (honors source ACLs). No. For real‑time knowledge, the standard connector calls run at runtime under the user's connection and identity.
Best for Documents, knowledge bases, tickets, wikis - content that benefits from semantic ranking, scoping, and citations across Microsoft 365. When data must not be replicated, up‑to‑the‑minute information, and transactions (such as create or update).
Set up and control Admin config in Microsoft 365 admin center; connect sources, define schema, apply semantic labels; quotas and licensing apply. Makers and admins create connections in Power Platform; governed by DLP policies; supports standard, premium, and custom connectors.
Scopes & security Respects source ACLs; supports semantic labels; appears in the Copilot connectors gallery; also powers Microsoft Search. Uses Entra‑based authentication modes; DLP governs where data flows; identity runs calls at runtime; supports custom connector authentication models.
Typical latency Low for retrieval (served from Graph index). Dependent on the target API or service; real‑time round‑trips.
Citations Yes. For example, references appear at the bottom of Copilot answers. Not inherent. Actions can return data; grounding via real‑time knowledge can be cited by the agent’s response logic.

When to use which (decision guide)

Use Copilot connectors when you need to:

  • Make large bodies of external content (for example, ServiceNow KB, Jira, Confluence, GitHub, or Azure DevOps Services) searchable and ground responses across Custom agents, Declarative agents, and Microsoft 365 Copilot.

  • Benefit from semantic indexing and citations in responses, plus reuse in Microsoft Search and other experiences.

Use Power Platform connectors when you need to:

  • Fetch live data ("What's ticket 1234 status?") or perform actions ("Create a case," "Update an order").

  • Ground an answer on real-time enterprise systems without copying data into Microsoft 365 (preview).

  • Apply custom APIs via custom connectors with your own OpenAPI definition and authentication.

Note

If the goal is knowledge discovery and grounded Q&A at scale, start with Copilot connectors. If the goal is real-time knowledge for grounding without copying or transactional steps, use Power Platform connectors.

Architecture at a glance

Copilot connectors (index‑then‑answer)

  1. The admin sets up a connection in Microsoft 365 admin center. Data is indexed into Microsoft Graph.

  2. The agent (or Copilot) issues a semantic query, then Microsoft Graph returns items, and then the LLM grounds answers and cites sources.

Power Platform connectors (real-time)

  1. The agent invokes the real-time knowledge source, or uses a tool or action.

  2. The runtime API calls under the user's connection identity.

  3. The response is used to answer or complete a task.

Setup checklists

Copilot connectors for knowledge

  • In M365 admin center: choose a prebuilt or custom connector; configure schema; apply semantic labels; complete indexing.

  • In Copilot Studio: Add knowledge and select the enterprise connection; ensure Tenant graph grounding with semantic search and authentication are configured. For example, the ExternalItem.Read.All scope is needed when publishing to channels.

Power Platform connectors for real-time knowledge

  • Add knowledge > Advanced > Real-time connector for example, Salesforce, ServiceNow, Azure SQL; select tables/entities; no data replication.

  • Govern usage with Power Platform DLP policies.

Licensing & governance

Copilot connectors: Content consumption is covered by M365/Copilot licensing; indexing quota applies to ingested items.

Power Platform connectors: Availability might depend on standard vs. premium connectors and Copilot Studio plan; governed via Power Platform DLP.

Concrete scenarios

  1. Company-wide knowledge over IT systems (knowledge bases, tickets):

    • Use the ServiceNow and Jira Copilot connectors to index KB articles and tickets into Graph; ground agent answers with citations. Later, add Tool/actions via Power Platform connectors for ticket creation.

  2. Always-fresh line-of-business data without copying:

    • Use Power Platform connectors as real-time knowledge to answer "What's the current priority of INC-123?" or "Show open orders over $50k," without moving data into Microsoft 365.

  3. Mixed mode (most enterprises):

    • Index evergreen content (policies, HR FAQs) with Copilot connectors, and use Power Platform connectors for workflows & transactions (create case, update asset).

Common pitfalls and how to avoid them

  • Microsoft Graph connection isn't displayed in Copilot Studio:
    Ensure your admin creates the connector in the tenant; then add it by selecting Add knowledge > Advanced in Copilot Studio.

  • Unexpected or low-quality answers from a Graph source:
    Verify semantic labels, indexing completeness, and the Tenant graph grounding with semantic search setting; the authentication configuration for the channels where you intend to publish your agent includes the appropriate scopes.

  • Connector works in Teams and Copilot but not in Copilot Studio:
    Differences often come from publishing, authentication settings, or scope. For example, it's missing the ExternalItem.Read.All scope. Check the channel configuration again.

  • Real-time knowledge not visible:
    The feature is in preview and might roll out by region or tenant. Check the Real-time connectors list and tenant availability.

FAQ

Can both connector types ground the same agent?

Yes. Many customers combine Copilot connectors for broad knowledge and Power Platform connectors for up-to-date answers and actions.

How do I manage which knowledge sources makers can use?

Use Power Platform data policies to enable or disable specific knowledge sources by environment or tenant.

Are there "no-copy" options for knowledge?

Yes. Real-time knowledge via Power Platform connectors (currently in preview) processes each request live and doesn't move the data into Microsoft 365.

Related content

  • Last updated on