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.
ISSUE - Windows App (Android) - Input latency and frozen screens with RemoteApps and handhelds
Good morning, ladies and gentlemen, TL;DR: Current Windows App for Android changed something in the background, causing massive latency issues while input. an announcement from end-user point of view. We are having performance and latency issues for almost eight weeks now with the current Windows App (Android). The issues are showing massive performance latency while giving input to a RemoteApp-connected Windows Terminal Server (WS2022DC). For troubleshooting measurements, we went through EVERYTHING... Changed GPOs for connecting only via TCP instead of UDP, cleared user profiles, even provisioned new VMs with new update states, went back to March updates. I never thought, I had to change App version (make this in an enterprise with about 100 handhelds, specifically assigned for warehouse and delivery management) to last January to solve those issues... We definitely need more transparent patch notes (really Microsoft? 2026 and you push updates without any release notes published, not even known issues?!) and a way to downgrade versions without re-provisioning the whole RDP client for Android... I am looking forward to hearing from other parts of the world, using RemoteApps with Android handheld scanner and RDS2022. Best regards, xSOU1 | Jules
Change AVD Insights Workbooks to use VM Insights Queries
Currently the AVD Insights workbooks rely on the Microsoft Monitoring Agent which is being retired. Please release an AVD Insights solution that works with and utilises the VM Insights capabilities of Azure Monitor. This will allow us to decommission the use of the MMA.
Microsoft AVD Client Support for Teams camera backgrounds
We are using Dell thin clients running Dell ThinOS. When connected to AVD from those devices using the Microsoft AVD app, camera backgrounds are not available in Teams calls. Please add this feature to future releases of the Microsoft AVD app for Dell ThinOS.
Problems connecting with the Virtual Desktop
After using this for a month at this point, it suddenly stopped working on itself. It has an error message stating that it needs to "initialize to an empty state" after "a part of the process has locked a portion of the file." There is no way I am aware of that can get an elaboration of what the problem is. I've tried logging in to my virtual desktop on a separate device, but it does not work. Any help or advice would be appreciated since there is no other method (that I'm aware of) that can allow me to contact support.
Remote Desktop for Mac 10.9.4 often causes spinning wheel of death when copying from Windows machine
Starting in the last version or two, I frequently get the "spinning wheel of death" after using Remote Desktop for Mac to copy from the remote Windows client. This manifests when I switch back to the mac and try to switch to Slack -- Slack will be frozen for 30 seconds to several minutes with the colorful spinning pinwheel. Many people have been experiencing this issue, both recently and in the last several years: https://techcommunity.microsoft.com/t5/azure-virtual-desktop-feedback/copy-and-paste-from-microsoft-remote-desktop-to-mac-causes/idi-p/3947326 https://techcommunity.microsoft.com/t5/azure-virtual-desktop-feedback/microsoft-remote-desktop-for-mac-copy-and-paste-works-a-while/idi-p/3930905 https://learn.microsoft.com/en-us/answers/questions/565240/microsoft-remote-desktop-freezes-constantly-apple Please look into this, it's a productivity killer. And if there's anything I can grab for you that will help (like a snapshot of a process using the Mac activity monitor) please let me know. EDIT: I just attached a sample and spindump of Slack (the macOS process that gets the spinning wheel of death after copying text on the remote windows machine).Windows App hangs when images are copied to local machine's clipboard
I am using MacOS Sonoma 14.7 and Windows App Version 11.0.0 (2372) on Mac. Final Update - Problem seems to be resolved: I realized that this problem was also happening when using the Windows App on Windows, and it was only happening while I was connected to one of my devboxes. Apparently, that devbox machine had "ditto" installed. Ditto is a clipboard manager which can keep a history of items on the clipboard. Apparently, when I uninstalled ditto, the problem just disappeared. I did not test it, but ditto app might be causing this problem even on every remote desktop connection. Anyways, I leave the original problem I was experiencing here, just to let other users know about it: Original Problem Description: When clipboard mode is set as Bidirectional or Local to Remote only, if I use the Mac Screenshot tool to copy some portion of my desktop, and then paste into some app running on my mac (e.g., One Note), remote desktop connection freezes, and I often have to close and reopen the connection. Sometimes, it unfreezes after some 15-20 seconds. This problem does not happen when the clipboard sharing is Remote to Local only. It does not matter if the region of the screen I copy is from my remote desktop, or from another monitor's Mac desktop. It looks like the screenshot image is trying to be synced back to the remote desktop connection, and that causes windows app to be stuck. Update: The problem also happens if I open an image on my mac on the preview app, and then copy the image to the clipboard, which causes a similar hang up. This is an image of size 1.6 MB only. It does not end there, when the last item on my Mac clipboard is an image, the freezing even happens if I restart the connection. It looks like windows app is freezing while trying to transfer the clipboard contents from the local machine to the remote machine. It would be better if this operation could be done in background without harming the user's experience.New Service Improvement Idea: AVD Performance Insight Dashboard
Overview: Enhance the Azure Virtual Desktop (AVD) experience by introducing a dedicated dashboard that displays real-time CPU and memory usage for each AVD session along with the top 10 processes consuming CPU. This dashboard will empower IT administrators to quickly diagnose performance issues and optimize resource allocation. Key Features: Real-Time Monitoring: Display live CPU and memory metrics per AVD session. Auto-refresh capability to capture real-time performance changes. Process Analysis: Show a list of the top 10 processes consuming CPU per session. Provide detailed process metrics including CPU percentage, memory footprint, and process IDs. Historical Data & Trend Analysis: Archive performance data to visualize trends over time. Enable administrators to identify recurring patterns or spikes in resource usage. Alerting & Notifications: Set custom thresholds for CPU and memory usage. Generate alerts for sessions or processes that exceed set limits, triggering proactive remediation. Integration with Existing Tools: Seamlessly integrate with Azure Monitor and Log Analytics for deep-dive analysis. Export data to Power BI for advanced visualization and reporting. User-Friendly Interface: Interactive dashboard design with filtering options (e.g., by session, time frame, or specific metrics). Drill-down capability to analyze individual sessions or processes in detail. Benefits: Enhanced Troubleshooting: Quickly pinpoint performance bottlenecks by identifying resource-intensive sessions and processes. Proactive Maintenance: Early detection of abnormal resource usage allows for timely intervention before issues escalate. Optimized Resource Management: Understand usage patterns to make informed decisions on scaling, workload balancing, and capacity planning. Improved User Experience: Reduce downtime and performance issues, leading to smoother end-user operations in the virtual desktop environment. Implementation Considerations: Data Collection: Leverage AVD session performance counters and existing telemetry from Azure Monitor. Dashboard Development: Use modern visualization tools (e.g., Power BI or Azure Dashboard) for an intuitive user interface. Security & Compliance: Ensure data privacy and compliance with government/federal cloud standards where applicable.
CCD Locations Syntax
I would recommend changing the information regarding the syntax in the documentation for "CCDLocations" when file shares/SMB is in use from "type=smb,name="WINDOWS SMB PROVIDER",connectionString=\\<server-name>\<share-name>" to "type=smb,connectionString=\\<server-name>\<share-name>." I have had no success using the "WINDOWS SMB PRVIDER" in the syntax for CCDLocations.
