Microsoft Power Automate Training Course

Participants can assess a business process and define automation requirements before building a flow.

• Process mapping identifies hand-offs, rules, exceptions and system touchpoints
• Automation candidate scoring using volume, variability, risk and effort
• SIPOC diagrams define suppliers, inputs, process steps, outputs and customers
• Business rules converted into trigger, action, condition and escalation requirements
• RACI assignments clarify process ownership, approvals and support responsibilities
• Acceptance criteria specify expected outcomes, exception routes and audit evidence

Participants can configure dependable flow triggers and prevent unwanted or duplicate runs.

• Automated, instant and scheduled cloud flow trigger patterns
• Trigger conditions prevent unwanted runs before actions execute
• Recurrence schedules, time zones and daylight-saving considerations
• Outlook, SharePoint and Teams triggers for Microsoft 365 events
• Trigger outputs, dynamic content tokens and schema inspection
• Idempotent flow design avoids duplicate business transactions

Participants can sequence actions and transform data for downstream flow processing.

• Compose, Select, Filter array and Join actions shape data
• JSON parsing converts connector responses into typed dynamic content
• Data Operations actions restructure records before downstream processing
• Variables, arrays and objects retain state across flow branches
• Apply to each settings control iteration order and concurrency
• Pagination retrieves complete result sets from list-based connectors

Participants can build approval processes with routing, reminders, decisions and escalation paths.

• Start and wait for an approval action configuration
• Sequential and parallel approvals match delegated decision rights
• Adaptive Card approval requests deliver actionable Teams notifications
• Reminder schedules identify pending decisions before service deadlines
• Escalation branches route overdue requests to alternate approvers
• Approval outcomes update records, notify requesters and retain evidence

Participants can automate SharePoint records and documents while preserving metadata and control points.

• SharePoint list triggers respond to created and modified items
• Get items filtering uses OData queries and indexed columns
• Document library metadata drives routing, approval and retention actions
• Content approval status supports controlled document review processes
• Create item and update item actions maintain workflow records
• Folder paths, file identifiers and attachments require distinct handling

Participants can automate common Microsoft 365 communications and spreadsheet-based operational tasks.

• Outlook email triggers classify messages using sender and subject rules
• Teams posts, chats and channel messages support operational notifications
• Excel Online tables provide structured rows for flow processing
• Workbook locking, table design and row limits affect reliability
• Email templates use HTML formatting, dynamic fields and links
• Calendar actions schedule follow-ups, meetings and service reminders

Participants can implement decision rules using conditions, switch cases and Power Automate expressions.

• Condition actions evaluate Boolean comparisons and null-value scenarios
• Switch actions manage multiple categories without nested conditions
• Expression functions manipulate strings, dates, numbers and arrays
• coalesce, empty and equals functions handle missing input values
• Date formatting converts timestamps for messages and business records
• Scope actions group logical stages within complex flow designs

Participants can design flows that manage failures, recover safely and notify support teams.

• Configure run after settings create success, failure and timeout paths
• Try-catch-finally patterns use Scope actions for controlled recovery
• Retry policies address transient connector and service failures
• Terminate actions record deliberate cancellations and failed executions
• Exception logs capture correlation identifiers, inputs and action outputs
• Support notifications distinguish business exceptions from technical faults

Participants can build a multi-stage request workflow using Microsoft 365 connectors and exception controls.

• Request intake captures mandatory fields, attachments and requestor details
• SharePoint records provide a traceable workflow system of record
• Approval routing applies value thresholds, roles and delegation rules
• Parallel branches send confirmations while approval processing continues
• Exception queues record incomplete submissions and rejected requests
• Run-history review verifies routing, updates and notification outcomes

Participants can use Dataverse tables and relationships as reliable data foundations for flows.

• Dataverse tables, columns, choices and primary keys explained
• One-to-many relationships model requests, approvals and supporting records
• Business rules enforce field requirements before flow processing
• Dataverse triggers respond to row creation and status changes
• Lookup fields preserve relationships between related workflow records
• Row ownership, security roles and teams control record access

Participants can package automation assets in solutions and prepare them for controlled deployment.

• Solution-aware flows package components for managed deployment
• Connection references separate authentication from flow definition
• Environment variables store configurable URLs, addresses and identifiers
• Managed and unmanaged solutions serve distinct lifecycle purposes
• Export and import processes move tested assets between environments
• Version notes document changes, dependencies and rollback decisions

Participants can identify suitable desktop automation tasks and configure attended desktop flow logic.

• Desktop flow use cases address legacy applications without connectors
• Recorder actions capture desktop interactions for repeatable procedures
• UI elements provide resilient targeting beyond screen coordinates
• Variables, conditions and loops control desktop flow decisions
• Attended versus unattended RPA determines execution and licensing requirements
• Desktop flow exceptions return meaningful status to cloud flows

Participants can call REST APIs safely and interpret structured responses within a flow.

• HTTP actions call REST endpoints using methods, headers and bodies
• OAuth 2.0 concepts explain token-based API authentication
• JSON request bodies map flow values to API fields
• Response status codes distinguish successful, client and server errors
• Pagination links retrieve multi-page results from external services
• Custom connector design documents endpoints, authentication and operations

Participants can assess where AI Builder adds value to document and text-based workflows.

• AI Builder model types support extraction, prediction and classification
• Document processing models capture fields from structured business documents
• Confidence scores route low-certainty results for human review
• Prompt actions generate drafts requiring defined review controls
• Training data quality affects model accuracy and operational suitability
• Licensing and capacity considerations govern AI Builder deployment decisions

Participants can apply governance controls that protect data while supporting approved automation development.

• Data loss prevention policies classify business and non-business connectors
• Connector groups prevent prohibited data transfers between services
• Microsoft Entra ID authentication governs user and service access
• Least-privilege connection ownership reduces unnecessary data exposure
• Flow sharing permissions distinguish owner, co-owner and run-only users
• Audit records support investigation of automation changes and activity

Participants can monitor production flows, diagnose performance issues and define support procedures.

• Run history filters identify recurring failures and delayed executions
• Action duration analysis locates connector and processing bottlenecks
• Analytics metrics track runs, failures, success rates and usage
• Correlation identifiers connect support tickets to individual flow executions
• Support runbooks define triage, ownership, recovery and communications
• Change requests assess business impact before modifying live flows

Participants can test Power Automate solutions against normal, boundary and failure scenarios.

• Test cases cover happy paths, boundary values and exception conditions
• Test data design protects sensitive information during validation
• User acceptance testing verifies process rules with business owners
• Regression testing checks existing routes after flow changes
• Expected results document records, notifications, approvals and audit outputs
• Defect logs prioritise functional errors, control gaps and usability issues

Participants can prepare an automation for adoption, ownership transfer and sustainable operational use.

• Operating models define central, federated and hybrid maker responsibilities
• Centre of Excellence practices coordinate standards, support and reuse
• Process owners approve rules, outcomes and change priorities
• User communications explain workflow changes, notifications and exception routes
• Training materials distinguish requestor, approver and support-user responsibilities
• Benefits tracking measures cycle time, rework, compliance and workload

Participants can build, review and present a complete Power Automate solution with documentation, controls and test evidence.

• Process requirements define scope, roles, rules, data and exceptions
• Solution architecture selects environments, connectors, ownership and dependencies
• Cloud flow implementation automates intake, routing, approvals and notifications
• Exception paths handle invalid data, failures and overdue decisions
• Test evidence demonstrates expected results across defined acceptance criteria
• Peer review assesses maintainability, security, supportability and business value