Best practices for automating Azure with PowerShell...
summary
Clear, actionable items: use Azure PowerShell on PowerShell 7 or higher and keep two module versions side‑by‑side so scripts can be tested when monthly releases land; prefer system-assigned managed identity for VMs/Arc to avoid secrets; use az preview or dynamic extension install for missing commands; create GitHub Actions credentials with PS-Sodium to create encrypted GitHub credentials instead of copy‑pasting secrets; run with -Debug for reproducible bug reports; use Cloud Shell upload, browse resource IDs, and code - to inspect JSON outputs.
AI-written summary · about
chapters (8)
- 0:00Azure automation with PowerShell
- 3:48Azure PowerShell vs CLI
- 10:51Breaking changes in Azure PowerShell
- 15:26Secure Azure authentication
- 24:57Azure CLI coverage and defaults
- 31:57Azure CLI installation and extensions
- 36:08Cloud Shell tips
- 46:15Q&A
related talks
53m8 Ways to Screw Your Azure Automation
51mImprove PowerShell scripting with Azure integration
03h 03mline tools work better for you
01h 29mThe Many Ways (To Run PowerShell in Azure)
31mAzure DevOps for System Engineers
43mUsing PowerShell From a Browser to Manage Cloud Resources
48mPowerShell in Azure Functions
44mSecrets at Scale: Managing Cloud Credentials with PowerShell Automation