Azure Functions PowerShell: The Missing Manual
summary
Demos show concrete techniques and outcomes: a push http binding module that replaces awkward HTTP output binding plumbing; local development using azurite and VS Code tasks; Pester tests with auto‑run and live attach debugging to the Functions host; direct Application Insights telemetry via the built‑in AI client instead of opaque rpc wrappers. One production function handles 6.24 million invocations per month at ~0.5s average, costs about $8/month, scales across 26 regions and runs unchanged for three years.
AI-written summary · about
chapters (10)
- 0:00Azure Functions and PowerShell intro
- 3:27Azure Functions architecture
- 7:15HTTP output bindings demo
- 15:22Testing with Pester locally
- 22:04Debugging step-by-step
- 29:24Application Insights telemetry
- 36:26Custom exception tracking
- 41:39Binding to PowerShell modules
- 43:05Leveraging .NET attributes
- 44:32Ticketing system integration
related talks
48mPowerShell in Azure Functions
48mIntroduction to Serverless Functions
25mBuilding AI-Powered Applications with Azure Serverless Functions and C# .NET
57mHands On Azure Functions
01h 01mDos and Don'ts for Serverless and Azure Functions
01h 00mServerless Trends of the Season
07mAzure Functions: Building serverless apps for Azure using Visual Studio Code
42mServer-less compute with .NET based Azure Functions
