본문으로 바로가기

강의

Intermediate Power Automate

중급기술 수준

업데이트됨 2026. 7.

Build reliable Power Automate cloud flows with triggers, branching, approvals, error handling, and production handover.

무료로 강의 시작

Power PlatformArtificial Intelligence

3시간

16 동영상

57 연습 문제

3,950 XP

성취 증명서

수천 개 기업의 학습자들이 사랑하는

팀을 교육하시나요?

비즈니스용으로 체험해 보세요

강의 설명

Automating a business process is easy until the data is messy, the logic branches, and someone needs to approve before anything moves forward. This course takes you past the basics and into the patterns that make Power Automate flows reliable enough for production.

Choose the Right Trigger and Fetch Data Efficiently

Start by comparing Recurrence, Automated, and Manual triggers, then build a daily renewal sweep with time-zone-aware scheduling. Connect to SharePoint with Get items and OData Filter Queries to pull only the records you need, resolve people via Office 365 Users lookups, and attach contract documents with the right link-vs-attach security posture.

Branch, Route, and Handle Failures

Add Condition actions to split flows on contract value (with type-coercion safety nets), replace nested Conditions with Switch for multi-status routing, and configure run-after settings so one failed action doesn't kill an entire sweep. Learn the diagnostic loop: test, inspect run history, fix, and resubmit.

Route high-value renewals through Start and Wait for an Approval, swap binary Approve/Reject for Custom Responses, and branch on the Outcome. Then prepare for handover: share the flow with co-owners for continuity, assign run-only access for end users, and verify the pipeline is live.

A capstone exercise brings every piece together into one pipeline you can confidently hand to an operations team.

선수 조건

이 강의에는 선수 과목이 없습니다

1

Triggers that fit the job

Detect upcoming contract renewals before they lapse. Walk through the three Power Automate trigger families, pick the right one for a real-world automation problem, configure time zones so a scheduled flow fires when users expect, and add trigger conditions that stop the flow from running on weekends.

Picking the right trigger

Match the scenario to its trigger type

Why doesn't a Recurrence trigger fit here?

Scheduled triggers

Build the daily renewal sweep

Spot the wrong time-zone setting

Why are there no weekend runs?

Automated triggers and conditions

Build a "renewal submitted" automated flow

Add a weekday-only trigger condition

2

Acting on structured data

Fetch, filter, and enrich contract records using SharePoint Get items with OData queries, resolve responsible partners via Office 365 Users lookups, attach contract documents with the correct link-vs-attach security posture, draft notification emails with dynamic content, and write back an audit trail so the flow remembers what it has already done.

Getting data: fetching structured records

Add Get items for upcoming renewals

Where does this filter belong?

Why did Get items return 0 records?

Resolving people: the lookup pattern

Resolve the responsible partner's email

Which token gives the email address?

People-reference anatomy

Working with SharePoint documents

Look up the contract PDF and capture its link

Why does the recipient see "Access denied"?

Attach or link?

Notification and audit-trail write-back

Send notification and update the audit trail

What changed in the audit workbook?

Audit trail simulator

3

Conditional logic and reliability

Route contracts by value with Condition actions and by status with Switch, guarding against type-coercion gotchas and silent Default misses. Then add run-after failure branches so one broken connector call doesn't kill the entire sweep, and close the diagnostic loop with test, run history, and Show raw outputs.

Condition: branching on contract value

Branch the flow on contract value

Why does the Condition always take "If no"?

Switch: routing by status

Replace nested Conditions with a Switch

Spot the missing Default

Switch builder sandbox

Run-after: catching failures gracefully

Add a "log failure to SharePoint" branch

Run-after state picker

Why didn't the failure-handler fire?

Test, run history, and the diagnostic loop

Find and fix the seeded bug

Which Flow Checker warnings matter?

4

Approvals and the renewal pipeline

Route high-value renewals through the Approvals connector, swap binary Approve/Reject for Custom Responses, and branch on the Outcome (capital-A casing trap included). Prepare the flow for production with shared ownership, run-only access, and connection continuity, then assemble everything into a capstone pipeline.

Approvals fundamentals: Start and wait

Add an approval for high-value renewals

What does the approver see?

Why didn't the "If approved" branch run?

Approval types and custom responses

Replace Approve/Reject with custom responses

Approval-type sandbox

Match the scenario to the approval type

Sharing, ownership, and going to production

Inspect the Share dialog

Owner or run-only?

Why does this flow keep failing after handover?

The full renewal pipeline

Assemble the final renewal pipeline

Renewal pipeline report card

Congratulations!

Intermediate Power Automate

강의
완료

수료증 획득

LinkedIn 프로필, 이력서 또는 CV에 이 인증서를 추가하세요
소셜 미디어와 성과 평가에서 공유하세요지금 등록

19백만 명 이상의 학습자와 함께 Intermediate Power Automate을(를) 시작하세요!

DataCamp for Mobile을 통해 데이터 분석 능력을 향상시키세요.

모바일 강좌와 매일 5분 코딩 챌린지를 통해 이동 중에도 학습 효과를 높이세요.