Power Platform + Microsoft 365: Better Together
Power Platform integrates deeply with Microsoft 365 — Teams, SharePoint, Outlook, and more.
Why does M365 integration matter?
Power Platform lives where your team already works.
Your team uses Teams for chat. SharePoint for files. Outlook for email. Excel for data. What if your custom apps, automations, and websites could plug straight into those tools — no switching between windows, no extra logins?
That is exactly what Power Platform does. Priya built a campaign tracker app and pinned it as a tab in her Teams channel. Carlos triggers approval flows directly from Outlook. Tom pulls form responses from Microsoft Forms into his Power App. Nobody had to leave the tools they already use every day.
M365 integration map
Here is how Power Platform connects to the services your team uses daily:
| M365 Service | How It Integrates with Power Platform |
|---|---|
| Microsoft Teams | Embed Power Apps as tabs, run flows from messages, deploy copilots as Teams bots, use adaptive cards for approvals |
| SharePoint | Use lists as data sources, trigger flows on item changes, build custom forms with Power Apps, surface Power BI dashboards |
| Outlook | Trigger flows on email events, send approvals via actionable messages, embed Power Apps in the Outlook sidebar |
| Excel | Use workbooks as data sources for canvas apps, import data into Dataverse, export flow results to spreadsheets |
| Microsoft Forms | Trigger flows when forms are submitted, push form responses into Dataverse, analyse results in Power BI |
| OneDrive | Store and retrieve files via connectors, trigger flows on file changes, use as a data source for simple apps |
Teams: the ultimate host
Teams deserves special attention because the exam tests it heavily. Power Platform treats Teams as its primary delivery channel.
Power Apps in Teams — Priya pinned her campaign tracker as a tab in the Marketing channel. The entire team accesses it without leaving Teams. She also uses Dataverse for Teams — a lightweight version of Dataverse that comes free with every Teams licence.
Power Automate in Teams — Carlos built an approval flow that posts adaptive cards into a Teams channel. When a manager clicks “Approve” on the card, the flow updates Dataverse and notifies the employee. No email chains. No switching apps.
Copilot Studio in Teams — Carlos deployed his HR chatbot as a Teams app. Employees open a chat with the bot, ask about leave balances, and get answers instantly — all inside Teams.
Dataverse for Teams vs full Dataverse
Dataverse for Teams is a limited version included with Microsoft 365 licences. It lives inside a Teams environment and provides tables, relationships, and basic security — enough for simple team apps.
Full Dataverse requires a premium licence and provides enterprise features: advanced security roles, audit logging, business rules, environment separation, and capacity for millions of rows.
The exam may ask when Dataverse for Teams is sufficient versus when you need full Dataverse. Rule of thumb: if the app is for one team and has simple data, Dataverse for Teams works. If you need row-level security, business rules, or cross-environment deployment, you need full Dataverse.
What are adaptive cards?
Adaptive cards are small, interactive UI snippets that render inside Teams messages, Outlook emails, and other Microsoft hosts. A card can show text, images, buttons, and input fields — all without opening a separate app.
Power Automate uses adaptive cards for approvals: the card appears in Teams with an Approve and Reject button. The user clicks a button, and the flow continues. No navigation, no context-switching.
The exam loves adaptive cards because they demonstrate how Power Platform surfaces actions directly where users work.
How Power Platform services work together
The exam also tests how Power Platform’s own services integrate with each other. Here is the full picture:
| Service Combination | What Happens | Example |
|---|---|---|
| Power Apps + Power Automate | An app triggers a flow, or a flow updates app data | Priya's app submits a campaign brief that triggers an approval flow |
| Power Apps + Dataverse | Apps read and write Dataverse tables with full security | Tom's property app displays listings stored in Dataverse tables |
| Power Automate + Dataverse | Flows trigger on Dataverse changes and write back results | When a record status changes, a flow sends a notification |
| Power Pages + Dataverse | External websites display and collect Dataverse data | Tom's property site lets buyers submit enquiries that create Dataverse records |
| Power Automate + Copilot Studio | Copilots call flows as actions to fetch data or perform tasks | Carlos's HR bot calls a flow to check leave balances in Dataverse |
| Power Apps + Power Pages | Internal app manages data that an external site displays | Tom manages listings in Power Apps; buyers see them on Power Pages |
The pattern is always the same: Dataverse is the hub. Apps write to it. Flows react to changes. Pages display it. Copilots query it. Everything revolves around Dataverse.
Microsoft Graph: the API behind the scenes
Microsoft Graph is the unified API for all Microsoft 365 data — users, emails, calendars, files, Teams messages, and more. Power Platform uses Graph connectors behind the scenes when you connect to M365 services.
You do not need to know Graph API calls for the PL-900 exam. But you should know that:
- Graph is how Power Platform reads M365 data (your profile, your emails, your calendar)
- Custom connectors can call Graph endpoints for advanced scenarios
- Graph is the reason Power Platform can access user photos, org charts, and presence status
Exam tip: licensing for M365 integration
Most M365 connectors (SharePoint, Outlook, Teams, Excel) are standard connectors — included in the base Power Platform licence that comes with Microsoft 365.
But features like Dataverse for Teams apps, premium connectors require additional licensing. The exam may present a scenario and ask which licence is needed.
Key rule: if a scenario uses only standard connectors and Dataverse for Teams, an M365 licence is enough. If it uses premium connectors or full Dataverse, you need a Power Apps or Power Automate premium licence.
Putting it all together: end-to-end scenario
Here is how all four characters use Power Platform with M365 together:
- Priya creates a campaign brief in a Power App pinned to her Teams channel
- The app saves the brief to Dataverse
- Power Automate detects the new record and sends an adaptive card to the Approvers channel in Teams
- The marketing director approves directly from the Teams card
- The flow updates the record status in Dataverse and sends a confirmation email via Outlook
- Aisha monitors all this from the Power Platform Admin Centre, ensuring DLP policies are enforced
- Tom publishes approved campaigns to a Power Pages site for external partners
- Carlos’s HR copilot in Teams answers questions about campaign-related staffing using data from Dataverse
No custom code. No third-party tools. One platform, one data layer, one identity system.
🎬 Video walkthrough
🎬 Video coming soon
Power Platform + Microsoft 365 — PL-900 Domain 1
Power Platform + Microsoft 365 — PL-900 Domain 1
~8 minFlashcards
Knowledge Check
Priya wants her team to use a Power App without leaving Microsoft Teams. How should she make the app available?
Carlos wants his approval flow to let managers approve or reject directly from a Teams message. Which feature should he use?
Which statement best describes how Power Platform services work together? (Select TWO)
Congratulations! You have completed Domain 1 — Business Value of Microsoft Power Platform. You now understand the three core services, connectors and Dataverse, Copilot and AI, Power FX, and how everything integrates with Microsoft 365. Next, we move to Domain 2 where we dive deeper into Power Apps.