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.
[Enterprise Customer Feedback] - AVD Forced Log Off
After going over the issue with support, we couldn't find a solution that an end user can self-service themselves to rectify when an AVD session host is having a performance issue. The host session VM booted up per our scaling policy at 7:45 a.m. and immediately had a User Profile service error. When the first attempted session connection occurred about 15 minutes later, it failed to load the session and only left the user with a black screen. Disconnecting and relaunching the session still placed them in the session hung session. We employ a disconnected session log-off policy of 120 total minutes. It would take at least 2 hours without user interaction for a session to fully terminate. There is no way a user can force log off their session in either the web client or Azure Virtual Desktop client. The only option available is to disconnect but it maintains the session live in the backend. 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. And, an option for the end user to avoid a new session connection to the host that was having the issue. This might limit productivity time loss as IT works on rectifying the issue. (most likely a reboot of the session host machine).
Add Capacity Reservation Group Support to Azure Virtual Desktop VM Creation Wizard
I would like to request support for assigning Azure Capacity Reservation Groups during Azure Virtual Desktop (AVD) session host creation. I recently deployed a GPU-enabled AVD environment for AI and machine learning workloads where GPU resources are extremely scarce and often unavailable for on-demand provisioning. To guarantee capacity, we were required to create a Capacity Reservation Group prior to deployment. Currently, there is a significant workflow gap between standard Azure VM creation and AVD session host deployment. Standard Azure VM deployment allows a VM to be assigned to a Capacity Reservation Group during creation. The Azure Virtual Desktop host pool creation wizard does not expose this option. Administrators are forced to either create the VM outside of the AVD workflow using the Capacity Reservation interface and manually register it to the host pool afterward, or deploy through the AVD wizard and associate the VM with a Capacity Reservation Group later. This creates several challenges. Additional Quota Requirements Capacity Reservations consume quota before a VM is deployed. Because the AVD wizard cannot deploy directly into a reservation, administrators may need additional quota approvals to support both the reservation and deployment workflow. In environments where quota increases require support requests, this can introduce delays of several days. Resource Scarcity and Timing Issues GPU-enabled SKUs frequently have limited regional availability. Administrators must wait for both quota availability and capacity availability multiple times throughout the deployment process. This significantly increases deployment complexity and delays project delivery. Inconsistent Management Experience Creating the VM through the Capacity Reservation workflow bypasses several AVD deployment conveniences, such as Microsoft Intune enrollment and other AVD-specific configuration settings available through the host pool deployment wizard. Administrators are forced to perform additional manual configuration after deployment. Operational Overhead Manual host registration, Entra ID joining, Intune enrollment, and post-deployment configuration introduce unnecessary complexity and increase the likelihood of deployment errors. Suggested Enhancement Add a Capacity Reservation Group selection option directly within the Azure Virtual Desktop session host deployment workflow, similar to the standard Azure VM deployment experience. This would allow administrators to: Deploy AVD session hosts directly into reserved capacity. Utilize existing AVD provisioning features, including Intune enrollment and Entra ID integration. Reduce quota management complexity. Minimize deployment delays for high-demand GPU workloads. Provide a more consistent and streamlined Azure deployment experience. This issue became particularly impactful when deploying NV-series GPU session hosts, where both regional capacity and quota approvals were constrained and deployment timelines were significantly extended. As AI, machine learning, and GPU-intensive workloads continue to grow, this capability would significantly improve the deployment experience for organizations leveraging Azure Virtual Desktop for these use cases.
MacOS Windows App Dynamic Resolution not working
When using MacOS Windows App 11.0.5, if the AVD icon settings are left un-customised, the App does not honour the host pool setting to enable Dynamic Resolution. Dynamic Resolution only seems to work if it's explicitly enabled on each AVD icon within the Windows App on the client device. Our users expect Dynamic Resolution to work by default. It's enabled in the host pool and it previously worked on the RD Client.AVD Federation with external identities
Spent months figuring out why federated SSO breaks for external users accessing Azure Virtual Desktop. Turns out Azure AD ignores custom federation when the user's domain is verified elsewhere—forces B2B routing, kills Windows SSO. Built a workaround using proxy domains and a federation hub. Curious—how are others solving this? Or just telling customers SSO isn't possible? I can't find any roadmap agenda.
Azure Virtual Desktop for Guest User / B2b Identity
All of our external customers have their own AAD / Entra ID and wish to not manage multiple identities. As we present our applications via AVD, it requires them to have a separate identity in our tenant currently. AVD should support guest accounts from another tenant to be able to sign in. Currently, per the documentation and per the ticket I just worked with Microsoft support: Azure Virtual Desktop doesn't support external identities, including guest accounts or business-to-business (B2B) identities. Whether you're serving internal commercial purposes or external users with Azure Virtual Desktop, you'll need to create and manage identities for those users yourself. Please continue development to allow guest accounts that have been invited into a tenant to sign in to AVD machines. Thanks!
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?
