6.3 Automating Microsoft 365 & Document Processes

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