The Azure Shared Image Gallery (SIG) has two features not shared by current supported source image mechanisms, replication and versioning. Both are extremely useful for organisations who are updating many images often.

Images need versioning so it's easy to keep track of releases and roll back/forward between releases.

Organisations often have customers located in more than one place. Keeping these disparate locations' images in sync with each other means that companies can stop running tiresome robocopy scripts or manual tasks.

Many Companies are already using the SIG for images. They currently have to move these images out before integration with WVD. A simple change to the ARM template would enable this feature. You can see many examples of this on the web/github as many users, including MSFT field staff, are changing the existing template to accommodate the SIG.

Since Raspberry PI i such a cheap piece of hardware it would be perfect to set up as a thin client. The web client is a good alternative but I would love a solution where the user doesn't have to relate to the underlying OS on their Raspberry in any way, just a shortcut they click and then enter a full desktop from WVD
I know there is an idea for a linux client over at the remote desktop client uservoice, but that is from 2015 and have never been given attention from Microsoft so I guess it's a dead end.

Although a great part of the IT industry moves towards some kind of public/private/hybrid cloud deployment, the greater part of the industry still functions the same like 10-20 years ago, where you have a simple Database->Server->Client application which won't transform itself into a native cloud application anytime soon. These customers still have the urge for a rather simple Microsoft based OS with win32 apps deployment. RDSH was a great solution for the last years (and it still is!), but honsestly what all the RDSH/Citrix admins ever wanted, was a real Multi-User OS which wasn't Server OS based. It would solve so many problem, if we wouldn't have to deploy Client software on a Server OS anymore, but finally Client software for users on a Multi User Client OS. The use cases were endless: We could deploy the latest and greates Windows 10 Enterprise Feature release, combined with Office 365 / OneDrive (Machine based setup) / MS Teams (machine based) / FSLogix / any ERP software; to hundredes of users based off a central Golden Master Image.

Allow for admins to disable the account registration prompt on WVD endpoints or client. You don't prompt on MacOS and Web Clients. Not all Windows users would like to perform account registration of their user account on their personal device. It might be confusing to them. Even if this provide them with a better experience. Please give us an option to remove the prompt.

For education users this is very confusing and annoying. Please add an option for disabling this within Windows Virtual Desktop client or administration portal. "Don't show the 'Use this account everywhere on your device' box".

Perhaps this prompt can be provided on a per user basis using group. For example faculty staff will benefit from this on a campus device. I think that most users just want the benefits from a better implementation of MSAL within the Remote Desktop client. The client can't even pick up the credentials on the machine using the Web Account Manager. It seems like a poor integration with room for improvement.

This setting should overwrite the MDM Scope setting in Intune: https://docs.microsoft.com/en-us/mem/intune/enrollment/windows-enroll#enable-windows-10-automatic-enrollment

With the current situation, we have to take a snapshot and deploy new WVD session host servers whenever there is an application upgrade or you need to manually update all the session host servers or use other tools like SCCM or Invanti etc... but my question is there a way to achieve this without using any other tools because in Citrix we have the machine creation service inbuilt to handle this. So that we can push an application update to all session host servers simply updating the master image.

We have a large customer deployment around 100+ WVD session host servers. in such a scenario what is the best and easiest way to handle the custom image management?

Using Azure DevTest labs as inspiration and the power off scheduler already available to Azure. I believe that a host pool should have a native power on and power off policy with a scheduler that can be mapped to a time zone, with the (optional) ability for desktop user to extend by 2 hours/skip the day of power management.
My story is that I have a pool of dedicated machines that I will be providing to developers. We have an expected hours of operation of 6am to 6pm Mon-Fri but there will be sometimes when someone needs to stay back or work on the weekend. Having
a) the native ability not to have a dedicated machine to power on machines or need to individually set power off policies
b) the ability like Azure DevTest labs for an optional extend/opt out email sent to a user
would be extremely valuable and enhance the product greatly.
Example user ability opt out with Azure DevTest Labs
https://docs.microsoft.com/en-us/azure/lab-services/devtest-lab-auto-shutdown#set-auto-shutdown-policy-for-a-lab