Study guide

6.3 Automating Microsoft 365 & Document Processes

Microsoft Power Platform Fundamentals PL-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 What PL-900 Tests in 2026 1.2 Exam Logistics & Scoring 1.3 The Power Platform Ecosystem

2 Business Value of Microsoft Power Platform (5-10%)

2.1 Business Value of Power Apps & Power Automate 2.2 Business Value of Dataverse & Connectors 2.3 Business Value of Power Pages, Generative AI & Copilot Studio Agents

3 Manage the Environment: Microsoft Dataverse (20-25%)

3.1 Dataverse vs Traditional Databases; Tables, Columns, Relationships 3.2 Forms, Views & Business Logic (Power Fx, Business Rules) 3.3 Using AI to Create & Edit Dataverse Schema

4 Manage the Environment: Administration & Governance (20-25%)

4.1 Environments & Their Purposes 4.2 The Power Platform Security Model (Roles, Business Units, Teams) 4.3 Data Privacy (DLP), Monitoring/Analytics & ALM Pipelines

5 Demonstrate the Capabilities of Power Apps (20-25%)

5.1 Canvas Apps: Use Cases & Capabilities 5.2 Model-Driven Apps, Plan Designer & Code Apps 5.3 Building Apps with AI (Vibe Experience)

6 Demonstrate the Capabilities of Power Automate (20-25%)

6.1 Cloud & Desktop Flows: Types & Use Cases 6.2 Building Flows: Triggers, Actions & AI Assistance 6.3 Automating Microsoft 365 & Document Processes

7 Agents in Microsoft Copilot Studio (20-25%)

7.1 Building Agents: Topics, Knowledge, Tools (MCP, Agent Flows), Publishing 7.2 Managing Agents: Microsoft Agent 365, Monitoring & Evaluations

6.3 Automating Microsoft 365 & Document Processes

Key Takeaways Explain This Topic AI

The Approvals connector routes requests sequentially or in parallel and captures Approve/Reject decisions to branch the flow.

Teams, Outlook, SharePoint, and Forms are the most commonly automated Microsoft 365 connectors on the PL-900 exam.

Outlook's "Send an email with options" action embeds Approve/Reject buttons directly inside an email message.

Document automation uses AI Builder models to extract data from incoming documents before routing and filing them.

Real-world flows typically chain connectors together, such as Forms to Dataverse to Approvals to a Teams notification.

Last updated: July 2026

Power Automate's most common real-world application is automating everyday work inside Microsoft 365 — routing approvals, keeping Teams and Outlook in sync with business events, and processing the documents that flow through an organization. The PL-900 exam expects you to recognize these Microsoft 365 automation and document-processing scenarios as classic Power Automate use cases.

Approvals

Approvals are one of Power Automate's most widely used capabilities. The Approvals connector (paired with the Approvals app in Teams and Outlook) lets a flow:

Send an approval request to a specific person or group when a business event occurs (a new expense report, a purchase requisition, a document ready for sign-off)

Route the request through sequential approval (one approver after another) or parallel approval (multiple approvers at once)

Capture the approver's decision (Approve/Reject, with optional comments) and branch the flow accordingly — for example, notifying the requester and updating a Dataverse record only after approval

Approval flows typically start as automated flows , triggered when a new record or item is created, and are a frequent exam scenario for demonstrating triggers, actions, and conditional branching together.

Automating Microsoft Teams

Power Automate integrates directly with Microsoft Teams to:

  • Post adaptive card notifications to a channel when a business event occurs
  • Create a Teams meeting or channel automatically from a flow
  • Add or remove team members based on data changes elsewhere (e.g., a new hire record in Dataverse)
  • Trigger a flow directly from a message using Teams message actions
  • Automating Outlook

The Outlook connector supports both triggers and actions, making it one of the most heavily used connectors in Power Automate:

Triggers : "When a new email arrives," "When a new email arrives with an attachment," flagged-email triggers

Actions : "Send an email," "Send an email with options" (embedding Approve/Reject buttons directly in the email body), "Move email to folder"

A common pattern is a flow that watches an inbox for specific incoming messages (such as customer inquiries) and automatically creates a task, logs the request in Dataverse, or notifies the right team.

Automating SharePoint

SharePoint is one of the most common trigger and action sources for business-process automation:

Triggers : "When an item is created," "When an item is created or modified," "When a file is created in a folder"

Actions : "Create item," "Update item," "Get items," "Create file," "Copy file"

Document- and list-centric business processes — such as routing a new contract for review the moment it's uploaded to a SharePoint library — are a signature SharePoint-plus-Power-Automate scenario.

Automating Microsoft Forms

Microsoft Forms triggers are commonly used to kick off flows the instant someone submits a survey, request form, or registration:

Trigger : "When a new response is submitted"

Paired actions typically pull the response details, then create a record, send a notification, or start an approval

This trigger-to-action pattern (Forms submission → Dataverse record → Approval → Notification) is a frequently tested end-to-end scenario because it touches several connectors in one flow.

Document Automation

Beyond app-to-app integration, Power Automate is also used for document automation — processing the documents an organization receives as part of its normal business flow:

Extracting data from incoming documents, using AI Builder document-processing models to pull structured fields, such as invoice number, vendor, and total, out of a PDF or scanned image

  • Routing documents to the correct reviewer, department, or approval chain based on extracted content
  • Filing documents automatically into the correct SharePoint library or Dataverse record once processed

A typical document-automation flow: an invoice arrives as an email attachment → a flow extracts the vendor and amount → routes it for approval if it exceeds a threshold → files the approved invoice in the appropriate SharePoint folder. This combines several concepts from this chapter — a trigger (new email with attachment), actions (extract, condition, approval, file), and connectors (Outlook, AI Builder, Approvals, SharePoint) — into a single automated flow.

Key Takeaways

The Approvals connector supports sequential and parallel approval routing with Approve/Reject decisions captured in the flow

Teams, Outlook, SharePoint, and Forms are the most common Microsoft 365 connectors tested for triggers and actions

Document automation extracts data from incoming documents, routes them for approval, and files them automatically

Real-world flows typically combine multiple connectors: a trigger from one service and actions across several others