On the 30th of April the Spring Update Release of Windows Virtual Desktop (WVD) entered Public Preview. This means anyone can go to the Azure Portal and deploy an WVD Workspace and test the new ...
I´m very excited with all these new features. I´m already working on a PoC so I can get familiar with the new administration/provisioning model, I´ll give it a shot and will try to migrate existing hosts to this new model, however I've found a stopper and I'm honestly not sure if this is something that is just temporarily in place until this new release is officially supported.
Here´s the issue:
If a User uses the "Remote Desktop" client to subscribe, he´s only able to see everything that was associated with his old Non-ARM model stuff (Desktop Apps/RemoteApp, etc).
However, I created a new Workspace, Hostpool, DesktopApps and RemoteApps with new ARM process, the user is now forced to re-subscribe in order to be able to see any available WORKSPACE associated with all new features provisioned with the ARM WVD model. This is not acceptable for my environment, as I´m already using Multi Factor authentication and other features, forcing the user to go through authentication/multifactor twice is a stopper for me at the moment.
I suspect that subscription process for the user would work smoothly and directly to the new Workspace ARM environment (with only 1 authentication prompt), if I didn't happen to had any preexisting Non-ARM resources assigned to the User. Have any of you tested this?