I recently analyzed an intermittent Azure Virtual Desktop (AVD) sign-in issue where a user encountered the message:
“Your session ended because the remote PC was low on memory.”
At first glance, the configuration appeared correct:
-
Session hosts provisioned with 64 GB RAM
-
Policies configured to log off disconnected sessions
-
FSLogix profile cleanup already in place
After reviewing AVD Insights and monitoring host performance metrics, the underlying issue became clear.
Session Density vs. Actual Workload
Even appropriately sized virtual machines can experience memory pressure when:
-
Session limits are configured too aggressively
-
Users run multiple applications simultaneously, such as Outlook, Teams, browsers, and Excel
-
Several users log in during peak usage periods
Key Takeaway
AVD reliability is not determined by VM size alone. It requires realistic session density planning, awareness of memory spikes during user logins, and a balanced approach between cost optimization and user experience.
If you are running Azure Virtual Desktop in a production environment, this is worth reviewing before performance issues begin affecting end users.
#AzureVirtualDesktop #AVD #CloudEngineering #Azure #FSLogix #VDI #RealWorldIT

No comments:
Post a Comment