Managing a Hybrid Infrastructure with PowerShell
summary
Uses the Azure Arc agent plus PowerShell remoting and the Azure REST API to run commands across clouds and on‑prem, distinguishes set-azvm run command (creates saved object) from invoke run, hits an output limit of 40096 characters and Arc overwrites previous output so scripts convert results to JSON and write to a blob SAS token (or use managed identity) to persist full output, ships a reusable wrapper (like invoke-az-remote-command) and validates the approach on a 14,000‑server Log4j scan that proved faster than ad hoc pushes.
AI-written summary · about
chapters (16)
- 0:00Hybrid infrastructure management
- 3:32Azure Arc benefits
- 5:38Demo: Run commands on Azure VMs
- 7:46Run commands on Arc servers
- 11:18Capture output with blob storage
- 15:16Handling output limits in Arc
- 18:45Automate command execution
- 22:18Demo: Cross-platform execution
- 25:50Unified remote command function
- 27:16Log4j vulnerability scan
- 29:02Centralized monitoring with Arc
- 31:16Windows Admin Center + Arc
- 32:58Azure Update Management
- 34:32Managed identities auth
- 37:01API & CLI automation
- 39:29Q&A
related talks
51mImprove PowerShell scripting with Azure integration
53mAzure Hybrid - Learn about Hybrid Cloud Management with Azure
45mOrchestrating Tasks across Hybrid Environments using ...
47mUnleashing the Potential of Hybrid Cloud
01h 29mThe Many Ways (To Run PowerShell in Azure)
48mMonitoring and Managing the Hybrid Infrastructure with Azure Monitor and Azure Automation.
47mIt’s PowerShell In the Cloud – Welcome to Azure Cloud Shell
43mUsing PowerShell From a Browser to Manage Cloud Resources