Power Platform Connecting to Microsoft 365 SharePoint Teams
Power Platform does not live in isolation. Its real power multiplies when it integrates with the tools your organization already uses every day — SharePoint for documents, Teams for communication, Outlook for email, OneDrive for files, Planner for tasks. This topic covers the integration patterns between Power Platform and Microsoft 365, showing you how apps, flows, reports, and bots connect to the fabric of your digital workplace.
The Microsoft 365 Ecosystem: A Map
MICROSOFT 365 + POWER PLATFORM INTEGRATION MAP
┌─────────────────────────────────────────────────────────────────┐
│ MICROSOFT 365 │
│ │
│ SharePoint ←──────────────────────────── Store and retrieve │
│ (Lists, Pages, files, data, sites │
│ Document Libraries) ◄────────────────┐ │
│ │ │
│ Teams ←─────────────── Post messages, approval actions, │
│ (Chat, Channels, embed apps, host bots │
│ Meetings) ◄───────────┐ │
│ │ │
│ Outlook ←──────────── Send/receive emails, calendar, │
│ (Email, Calendar) approval notifications │
│ │
│ OneDrive ←──────────── Store and read Excel/PDF files │
│ Planner ←──────────── Create and update tasks │
│ Forms ←──────────── Trigger on new response │
│ Excel Online ←─────────── Read and write spreadsheet data │
└─────────────────────────────────────────────────────────────────┘
↑
POWER PLATFORM connects to all of these
through standard connectors (no extra license)
SharePoint Integration: The Most Common Pattern
SharePoint is the most frequently used data source for Power Apps and Power Automate in organizations that do not yet use Dataverse. SharePoint lists store structured data, document libraries store files, and SharePoint pages host embedded Power Apps and Power BI reports.
Power Apps + SharePoint Lists
The quickest way to modernize a SharePoint list is to build a Power App on top of it. Instead of users filling the raw SharePoint list form (which looks like a clunky web form), they use a beautiful, mobile-friendly Power App. The data still lives in SharePoint, but the experience is dramatically better.
SHAREPOINT LIST MODERNIZATION PATTERN BEFORE: SharePoint list form AFTER: Power App Ugly, desktop-only form Mobile-friendly, step-by-step form No validation Real-time validation No conditional fields Fields show/hide based on answers No offline capability Works offline (limited) Users must navigate to SP list App is pinned in Teams or on phone Data: Still in SharePoint (same list, same columns)
Power Automate + SharePoint
Power Automate enhances SharePoint lists with automated behaviors that SharePoint alone cannot provide. Common patterns include approval workflows triggered when a list item is created, notifications to Teams when a document is uploaded to a library, automatic metadata tagging on uploaded files, and scheduled cleanup of old or expired list items.
SHAREPOINT DOCUMENT APPROVAL FLOW
Trigger: When a file is created in "Policy Documents" library
(SharePoint connector)
│
▼
Action: Start and wait for an approval
Assigned to: Legal Team (group email)
Item link: [SharePoint file URL from trigger]
│
┌────┴────┐
Approved Rejected
│ │
Move file Move file
to Approved to Rejected
folder folder
│ │
Update file Send rejection
metadata reason to uploader
Status = Live
Power BI + SharePoint
Embed Power BI reports directly into SharePoint pages using the Power BI web part. This brings analytics to where users already work — the SharePoint intranet — without requiring them to navigate to app.powerbi.com. Open a SharePoint page, click Edit, insert a new web part, search for Power BI, select the web part, and paste your report's URL. Save and publish the page.
Microsoft Teams Integration: Meeting Users Where They Are
Teams has become the primary workplace for many organizations. Power Platform integrates with Teams at multiple levels — apps inside Teams tabs, flows posting to channels, bots living in chats, and Power BI dashboards embedded in team workspaces.
Power Apps in Teams
Any canvas app can be pinned as a Teams tab — available to all members of a Team without them needing to visit make.powerapps.com. From inside a Team in Teams, click the plus (+) button on any channel tab bar. Search for Power Apps. Select your app. Now the app appears as a tab. Team members open it directly from Teams with no extra navigation.
Alternatively, Dataverse for Teams (covered in Topic 3) lets you create simple apps and tables entirely inside Teams, without needing a paid Dataverse license. Go to a Teams channel, click the plus tab, add Power Apps, and build from there. The app and its data live inside the team.
Power Automate + Teams
Teams is a primary notification and action channel for Power Automate. Flows post messages to channels, send direct messages to users, send Adaptive Card actions (where users click buttons inside the Teams message to approve, reject, or respond), and react to Teams events as triggers.
TEAMS ADAPTIVE CARD ACTION FLOW Flow posts a card to Teams channel: ┌─────────────────────────────────────────────────────┐ │ 📋 New Expense Request │ │ From: Priya Sharma │ │ Amount: ₹15,000 │ │ Purpose: Conference registration │ │ │ │ [Approve ✓] [Reject ✗] [View Details] │ └─────────────────────────────────────────────────────┘ Manager clicks [Approve ✓] inside Teams — no app to open. Flow receives the button click response. Flow updates Dataverse record, notifies Priya. This is done using: Action: "Post an Adaptive Card to a Teams channel and wait for response"
Copilot Studio Bots in Teams
As covered in Topic 17, Copilot Studio bots deploy to Teams with one click. The bot appears as a contact users can chat with. Teams passes the user's identity to the bot automatically — no login prompt. This creates seamless employee self-service: ask the bot a question the same way you would ask a colleague.
Outlook Integration
Power Automate + Outlook
Outlook is both a trigger source and an action destination in Power Automate. Flows trigger on new email arrival, emails from specific senders, or emails with specific subject-line keywords. Flows send emails from the flow owner's account or from a shared mailbox. The most common pattern: receive an email, extract information from it (using AI Builder document processing or keyword matching), and create a record in Dataverse or a SharePoint list.
EMAIL-TO-RECORD PATTERN
Trigger: "When a new email arrives" with subject containing "New Purchase Order"
│
▼
Action: "Get email body" — extract the text content
│
▼
Action: AI Builder — extract PO number, vendor name, amount from email text
│
▼
Action: Create row in Dataverse — Purchase Orders table
PO Number: [extracted]
Vendor: [extracted]
Amount: [extracted]
Email Received: [trigger timestamp]
│
▼
Action: Reply to email — "PO received and logged as [Dataverse record link]"
Calendar Integration
The Office 365 Outlook connector in Power Automate provides full calendar access — create events, read upcoming events, update existing events, and respond to meeting invitations. Common uses include automatically creating calendar events when project deadlines are set in Dataverse, sending calendar invitations to customers when service appointments are booked, and querying a person's calendar for free/busy time before scheduling.
OneDrive Integration
OneDrive for Business stores personal and shared files in the cloud. Power Automate connects to OneDrive to monitor folders for new files, read file content (text, Excel, PDF with AI Builder), create new files, move and copy files, and share files with specific people.
ONEDRIVE FILE PROCESSING PATTERN
Trigger: When a file is created in OneDrive folder "/Invoices/Incoming"
│
▼
Action: Get file content (OneDrive)
│
▼
Action: AI Builder — extract invoice data (vendor, amount, due date)
│
▼
Action: Create row in Dataverse (Invoices table)
│
▼
Action: Move file to "/Invoices/Processed" (OneDrive)
│
▼
Action: Post Teams notification — "Invoice from [vendor] logged"
Microsoft Planner Integration
Planner is Microsoft's task management tool. Power Automate creates, updates, and reads Planner tasks. Common uses include creating a Planner task when a Dataverse record is created (a new service request creates a task assigned to the IT team), updating task status when the Dataverse record's status changes, and reading all overdue tasks to send reminder notifications.
DATAVERSE-TO-PLANNER SYNC PATTERN
Trigger: When a row is added in Dataverse (Service Requests table)
│
▼
Action: Create a task (Planner)
Group ID: IT Support team
Plan ID: IT Backlog plan
Bucket ID: New Requests bucket
Title: [Service Request Title from trigger]
Assigned User IDs: [assigned technician's Teams user ID]
Due date: [Due Date from trigger]
│
▼
Action: Update the Dataverse row with the new Planner task ID
(for cross-referencing later)
Microsoft Forms Integration
Forms creates surveys and quizzes that anyone can fill on any device. Power Automate triggers when a new form response is submitted, retrieves the answers, and processes them — creating records, sending notifications, or routing to different workflows based on the answers.
Power Apps cannot read Form responses directly — always use Power Automate as the intermediary between Forms and any data destination. The "When a new response is submitted" trigger (Forms) combined with "Get response details" (Forms) gives you all the form answers in a flow within seconds of submission.
Azure Active Directory (Microsoft Entra) Integration
Power Platform integrates with Microsoft Entra ID (formerly Azure Active Directory) for user and group management. The Office 365 Users connector retrieves user profiles, manager relationships, and department information. The Office 365 Groups connector manages group membership. Flows can add users to groups, send notifications to group members, and check group membership before granting access.
ENTRA ID USE CASES IN FLOWS
Look up who manages a specific employee:
Office365Users.Manager("priya@company.com").DisplayName
→ "Rajesh Kumar"
Get all members of a Teams group:
Office365Groups.ListGroupMembers("group-guid").value
→ Array of user objects
Check if a user is in a specific security group:
(Use HTTP + Entra ID Graph API for this — custom connector covered in Topic 19)
Power Platform + Microsoft Loop
Microsoft Loop is Microsoft's collaborative canvas application — teams co-create content in real time. Power Automate can interact with Loop components through the Microsoft Loop connector (preview), enabling automated content creation, status updates in Loop pages, and triggering flows from Loop workspace events. This integration is rapidly evolving as Loop matures in the Microsoft 365 ecosystem.
Licensing Implications of M365 Integration
All connectors to Microsoft 365 services — SharePoint, Teams, Outlook, OneDrive, Planner, Forms, and Office 365 Users — are standard connectors included in your Microsoft 365 license. Building Power Apps and Power Automate flows that only connect to M365 services requires no premium Power Platform license. The premium license requirement kicks in when you connect to Dataverse, third-party services, or use advanced features like process mining. This is an important fact for organizations with Microsoft 365 but without Power Platform premium licenses — they can still automate and build significantly using standard connectors alone.
Key Points
- SharePoint, Teams, Outlook, OneDrive, Planner, and Forms all connect to Power Platform through free standard connectors included in Microsoft 365.
- Power Apps replaces ugly SharePoint list forms with mobile-friendly, validated, conditional interfaces — data stays in the SharePoint list.
- Power Automate triggers on SharePoint events (file created, item modified) and acts on Teams (post messages, Adaptive Card approvals), Outlook (send/receive emails), and Planner (create/update tasks).
- Embed Power BI reports in SharePoint pages using the Power BI web part — brings analytics directly to the intranet.
- Pin Power Apps as Teams tabs so users access apps without leaving Teams. Pin Copilot Studio bots as Teams contacts for employee self-service.
- The Teams "Post Adaptive Card and wait for response" action lets approvers click buttons inside a Teams message — approval without opening any separate app.
- All M365 integrations use standard connectors — no premium license needed for M365-only automation scenarios.