[ ABORT TO HUD ]
SEQ. 1

Cloud Flows & Connectors

⚡ Power Automate Essentials⏱ 15 min⭐ 100 BASE XP⌨ HANDS-ON LAB

Automating Business Processes

Power Automate is Microsoft's workflow automation platform with access to 1,000+ pre-built connectors spanning Microsoft services, third-party SaaS, and custom APIs. Cloud flows are the most common flow type — event-driven automations that run in the Microsoft cloud.

Copilot NL Flow Authoring

As of 2026, the primary interface for building Power Automate is Copilot NL (Natural Language) Authoring. Users simply describe the workflow ("When an email from Contoso arrives with an invoice, extract the data and add it to SAP"), and Copilot generates the trigger, actions, loops, and conditions automatically.

Flow Anatomy

ComponentRoleExample
TriggerThe event that starts the flow"When a new email arrives", "When a Dataverse row is created", "On a schedule"
ActionsSteps the flow performs after triggering"Send an email", "Create a Dataverse row", "Post to Teams"
ConditionsBranching logic based on data values"If priority equals High, notify manager"
LoopsIterate over arrays of data"For each item in the SharePoint list, send a reminder"
Error HandlingGraceful failure management"Run after failure" configuration, try-catch-finally patterns

Connector Tiers

TierLicense RequiredExamples
StandardIncluded with M365SharePoint, Outlook, Teams, OneDrive, Excel Online
PremiumPower Automate Premium licenseDataverse, SQL Server, HTTP, Azure services, Salesforce
CustomPremium licenseYour own REST APIs wrapped as connectors

Error Handling Best Practices

  • Configure 'Run After': Set actions to run after failure, timeout, or skip — not just success
  • Try-Catch Pattern: Use parallel branches with 'Run After: Failed' to catch and handle errors
  • Retry Policies: Configure automatic retries with exponential backoff for transient API failures
  • Alerts: Send Teams/email notifications when critical flows fail

Flow Types

  • Automated (Cloud) Flows: Triggered by events (email, form submission, Dataverse change)
  • Instant (Button) Flows: Triggered manually by a user clicking a button
  • Scheduled Flows: Run on a recurring schedule (daily, weekly, hourly)
  • Desktop Flows (RPA): Automate legacy desktop applications using UI automation
  • Agent Flows (2026): AI-powered flows that combine reasoning with structured execution
💡 Key Insight: Always implement error handling in production flows. The #1 cause of flow failures is unhandled API timeouts and transient errors. Use retry policies and 'Run After: Failed' branches to build resilient automations.
⌨ HANDS-ON LABAudit Connections & Connectors
⭐ +150 XP

Governance review: the CoE team needs to know which connections exist in the environment and which connectors are available before approving new flows.

1List every connection created in the selected environment.
2List the connectors available in this environment (standard + premium + custom).
lab-sandbox — simulated environment
INFINITY LAB SANDBOX v2.6 — simulated shell
Type the command for the current objective. Helpers: "hint", "solution", "clear".
$
OBJECTIVE 1 / 2 — type "hint" if stuck
SYNAPSE VERIFICATION
QUERY 1 // 3
What is a Trigger in Power Automate?
A button in the UI
The event that starts a flow — such as receiving an email, a Dataverse record change, or a scheduled time
A type of connector
An error handler
Cloud Flows & Connectors Tutorial | Power Automate Essentials — Power Platform Academy