Support Live Session Migration for Windows 11 Enterprise Multi-Session AVD Hosts
Description Azure Virtual Desktop administrators regularly encounter maintenance scenarios where a Windows 11 Enterprise Multi-Session session host must be removed from service to apply urgent patches, investigate platform issues, replace a host, or perform emergency maintenance. The current approach requires placing the session host into drain mode and waiting for active user sessions to disconnect or forcing user logoff, which can disrupt productivity and user experience. It would be valuable if Azure Virtual Desktop supported live migration of active user sessions between Windows 11 Enterprise Multi-Session hosts within the same host pool, similar to the way virtual machine live migration minimises downtime during infrastructure maintenance. This capability would allow administrators to move active sessions from one session host to another without requiring user disconnection or application interruption. This feature would provide significant operational benefits, including: Reduced user disruption during planned and emergency maintenance. Faster remediation of unhealthy or degraded session hosts. Improved patching and update operations. Reduced dependency on large maintenance windows. Improved service availability for business-critical AVD environments. Better support for future hot patching and rolling maintenance scenarios. While Windows 11 Enterprise Multi-Session differs significantly from Windows Server and traditional VM live migration technologies, the ability to seamlessly relocate active user sessions between healthy hosts in a host pool would be a major enhancement for enterprise Azure Virtual Desktop deployments operating at scale.
Azure Virtual Desktop (AVD) drag and drop files
In some situations, it is handy to drag and drop files from a local endpoint to for example AVD remote app. For example when using Outlook on the local endpoint and wanting to archive attachments in the ERP application (legacy app) hosted in a remote app. Copy and paste works but is not user-friendly in this situation.
AVD Forced log off by user
My suggestion for a feature request is to add a logoff/force-logoff option in both the web client and AVD client at a minimum. Right now, if a user logs into a host and they hit a black screen or any other type of error they are stuck to that host until the session is force logged off by an admin or they hit the logoff timeout that an admin sets. This would save frustration and productivity loss for a user that would have to wait for an admin to help. This is especially needed for companies that support around the clock teams.
[Enterprise Customer Feedback] - AVD Forced Log Off
After going over the issue with support, we couldn't find a solution that an end user can self-service themselves to rectify when an AVD session host is having a performance issue. The host session VM booted up per our scaling policy at 7:45 a.m. and immediately had a User Profile service error. When the first attempted session connection occurred about 15 minutes later, it failed to load the session and only left the user with a black screen. Disconnecting and relaunching the session still placed them in the session hung session. We employ a disconnected session log-off policy of 120 total minutes. It would take at least 2 hours without user interaction for a session to fully terminate. There is no way a user can force log off their session in either the web client or Azure Virtual Desktop client. The only option available is to disconnect but it maintains the session live in the backend. My suggestion for a feature request is to add a logoff/force-logoff option in both the web client and AVD client at a minimum. And, an option for the end user to avoid a new session connection to the host that was having the issue. This might limit productivity time loss as IT works on rectifying the issue. (most likely a reboot of the session host machine).
Add Capacity Reservation Group Support to Azure Virtual Desktop VM Creation Wizard
I would like to request support for assigning Azure Capacity Reservation Groups during Azure Virtual Desktop (AVD) session host creation. I recently deployed a GPU-enabled AVD environment for AI and machine learning workloads where GPU resources are extremely scarce and often unavailable for on-demand provisioning. To guarantee capacity, we were required to create a Capacity Reservation Group prior to deployment. Currently, there is a significant workflow gap between standard Azure VM creation and AVD session host deployment. Standard Azure VM deployment allows a VM to be assigned to a Capacity Reservation Group during creation. The Azure Virtual Desktop host pool creation wizard does not expose this option. Administrators are forced to either create the VM outside of the AVD workflow using the Capacity Reservation interface and manually register it to the host pool afterward, or deploy through the AVD wizard and associate the VM with a Capacity Reservation Group later. This creates several challenges. Additional Quota Requirements Capacity Reservations consume quota before a VM is deployed. Because the AVD wizard cannot deploy directly into a reservation, administrators may need additional quota approvals to support both the reservation and deployment workflow. In environments where quota increases require support requests, this can introduce delays of several days. Resource Scarcity and Timing Issues GPU-enabled SKUs frequently have limited regional availability. Administrators must wait for both quota availability and capacity availability multiple times throughout the deployment process. This significantly increases deployment complexity and delays project delivery. Inconsistent Management Experience Creating the VM through the Capacity Reservation workflow bypasses several AVD deployment conveniences, such as Microsoft Intune enrollment and other AVD-specific configuration settings available through the host pool deployment wizard. Administrators are forced to perform additional manual configuration after deployment. Operational Overhead Manual host registration, Entra ID joining, Intune enrollment, and post-deployment configuration introduce unnecessary complexity and increase the likelihood of deployment errors. Suggested Enhancement Add a Capacity Reservation Group selection option directly within the Azure Virtual Desktop session host deployment workflow, similar to the standard Azure VM deployment experience. This would allow administrators to: Deploy AVD session hosts directly into reserved capacity. Utilize existing AVD provisioning features, including Intune enrollment and Entra ID integration. Reduce quota management complexity. Minimize deployment delays for high-demand GPU workloads. Provide a more consistent and streamlined Azure deployment experience. This issue became particularly impactful when deploying NV-series GPU session hosts, where both regional capacity and quota approvals were constrained and deployment timelines were significantly extended. As AI, machine learning, and GPU-intensive workloads continue to grow, this capability would significantly improve the deployment experience for organizations leveraging Azure Virtual Desktop for these use cases.[MMR Call Redirection] ISV submission form broken — requesting allowlisting channel
The ISV submission form referenced on this page is currently unavailable. Here ishttps://forms.microsoft.com/r/BtDs4pdYzB We represent an ISV (Ringover — app.ringover.com) with a completed PoC validating MMR Call Redirection on AVD and Windows 365. Full submission pack is ready. Please advise on the correct submission channel or restore The form. Contact: hicham.kadiri [at] ringover.com Thanks in advance for your feedback. Regards, Hicham.Broken ISV Submission form for MMR — 404 on forms.microsoft.com/r/BtDs4pdYzB
Hi AVD team, I'd like to report a broken link that is currently blocking ISV submissions for Multimedia Redirection (MMR) call redirection on Azure Virtual Desktop and Windows 365. The issue On the official Learn page: https://learn.microsoft.com/en-us/azure/virtual-desktop/multimedia-redirection-developer-integration …the section "Submit your website for review or request assistance" points ISVs to this form to request inclusion in the Websites for call redirection allowlist: https://forms.microsoft.com/r/BtDs4pdYzB This form returns a 404 / no longer available error. As far as I can tell from the public documentation, this is the only documented channel for ISVs to submit their WebRTC-based calling app for review, so the broken link effectively blocks any new submission today. Context I'm working with a WebRTC-based business telephony ISV who has completed a successful MMR integration PoC on both AVD and Windows 365. Call redirection is working end-to-end, and one of their enterprise customers has independently validated the integration on their own tenant. The submission package is ready — we just have nowhere to send it. Ask Could the AVD / MMR team please: Update the link on the Learn page with a working submission URL, or Provide an alternative submission channel (email alias, replacement Forms URL, or the right internal contact) that ISVs can use in the meantime? Thanks in advance — happy to provide additional technical details about the integration off-thread if that helps route the request.
