A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
Hello Musab,
Thank you for reaching out. I understand the concern regarding users being unable to fully sign out from Azure Virtual Desktop (AVD) and sessions remaining active even though sufficient resources are available.
In Azure Virtual Desktop, when a user closes the Remote Desktop window without explicitly selecting Sign out, the session does not end. Instead, it moves into a Disconnected state. In this state:
- Applications continue running in the background
- The session still consumes host pool capacity
- New users may be blocked from signing in, even though hosts appear available.
To prevent sessions from remaining stuck in a disconnected state, Microsoft recommends automatically ending disconnected or idle sessions using one of the following supported options:
Configure Session Time Limits
Set a time limit so disconnected sessions are automatically signed out after a defined period.
- Configure “Set time limit for disconnected sessions”
- This can be applied using:
- Group Policy (AD‑joined hosts)
- Microsoft Intune (Entra ID‑joined hosts)
Use Autoscale with Force Logoff(For Pooled Host Pools)
If you are using Autoscale, enable Force logoff during ramp‑down. This ensures users are signed out cleanly when hosts are being scaled down.
https://learn.microsoft.com/en-us/azure/virtual-desktop/autoscale-scenarios
**Manually Sign Out Stuck Sessions
**As a short‑term mitigation, administrators can manually sign out disconnected sessions using:
- Azure Portal
- Azure PowerShell (
Remove-AzWvdUserSession)
https://learn.microsoft.com/en-us/azure/virtual-desktop/terminology
Could you please help answering this questions
How are you attempting to sign out users?
- Azure Portal (Host pool > Sessions > Sign off)
- PowerShell/CLI (
Stop-AzWvdUserSession, etc.) - Azure SDK or REST API
- Are you seeing any error messages or error codes when you try? If yes, what do they say?
- Which session state are you targeting?
- Active sessions
- Disconnected or hung sessions
- Is this happening across all session hosts in the host pool or only on specific VMs?
- Are you using a pooled host pool or personal desktops?
- What client are your users connecting with?
- Windows (Remote Desktop)
- macOS, Web client, or another platform
- Have you checked the host pool’s diagnostics logs or the session host event logs for related errors?
- Are there any custom RDP properties, Conditional Access policies, or sign-in frequency settings applied that might block sign-out operations?
Please note that session behavior can vary depending on host pool type, identity configuration, and session management settings. If the issue persists after applying the recommended configuration, we’ll be happy to assist further.
Feel free to add a comment in the Comments section, and we’ll get back to you promptly.
Thanks,
Manish.