How to measure AVD cost per user

Choose the question the metric answers

Finance may ask what it costs to keep a desktop available to an eligible employee. Operations may ask what the service costs per person who connected during the month. Those questions need different denominators. Write whether your numerator includes licensing, profile storage and shared infrastructure before calculating either figure.

A cost per concurrent session is a capacity planning measure. It cannot replace a count of distinct people served. One person can reconnect many times or use several applications. Repeated connection events must not inflate the population. State the business question in the report title so that the result does not acquire a different meaning when circulated.

Define and date the user population

For a provisioned population, identify the eligibility or assignment source and how joiners and leavers enter the month. A month-end directory snapshot cannot establish who had access for every earlier day. Decide whether finance needs month-end headcount, distinct eligible people during the month or an explicitly defined average population.

For an observed population, count distinct identities with successful connection evidence inside the selected interval. Record the queried scope and evidence coverage. Microsoft states that diagnostics become available after they are enabled; connections that never reach the AVD service are absent from those results. Missing history leaves activity unknown. Avoid labeling everyone without a returned event as inactive.

Separate personal responsibility from pooled service use

A personal desktop assignment can support a resource-to-person relationship at the observed time. A pooled host serves several people, and its current session or login records do not establish exclusive financial ownership. Profile storage and shared gateways need their own allocation treatment, even when a user has a personal desktop.

Costframe's AVD normalization treats assignedUser as assignment evidence for personal host pools. It does not elevate that field on a pooled host into personal entitlement. Linked managed disk mapping requires an unambiguous provider relationship, with a limitation when earlier attachment history is missing. Keep unresolved costs visible until the required evidence or an approved allocation rule exists.

Two averages from one illustrative cost scope

Assume USD 6,000 in scoped monthly service charges, 120 provisioned people and 80 distinct people with observed successful connections. Coverage for this fictional example is sufficient for its stated observation interval. The average is USD 50 per provisioned person or USD 75 per observed connected person. No cost has changed between those calculations.

The USD 1,000 unresolved amount remains in the service average because it is confirmed service cost. It cannot yet be assigned to individuals. Excluding it would reduce the displayed numerator and conceal an attribution gap. The USD 2,000 pooled and shared amount also needs an explicit policy before any personal chargeback.

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

Agree the shared-cost rule with finance

The FinOps Foundation describes fixed, proportional and proxy-based methods for shared costs, alongside centrally funded shared services. Choose a rule that people can explain and reproduce. Equal allocation can fit a service that offers the same entitlement to every eligible person; a usage proxy needs reliable evidence and a reason to reflect responsibility.

Record the rule version and effective period. Preserve the original resource charges alongside allocated amounts, and check that every split returns to the source total in the same currency. Unknown identities and people without a cost center remain explicit categories. A current department label should not silently rewrite responsibility for an earlier month.

Explain movements before judging users

A rise in cost per observed person can follow a holiday month with fewer connections even when the bill is unchanged. Growth in the provisioned population can lower an average while the total service bill rises. Present the numerator and denominator next to the unit cost, with the same exclusions each month.

Connection evidence describes service access. It does not measure employee productivity or establish why a person needed a desktop. Ask the service owner about seasonal roles and recovery requirements before recommending an assignment change. Costframe reviews Azure through read-only access; customer administrators remain responsible for all cloud changes and financial allocation decisions.

Related guidance