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.[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.Allow swapping Alt+PageUp / Alt+PageDown direction in Windows App (AVD)
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Product: Windows App (Azure Virtual Desktop client) Description: When using Azure Virtual Desktop through the Windows App (especially in windowed mode), Alt+PageUp and Alt+PageDown are the only supported shortcuts for switching between remote applications. The direction of these shortcuts is opposite of intuitive and inconsistent with common task‑switching expectations (Alt+Tab, browser tab switching, virtual desktop navigation, etc.). There is currently no way to: remap these shortcuts reverse the navigation direction customize keyboard behavior per user This significantly impacts usability for power users who spend all day inside AVD sessions. Requested enhancement: Add a configurable keyboard mapping option in the Windows App to: swap Alt+PageUp / Alt+PageDown direction or allow user‑defined key mappings for remote app switching Why this matters: Reduces cognitive friction and user error Improves accessibility and ergonomics Brings Windows App closer to parity with legacy mstsc.exe and competing VDI clients (e.g., Citrix) Workarounds today: Users must rely on third‑party tools (AutoHotkey) to fix this locally, which should not be required for a basic UX issue.
Enable Single Sign-On for Windows App under Proxy Environment with Entra Connect Users
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } We are using Azure Virtual Desktop and, due to our security policy, we run Windows App under a proxy environment. Currently, when signing in to Windows App in this environment, Single Sign-On (SSO) does not work for users connected via Entra Connect. Could you please update the specifications so that these users can sign in with SSO when using Windows App under a proxy? For reference, in the Remote Desktop Client app, SSO works correctly after pressing the Register button. We would like to see similar functionality in Windows App.
Add Search to Remote Desktop client for Windows
As an Azure Administrator responsible for managing extensive cloud infrastructure, I rely heavily on this client to access multiple Azure Virtual Desktop (AVD) environments. My current responsibilities involve managing a large and growing pool of AVDs, each providing access to a specific environment (e.g., development, staging, production, or customer-specific resources). Currently, I have no easy or efficient way to look up the relevant AVD within the client interface. The lack of a search bar forces me to manually scroll through long lists of connection icons and names whenever I need to switch contexts. This process is time-consuming, prone to error, and significantly hinders my productivity, especially during time-sensitive administrative tasks or troubleshooting efforts. Implementing a simple, functional search bar would drastically improve the user experience for administrators like myself by providing immediate access to the required virtual desktop connection.
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.Support for start menu integration for RemoteApps
Customers of us want to have the ability to start appps directly via start menu, as it was possible with Citrix: https://support.citrix.com/external/article?articleUrl=CTX215624-published-app-shotcuts-on-start-menu-configuration It allows seamless access to remote apps We believe it is a great feature missing on AVD/Windows365 which would improve user adoption and experience by making access to remote apps fast, seamless and highly user-friendly.Windows App - Account Picker During Startup
Windows App is showing additional improvements to the overall VDI experience. As an Architect working for a consulting company, I have multiple clients with AVD environments I have to log into. One of the major benefits of Remote Desktop is that when opening, the window provides visibility to all signed in accounts. With Windows App, when opening the application, I'm in the most recent account. To benefit us that work in multiple environments, allow us the capability to choose which account I want to work in when opening the application. If Windows App only has one account associated, it can default to that account. But if there are two accounts present, allow the user to choose which one they want to go into at the onset.
Support URI schemes like ms-avd:connect across all platforms in Windows App
https://learn.microsoft.com/en-us/azure/virtual-desktop/uri-scheme We would like to request the implementation of support for URI schemes, such as ms-avd:connect, in the latest Windows App. Currently, this feature is available only in MSRDC. We are developing a web app portal running in the browser that allows users to connect to their Azure Virtual Desktop instances. Having this feature in the Windows App across all platforms (including Windows, macOS, Android, and iOS) would significantly benefit our development and provide a seamless experience for our users.Host Pools session hosts list
Large number of session hosts (1700+) is difficult to handle. Following suggestions would help: Allow to customize the the filters on the different columns Filter on Power State Filter on Health State Filter on user (with wild cards) Allow to export in CSV with filters applied Today, the CSV export exports all the VMs whatever the filter It is a workaround of the lack of filters on different fields Thanks for reading
