Demystifying Microsoft's Cloud Automation products
summary
Shows concrete demos and tradeoffs: Microsoft Flow uses templates and connectors to save email attachments to OneDrive, supports gateways for on‑prem access, and can trigger local PowerShell via a file system watcher demo; Cloud Shell provides a free interactive PowerShell Core session with a 5 GB cloud drive and short idle timeout (~10–20 minutes); Azure Functions adds PowerShell support (v2), is created from VS Code, runs serverless with a functions 5 minute default execution limit and millisecond billing.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:23The Azure Cloud Automation Suite
- 4:02Azure
- 4:52Azure Automation
- 7:37Microsoft Flow
- 8:31Weekly Reports
- 10:52Templates in Flow
- 11:20Outlook Automation
- 17:20Gateways
- 19:30File System Watcher
- 23:37Azure Cloud Shell
- 29:48Azure Drive
- 36:12Azure Functions
- 37:53Differences between Azure Functions V1 and V2
- 43:01Questions
- 43:15What Do I Find Flow Useful for
related talks
01h 34mM365 Automation using PowerShell in Azure Function
48mRapidly and securely manage your resources with Azure Cloud Shell
43mUsing PowerShell From a Browser to Manage Cloud Resources
03h 03mline tools work better for you
40mWho tests their cloud code anyway?
01h 04mPermit to Cloud - Land with confidence in Azure
43mPowerShell For Every System
54mBuilding Azure Apps