Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 38 ยท Connectors and Integration

Connectors - The Big Picture

Learn what Power Apps connectors are, the difference between standard, premium and custom connectors, connections, tabular and action connectors, and licensing basics.

Power Apps is rarely used alone. Real apps read a SharePoint list, send an email, post to Teams, look up a customer in a CRM and call an internal service. Connectors are the ready-made bridges that let an app do all of that without writing authentication and HTTP code yourself.

This lesson explains what a connector is, how connections work, and the vocabulary you need before using one. The services themselves cannot be reached from this site, so every demo is a labelled stand-in.

Connector, connection, action

Three words are often confused:

  • A connector is a wrapper around an API. It defines what you can do (actions and triggers) and how to authenticate. Examples: SharePoint, Office 365 Outlook, Microsoft Teams, SQL Server, Dataverse.
  • A connection is your sign-in to one connector. It stores who you are. One connector can have many connections (for example two different mailboxes).
  • An action is one operation of a connector, such as "Send an email (V2)" or "Get items". Triggers (used in flows) start a process when something happens.

When you add a data source in Power Apps (left panel, Data, then Add data), you choose a connector and then pick or create a connection. The first time you use it, a sign-in dialog appears.

Tabular versus action connectors

  • Tabular connectors expose data as tables you can read and write with Filter, Patch, Collect and LookUp: SharePoint, SQL Server, Dataverse, Excel Online (Business).
  • Action connectors expose calls you invoke as functions: Office 365 Outlook, Teams, Translator. You call them like Office365Outlook.SendEmailV2(to, subject, body).

In a canvas app, an added connector becomes an object in your formulas. A call looks like a function with the connector name as a prefix.

Connector vocabulary

Connector A wrapper around an API
Connection Your sign-in to it
Action One operation
1 / 2

Standard, premium and custom

Connectors are grouped by licence tier:

  • Standard: covered by the licences that come with many Microsoft 365 plans (SharePoint, Outlook, Teams, OneDrive, Excel Online).
  • Premium: need a Power Apps (per app or per user) licence for the people who use the app (SQL Server, HTTP, Salesforce, many others).
  • Custom: connectors you build yourself (Custom Connectors and OpenAPI); they count as premium.
  • Dataverse has its own licensing rules; the common features are premium for an app that uses it.

Licence tiers and the list of connectors change often. Always confirm on Microsoft's official licensing documentation before you build an app that depends on one.

Connections and security

A connection to an action connector usually runs as the person who first created it unless the app uses implicit (user's own) or explicit (shared) connections. This matters:

  • With implicit connections (the default for most Microsoft services), every user signs in with their own account and gets only their own permissions.
  • With shared connections (like SQL with a stored login), everyone uses the same stored credentials. This is convenient and risky: all users can do whatever that login can do.

Choose the model deliberately and document it. For data in SQL Server, prefer per-user authentication where possible.

Modelling connection types: a stand-in

This stand-in shows the difference between a per-user and a shared connection when two users act on the same data. It is a simulation, not real authentication.

JS Stand-in: per-user versus shared connection

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The shared connection let Bob's click perform a write he was not allowed to do himself. That is why governance teams review shared connections.

Calling an action connector

In a canvas app, an action looks like this (read-only, because the services are not available here):

TEXT
Office365Outlook.SendEmailV2(
    "[email protected]",
    "New request",
    "A request was submitted by " & User().FullName
)

Wrap risky calls with IfError so a failed send does not break the app:

TEXT
IfError(
    Office365Outlook.SendEmailV2(txtTo.Text, "Hi", "Body"),
    Notify("Could not send the email.", NotificationType.Error)
)

Simulating a connector call with an error handler

JS Stand-in: handling connector failures

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a connection?

    A connector is the API wrapper; the connection stores the sign-in used with it.
  2. 2. Which kind of connector is read and written with Filter and Patch?

    Tabular connectors present data as tables.
  3. 3. Why can a shared connection be risky?

    Everyone using the app borrows the shared login's rights, which may exceed their own.
  4. 4. A custom connector is licensed as...

    Custom connectors count as premium; confirm current rules in Microsoft's licensing guide.

Summary

  • A connector wraps an API, a connection is your sign-in, an action is one operation.
  • Tabular connectors give tables; action connectors give functions.
  • Standard, premium and custom tiers affect licensing; verify it officially.
  • Prefer per-user connections, and wrap calls with IfError.

Next: Custom Connectors and OpenAPI