Building Resilient Automations
summary
Shows concrete patterns and runnable code: PowerShell scripts that make user-creation idempotent by checking employee ID and looping to unique UPNs, Graph API calls with paging, throttling (429) and token-refresh handled by try/catch/finally plus bounded retries, split download/upload pipelines that prevent reprocessing, and blob uploads that use hash-based duplicate detection and timestamped temp paths. Demonstrations hit real failures (too-long job title, existing UPNs) and are adjusted to succeed, illustrating idempotent operations and practical recovery techniques.
AI-written summary · about
chapters (10)
- 0:00Resilient automations intro
- 1:46Why automations matter
- 3:10Designing idempotent automations
- 8:57Handling API call failures
- 16:26Error handling best practices
- 21:05File transfer challenges
- 31:28Modular automation blocks
- 33:35User-induced failures
- 37:32Advanced error recovery
- 43:29Q&A
related talks
01h 11mWorkshop - Automating for DevOps
18mIdempotence isn't a dirty word
41mPowerShell for Life: Automate the Everyday
01h 47mBuilding PowerShell Applications that Operate on a Planetary Scale
01h 30mConjuring data with APIs
52mPerformance & Stability Anti patterns
29mServices, Scale, Backgrounding and WTF is going on here?!???
26mThe tools and techniques behind resilient systems