Session Replay
Replay what happened in any AVD session, event by event, next to the host's metrics.
Session Replay rebuilds an Azure Virtual Desktop session as a timeline. Scrub through its connects, disconnects, reconnects and sign-out, and see CPU, memory, disk queue and round-trip time on the same clock, with thresholds marked. Open any event to see what happened around it and the recommended actions for that kind of event. Session Replay records events and metrics, not the screen, and keeps them for 30 days by default.
The problem Session Replay solves
"It was really slow this morning" is the hardest ticket in virtual desktops. By the time anyone looks, the session has ended, the host has recovered, and Azure's session list only shows who is connected now. Rebuilding what happened means stitching together connection logs, performance counters and guesses about the timing.
Help desks need to see the session as it happened: when the user connected and dropped, and what the host was doing at that moment.
Key capabilities
How Session Replay works
- 1Atlas records connects, disconnects, reconnects and sign-outs as they happen
- 2Host metrics come from the Atlas agent or your Log Analytics workspace
- 3Open Session Replays and pick a session
- 4Scrub the timeline and line up events with the metrics to see what the user went through
Finding the session
The Session Replay page lists past and current sessions with their user, host pool, session host, client, start and end times, duration, status, score and issue count. Search by user, VM or session ID, filter by status (Active, Disconnected, Completed or Error), host pool, region and time range, and turn on Issues only to see just the sessions where something went wrong. Tiles above the list count total, active and completed sessions and those with issues. Click a row to preview it, then open the full replay.
What the replay shows
The replay opens with the session's user, host, pool, times and score, above a timeline with a scrubber. On a live tenant the timeline marks the session's connect, each mid-session disconnect and reconnect, and the sign-out. Atlas detects them with its two-minute session poll, so a disconnect is placed within a couple of minutes of when it happened, and the connect is pinned to the session's real start. Zoom to 1, 5 or 15 minutes or the whole session, and click a marker to open that event with the events from the two minutes around it and the recommended actions for that kind of event. The raw event data is there too.
Below the timeline, charts of CPU, available memory, disk queue length and network round-trip time share the same clock, with thresholds marked, so a disconnect can be lined up against a CPU spike or a jump in latency. The counters come from the AVD Insights performance counters in your Log Analytics workspace. They are measured per session host, so every session on a host shares its numbers. Where there is no workspace, Atlas falls back to the Atlas agent's in-guest counters or to Azure Monitor CPU.
Privacy and retention
Session Replay is an event timeline, not a video. It never captures the user's screen or keystrokes; recording a remote session is a separate Atlas Reach feature. Events and metrics are kept for 30 days by default, and each tenant can set its own window from 1 to 365 days.
How to set up Session Replay
- 1Connect a Log Analytics workspace to the tenant with the AVD Insights data collection rule, so host counters are collected.
- 2Give help desk administrators the session_replay.view permission.
- 3Open Session Replay and filter to the user and the morning they reported.
- 4Open the replay, scrub to the disconnect, and compare it with the CPU, memory, disk and latency charts.
Session Replay: frequently asked questions
Does Session Replay record the user's screen?
No. It rebuilds the session from connection events and host performance metrics. It never captures the screen, keystrokes or anything the user typed.
Which events appear on a real tenant's timeline?
The connect, every disconnect and reconnect during the session, and the sign-out. Sign-in phases such as profile load time are not on the replay timeline; use the Logon Breakdown card for those.
Why are the performance charts empty?
The charts need host counters, normally from a Log Analytics workspace with the AVD Insights data collection rule, or from the Atlas agent. A pool with neither has events but no metrics.
How far back can I replay a session?
30 days by default. An administrator can change the tenant's retention to anything from 1 to 365 days.
Who can open Session Replay?
It needs the Atlas AVD plan, an administrator role and the session_replay.view permission. The page is read-only and changes nothing on the session or the host.
Related features
Guides
Available on
Atlas AVD plan and above
Session Replay is included in every Atlas AVD subscription.