AVD QuickStart - beware of Entra DS
Hi I recently received a notification from several customers whom had been billed for Entra DS - They had deployed AVD from the QuickStart menu. When attempting to deploy AVD - while going through the wizard, they get to a part that requires the VNET be pre-configured. Of course ,if they haven't properly planned AVD, this part of the wizard won't work. So they exit the wizard, then go to the QuickStart, and run through there.. Using this, they get what they wanted - easy deployment of AVD. However in this case, it enables Entra DS. Once added, it starts BILLING for Entra DS. The new AVD doesn't require Entra DS, it only requires Entra DS if there will be FSLogix containers). But the billing has started. To fix, we had to remove the Entra DS after validating that the credentials were indeed being helped. Monthly, this amounted for over $200 per month to the customer. We had to find a way to rebate the $$ to them. To ensure that this DOES not continue to happen - Can you add a piece to the QuickStart that enables Entra by itself without the entraDS or, at least WARN in the documentation that if you use QuickStart that this will be the side effect of launching this way? The client believes it should be articulated that this was a hidden fee they wouldn't have gotten if they had known the Wizard was going to bill this. So Customer request: Modify Azure Virtual Desktop Quickstart - ADD OPTION, Entra ONLY Add visual indicators that if chosen Entra DS option will bill Entra DS Entra DS is only required if using FSLogix or Entra DS as a domain for Hybrid Virtual desktop There is not an option to join the machine to Intune. Can you ADD one?
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.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.
