Inventory Your Server Environment and Detect Change at Scale
summary
Azure Automation Change Tracking and Inventory claims to record software services daemons files and registry entries across Windows and Linux using PowerShell Desired State Configuration and a get-inventory DSC resource, compare snapshots on the backend, and surface drift in the portal and VM blade. File contents upload to a customer storage account via write SAS only after MD5 detects change. Collection latency drops toward 10 seconds collection for services. There’s a weekly HTML report script on the PowerShell Gallery that emails parsed Log Analytics results. Pricing: included for Azure nodes, $6/node on‑prem after five.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:17Automation Configuration
- 2:27Configuration Management
- 5:25Change Tracking
- 6:09Configure My Settings
- 17:48What's Coming Next
- 18:20Azure Security Center
- 20:37What Is this Going To Cost Me
- 27:46Overview of How Inventory and Change Tracking Are Communicating for on-Premise Notes
- 30:51Tracking the Content Changes
related talks
50mMicrosoft Azure Policy Guest Configuration
48mMonitoring and Managing the Hybrid Infrastructure with Azure Monitor and Azure Automation.
46mAn IT Operations Approach to Observability
31mAzure DevOps for System Engineers
49mMonitoring Using PowerShell
47mAutomating Active Directory Health Checks
53mAzure Cost Management
46mLeverage from Pester to automate Azure Storage Account testing