[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.
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.
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.
Windows 11 MultiSession 23h2 User Photo Bug
If a user changes their icon in the start menu, the profile picture is changed to the same for all users who are logged in to the same Windows 11 multi session + FSLogix session host. Fortunately, this doesn't happen in Teams / Outlook! This is a bug with MultiSession + Fslogix. Does anyone have any news on whether MS will fix the bug? Other guys have the same issue https://techcommunity.microsoft.com/idea/azurevirtualdesktop/bug-with-profile-picture-on-avd--windows-11-multi-user/4180592
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.Something is preventing you from using Windows App right now.
After being auto-updated from Windows App version 2.0.327.0 to version 2.0.328.0, some of our users can't launch their Windows App anymore and get an error message says: "Something is preventing you from using Windows App right now." Since there is no way to control the update process, we could only let our desk users use MSRDC instead, as a temporary solution. For the frontline users, I could only pray that this problem will not take place until weekend. If any Microsoft person sees this post, please let the Windows App team know about this and fix this problem ASAP.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.
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.Frequent AVD Deployment Failures
Since June 2024, we have experienced occasional failures in AVD deployments. While most deployments succeed through adding session hosts to the host pool, there are instances where the deployment fails. Given this situation, we would like to request a change in behavior to reduce the burden of recreating AVDs when deployment fails.
