What's changed: Created AZ-140 Chapter 5, completing the textbook (Domain 4: monitoring (Azure Monitor + Log Analytics, AVD Insights workbooks, capacity/performance optimization, autoscaling scaling plans, active-session monitoring); updates/backup/DR (drain + recreate from a new image version, Azure Update Manager, Azure Backup point-in-time restore of FSLogix profiles/personal desktops/images, multi-region DR, pooled stateless)).
5.1Monitoring and autoscaling
Understand AVD log collection/analysis, Azure Monitor, customizing AVD Insights workbooks, optimizing capacity/performance, host pool autoscaling, and monitoring active sessions and application groups.
In operations, you surface environment health and scale capacity with demand to balance cost and experience. Visibility and automation are the pillars.
5.1.1Azure Monitor and AVD Insights
Aggregate session-host and service logs/metrics into a Log Analytics workspace and analyze/alert with Azure Monitor. AVD Insights (a workbook on Azure Monitor) visualizes connection performance, host utilization, and user connection failures via workbooks you can customize. Think "AVD-specific operations dashboard for connections/utilization" = AVD Insights; "general metrics/log analytics/alerting platform" = Azure Monitor. Use them to identify and optimize capacity/performance bottlenecks (CPU/memory/profile storage/logon time).
5.1.2Autoscaling
Autoscaling uses a scaling plan to automatically start/stop session hosts by time of day (ramp-up/peak/ramp-down/off-peak) or load, optimizing capacity and cost (stopping reduces billing). This differs from Start VM on Connect ("power on one host only when a user connects"); autoscaling handles fleet-wide scaling based on demand. Operate it with load balancing (breadth/depth) on pooled host pools.
Cues: "AVD-specific dashboard for connections/utilization" = AVD Insights (workbooks). "general logs/metrics/alerts" = Azure Monitor + Log Analytics. "scale the fleet by time/load" = autoscaling (scaling plan). "power on one host at connect" = Start VM on Connect.
Watch the mix-ups: (1) Autoscaling (demand-based fleet scaling) vs Start VM on Connect (single power-on at connect). (2) AVD Insights is a workbook on Azure Monitor and requires sending data to Log Analytics. (3) Capacity optimization is metrics-driven—do not add hosts on a hunch.
5.1.3Section summary
- Azure Monitor + Log Analytics for logs/metrics/alerts; AVD Insights workbooks for AVD-specific visibility
- Autoscaling = scaling plan auto-starts/stops the fleet by time/load (cost optimization)
- Autoscaling (demand-based fleet) and Start VM on Connect (single power-on at connect) are distinct
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to visualize AVD connection performance, host utilization, and connection failures in an AVD-specific dashboard. Which is best?
Q2. You want to auto start/stop the session-host fleet by time of day/load to optimize cost. Which is best?
Q3. Which platform aggregates session-host logs/metrics for general analysis and alerting?
Q4. Which correctly distinguishes autoscaling from Start VM on Connect?
Q5. What is the correct approach to identify and optimize session-host capacity/performance bottlenecks?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.