How to review idle AVD session hosts

Define what you mean by idle

Choose an observation interval that includes the workload's expected use. A desktop used for a monthly closing process needs a different review window from a daily support desktop. Write whether the concern is absence of observed successful connections, low machine utilization or allocated hours outside an agreed schedule.

Each signal has a different limit. Low CPU can coexist with a connected user reading documents. A recent successful connection proves that a connection occurred at that time; it cannot establish continuous use afterward. A disconnected session may still contain applications or unsaved work. Confirm current session state separately before considering any interruption.

Check the connection evidence coverage

Microsoft requires diagnostics to be enabled for each AVD resource being monitored. Data becomes available for subsequent activities, and connections that never reach AVD do not appear in diagnostic results. Confirm that the Connections category reaches the intended Log Analytics workspace and that the reviewer can query the required scope.

Record query start and end dates, collection time and readable retention settings. Distinguish a successful empty query from a permission failure or missing table. Even a successful query does not by itself prove continuous historical coverage. Preserve older successful observations when newer queries are empty; a shorter retained window must not erase known past use.

Ask why the host remains available

Find the desktop owner and ask about current tasks, leave periods and recovery duties. For pooled hosts, ask the host pool owner about capacity headroom and session consolidation. A spare host may be deliberate. A personal assignment may belong to a contractor whose need is documented outside the employee directory.

Record customer testimony as business context with its date and source. Keep it separate from provider connection observations. A statement that a desktop is no longer needed supports a continued-need review; it does not establish past inactivity or authorize deleting storage. Resolve dependencies and the approval route before choosing a change.

Compare illustrative review candidates

These invented USD monthly compute charges prioritize a review queue. They are not recoverable savings. Host A has an older successful connection but only partial recent coverage, so its activity remains uncertain. Host B has recent use and disconnected sessions. Host C has customer-confirmed recovery duties despite no returned connections.

The combined compute charge is USD 720. No amount is assigned as a saving because the evidence does not yet establish an approved removable cost. If one host is later approved for a bounded power schedule, estimate only the affected instance hours and account separately for disks and other resources that remain billed.

Scroll the table sideways on smaller screens. Keyboard: focus the table and use the arrow keys.

Bound a proposed power change

Azure distinguishes Stopped (Allocated) from Deallocated. Stopped allocated VMs incur instance charges; deallocated VMs release their hardware allocation. Managed disks and some networking resources can continue to incur charges. Confirm the intended final state and the remaining resource bill when writing the change request.

The customer administrator should specify the host, permitted time window and restart path. Check whether users must be warned or signed out and how out-of-hours access works. Keep deletion of profiles or disks out of a power-only request. For pooled capacity changes, review the scaling plan and session thresholds with the pool owner.

Retain a review record and check the outcome

Keep the original evidence window, source timestamps and known gaps with the decision. If the reviewer retains the host, record its purpose and a future review date that matches the workload. If the customer changes its schedule, collect subsequent power and connection observations to check whether the intended behavior occurred.

Compare same-currency charges over meaningful periods and explain other changes, including workload demand or rates. A lower total alone does not attribute a saving to the host change. Costframe's Azure client exposes a read-only audit surface. Its AVD evidence rules preserve uncertainty when history is missing; customers make power, assignment and removal decisions in their own environment.

Related guidance