Skip to content
Tutorials Center
My learning

Topics

Lesson 26 of 38 ยท Connectors and Integration

SharePoint, Outlook and Teams Integration

Use the Microsoft 365 connectors in Power Apps: SharePoint lists, Outlook email and calendar, Teams messages and an app embedded in Teams. Includes safe stand-ins.

Most organizations already live in Microsoft 365. SharePoint stores lists and documents, Outlook holds mail and calendars, and Teams is where people talk. Power Apps connects to all three with standard connectors, so a small app can fit right into the tools people use every day.

SharePoint lists

The SharePoint connector turns a list into a table. To add one, choose Data, Add data, SharePoint, enter the site URL and pick the list. You can then use it like any table:

TEXT
Filter(Equipment, Status.Value = "Active")
Patch(Equipment, Defaults(Equipment), { Title: "Projector", Quantity: 2 })

Things to remember about SharePoint columns:

  • Choice columns are records with a .Value property (Status.Value).
  • Person columns are records with DisplayName, Email and Claims.
  • Lookup columns return a record with Id and Value.
  • Column internal names may differ from display names (a column renamed from "Title" keeps the internal name). Power Apps shows display names but the formula bar warns when they are ambiguous.
  • Delegation is limited: SharePoint supports Filter with =, StartsWith, And, Or on indexed columns, but not in or Search on every column. See Delegation and Performance.

Large lists need indexed columns: a SharePoint list view threshold stops queries on unindexed columns over 5,000 items. Index the columns you filter on.

Outlook email and calendar

The Office 365 Outlook connector is an action connector:

TEXT
Office365Outlook.SendEmailV2("[email protected]", "Subject", "<p>HTML body</p>")
Office365Outlook.V4CalendarGetItems("Calendar", ...)

Tips:

  • SendEmailV2 sends as the signed-in user and the message appears in their Sent Items. For automated messages use a shared mailbox and the Send an email from a shared mailbox (V2) action in a flow.
  • The body accepts HTML. Escape user-typed text before placing it in HTML to avoid broken markup: use Substitute on < and >.
  • Use IfError so a failed send is reported instead of silently ignored.

Microsoft Teams

There are two directions:

  1. An app inside Teams. From the maker portal choose your app, then Add to Teams (or Details, Add to Teams) and download or publish it as a Teams app. People then open it as a tab or a personal app, signed in automatically.
  2. An app that talks to Teams. The Microsoft Teams connector posts messages and cards: Post message in a chat or channel. Use it from a flow so permissions are clear.

Another path is Power Apps in Microsoft Teams (the Dataverse for Teams feature): apps and tables stored in a team's own lightweight Dataverse environment, made inside Teams. It is handy for small team tools, with a smaller feature set than full Dataverse.

Three Microsoft 365 partners

SharePoint Lists as tables
Outlook Email and calendar actions
Teams Embed the app, post messages

All three are standard connectors.

1 / 2

Working with complex SharePoint columns: a stand-in

SharePoint's choice and person columns are records, not strings. This stand-in shows the shape of the data and how a filter formula works with it.

JS Stand-in: filtering list items with choice columns

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

No output.

Safe email bodies: a stand-in

When a user types text that ends up inside an HTML email, special characters can break the layout. This stand-in escapes them as you would with Substitute.

JS Stand-in: escape user text for an HTML email

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

No output.

In Power Fx the same idea is a chain of Substitute calls, escaping & first so that the later replacements are not double-escaped.

Permissions to plan for

  • SharePoint: users need rights on the list. The app does not grant them. A list owner can give Contribute to the group.
  • Outlook: the sender is the signed-in user (unless a flow uses another account).
  • Teams: app sharing in Teams follows the Power Apps sharing; people also need to be allowed to use custom apps in Teams (a Teams admin setting).
  • Whatever the connector, remember the connection runs under the account that created it (Connectors: The Big Picture).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. How do you read the text of a SharePoint choice column named Status?

    Choice columns are records, so the visible text is in the Value property.
  2. 2. Why index SharePoint columns used in filters?

    Unindexed filters over about 5,000 items hit the threshold and fail or are slow.
  3. 3. Under which account does SendEmailV2 normally send?

    The message is sent as the user whose connection is used, and it appears in their Sent Items.
  4. 4. Which is the correct way to use an app in Teams?

    Use Add to Teams to publish the app as a Teams app.

Summary

  • SharePoint lists become tables; remember choice, person and lookup columns are records, and index filtered columns.
  • Outlook's SendEmailV2 sends as the user; escape user text in HTML bodies and wrap in IfError.
  • Teams can host your app and a flow can post messages; Dataverse for Teams offers lightweight team apps.
  • Plan list permissions and connection ownership early.

Next: Component Libraries