M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Connector

Concept

Prebuilt wrapper around an API that lets Power Apps, Power Automate and Copilot Studio read and write data in hundreds of services.

✦ CONCEPTConnectorM365.FM
Title graphic: Connector (Concept)

Relationships

Connector is closely related to Power Platform, Power Automate, Power Apps, Data loss prevention (DLP), Copilot Studio, Azure Logic Apps and 3 more.

Connector is an exam topic of the certification Microsoft Certified: Power Platform Developer Associate (PL-400). Connector is one of the topics of Angeliki Patsiavou.

Full lists: all 9 topics related to Connector

Description

A connector, also referred to as a Power Platform connector or Konnektor, is a prebuilt wrapper around an API. It allows Power Apps, Power Automate and Copilot Studio to read and write data in hundreds of services. Instead of building and handling raw API calls, a maker selects a connector and works with the actions, triggers and data sources it exposes. Connectors sit under the broader Power Platform concept and are one of the main ways the platform reaches data and services outside of itself.

In practice, connectors supply the building blocks of automation and app logic. In Power Automate, triggers and actions in a flow come from connectors. In Power Apps, connectors provide the data sources that an app reads from and writes to. In Copilot Studio, connectors give a copilot access to external systems. A reference list of available connectors is maintained in Microsoft's official connector reference documentation. When a service has no ready-made connector, a custom connector can be created so that the same low-code tooling can still reach it.

Connectors are also a central point for governance. Data loss prevention (DLP) policies classify connectors and control which of them may be used together in the same app or flow. Because every connection to a service passes through a connector, DLP gives administrators a way to separate business data from non-business data and to limit where information can move. Decisions about which connectors are allowed, and how they are grouped, therefore shape what makers can build and what risks they can introduce.

The M365.FM episode "MCP Custom Connector in Copilot Studio: The Complete Integration Guide" covers a concrete use of custom connectors. It describes connecting an MCP server to Copilot Studio through a custom connector, and walks through authentication, schemas, testing, streaming and troubleshooting. This shows that a custom connector can serve as the bridge between Copilot Studio and an external tool server.

A more critical view appears in the episode "Custom Connectors vs Model Context Protocol for Enterprise AI". The episode argues that organizations have treated managed connectors as an easy button for automation, and it presents them as a fragile transport model. It names hidden latency, throttling limits, middleware bottlenecks, retry storms and black-box infrastructure that the organization does not control as concerns. The related episode "Dataverse MCP Integration with Nathan Rose [MVP]" discusses the end of custom integration, noting that building a custom connector for each tool and platform takes considerable time and money, and that standardized solutions can reduce the need to build every connection from scratch. These are positions taken in the episodes rather than universal statements.

The term connector is also used for different technologies, which can cause confusion. The episode "Microsoft Graph Connectors - Simply Explained" describes Microsoft Graph connectors, which integrate external data with Microsoft 365 services so that content from other business applications becomes searchable, for example in Microsoft 365 Copilot. This is distinct from a Power Platform connector, which wraps an API for use in apps and flows. Likewise, the episode "Microsoft Entra Private Access - Simply Explained" mentions verifying connector configurations when troubleshooting connection issues, which refers to a connector in the Microsoft Entra context rather than to a Power Platform connector. When searching for the term, it helps to confirm which product area is meant.

Typical decisions around connectors include whether a prebuilt connector is sufficient or a custom connector is needed, how connectors are classified in DLP policies, and how authentication and testing are handled for custom ones. Understanding the connector concept therefore supports both building solutions in Power Apps, Power Automate and Copilot Studio and governing them across the Power Platform.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept
KindTerm
Also known asPower Platform connectors, Konnektor
DocumentationConnector – Microsoft Learn learn.microsoft.com

Sessions on this topic (2)

Event sessions on Connector:

Key points about Connector

Key points about Connector from the episodes, each with its source episode:

Episodes about Connector

Episodes in which Connector is discussed:

Timeline of episodes about Connector

Articles about Connector (11)

Articles in which Connector is a topic:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What is a connector in the Power Platform? (AI)

A connector is a prebuilt wrapper around an API that lets Power Apps, Power Automate and Copilot Studio read and write data in hundreds of services. It exposes actions, triggers and data sources so makers do not handle API calls directly.

How do connectors relate to data loss prevention (DLP)? (AI)

DLP policies classify connectors and control which of them may be used together in the same app or flow. This makes connectors a central point for governance decisions in the Power Platform.

Is a Microsoft Graph connector the same as a Power Platform connector? (AI)

No. According to the episode "Microsoft Graph Connectors - Simply Explained", Graph connectors bring external data into Microsoft 365 so it becomes searchable, for example in Microsoft 365 Copilot. A Power Platform connector wraps an API for use in apps and flows.

What replaces REST-based managed connectors?

The episode points to protocol-level engineering with gRPC, Protobuf, persistent streams and WebTransport instead of REST connector transport. · From the episode: Custom Connectors vs Model Context Protocol for Enterprise AI

What is the connector illusion?

It is the belief that pre-built low-code connectors reduce complexity, when they hide latency, throttling limits and middleware bottlenecks. · From the episode: Custom Connectors vs Model Context Protocol for Enterprise AI

How does Power Platform DLP protect Copilot Studio agents?

It classifies connectors into Business, Non-Business and Blocked groups and forbids traffic between groups. A tenant-level policy overrules environment policies, forming a fortress at the connector and environment boundary. · From the episode: Lock Down Copilot Studio Agent Permissions with DLP

Relationship map of Connector: linked topics

Related topics in brief

Topics linked to Connector, each briefly explained:

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Community members with expertise in Connector:

Experts on related topics

Experts on topics related to Connector, each with the topic that connects them:

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: