Bug with profile picture on AVD / Windows 11 Multi-User
My organization has seen multiple occurrences where a different user's profile picture/icon is shown besides their own. This has been seen in the OS under Start (lower left corner) as well as in Settings -> Accounts. No issues have been seen with Teams or Outlook only the profile picture shown within the OS. Have not seen anything similar with our on-premise Citrix machines. Not a high priority issue obviously but would like to raise awareness. If anyone has ideas, please let me know what information I can gather to start troubleshooting! Thank you.
Expose AVD registration status on Azure VM objects
In enterprise environments, it's difficult to determine whether a VM is successfully registered with Azure Virtual Desktop (AVD) without querying the host pool or relying on indirect signals. Please consider surfacing the AVD registration status (e.g., Registered, Not Registered, Pending) directly on the Azure VM object, accessible via: Azure Portal Azure Resource Graph Azure PowerShell / CLI REST API This would simplify automation, monitoring, and remediation workflows across large-scale deployments. Thanks for considering this! VuAdd the Networking Tab in the Host Pool Creation Wizard in the Azure Portal
Just like we have a Networking tab in the Storage Account where public access can be disabled and private endpoints enabled, there should be a similar option available during Host Pool creation in the Azure Portal. In my customer environment, which is a banking organization, a policy is enforced that does not allow any resource to be created with public access—it blocks the creation outright. az policy assignment create \ --name "DenyPublicAccess" \ --scope "/subscriptions/<subscription-id>" \ --policy "/providers/Microsoft.Authorization/policyDefinitions/<policy-definition-id>" The policy they use is named "Public network access should be disabled for PaaS services", which prevents the creation of a Host Pool unless public access is disabled. Currently, this setting cannot be configured during Host Pool creation in the Azure Portal, as the networking tab is only available after the Host Pool is created, allowing you to disable public access and enable private endpoints. For BFSI customers, requesting a policy relaxation is difficult. While this may be achieved through automation, the option should also be available in the Azure Portal. Otherwise, it creates a contradiction—there is a policy to disable public access, but no way to comply with it during the initial creation.Dynamic RDP Properties Based on User's Location and Device Type
Hello! I am working with a client that currently uses Citrix SmartPolicies to update the RDP property of the remote machines based on if a user is connecting from a personal machine (not a client provided machine) and if the user is connecting from outside of the network (personal and client provided machine). So if, for example, they connect from a personal machine, the user cannot map printers, local drives, or have copy/paste functionality. I write this to ask if there's a possible way to do this in Azure Virtual Desktop. We've looked at Liquidware's ProfileUnity solution which can update these RDP properties based on AVD Session host properties like WMI classes, registry values, and environment variables. However, the only real discernable value we could find at the moment is $env:CLIENTNAME. We are looking for a secondary value to base filter on as the CLIENTNAME could be hacked pretty easily. Looking to see if anyone has had success in this type of scenario for a highly regulated company and what was your solution? If you used a third-party service, what was that service? Thanks!
FSLogix - 48v35 error at Microsoft login prompt in AVD
I'm resposting from this thread to hopefully create more attention for this problem: https://answers.microsoft.com/en-us/outlook_com/forum/outlk_win-outtop_new-outsub_ofb/outlook-error-message-somehting-went-wrong-48v35/97d7ff71-8a58-40c8-8726-adf3d1f095b8 Me and other admins (from reposted thread) have specific users who experience M365 authentication problems after upgrading to the latest FSLogix version(s) that offers support for New Teams. The error occurs in the Azure Virtual Desktop environment, when a user tries to open a Microsoft application (Outlook, OneDrive etc.). Not all users have the problem that they need to reauthenticate, or can't authenticate at all, with the 48v35 error. The users who do however, repeatedly get the same error after a few days or a week. We tried multiple things, like removing the Microsoft.AADBrokerPlugin directory or creating a completely new FSLogix profile, but the problem stays for these users. In my case I am using the FSLogix setting RoamIdentity=1. Is there any news from FSLogix on this issue? Or does anyone have workarounds to share? I would like to update more customer environments to use the New Teams, but with these issues I would rather wait.
New Service Improvement Idea: AVD Performance Insight Dashboard
Overview: Enhance the Azure Virtual Desktop (AVD) experience by introducing a dedicated dashboard that displays real-time CPU and memory usage for each AVD session along with the top 10 processes consuming CPU. This dashboard will empower IT administrators to quickly diagnose performance issues and optimize resource allocation. Key Features: Real-Time Monitoring: Display live CPU and memory metrics per AVD session. Auto-refresh capability to capture real-time performance changes. Process Analysis: Show a list of the top 10 processes consuming CPU per session. Provide detailed process metrics including CPU percentage, memory footprint, and process IDs. Historical Data & Trend Analysis: Archive performance data to visualize trends over time. Enable administrators to identify recurring patterns or spikes in resource usage. Alerting & Notifications: Set custom thresholds for CPU and memory usage. Generate alerts for sessions or processes that exceed set limits, triggering proactive remediation. Integration with Existing Tools: Seamlessly integrate with Azure Monitor and Log Analytics for deep-dive analysis. Export data to Power BI for advanced visualization and reporting. User-Friendly Interface: Interactive dashboard design with filtering options (e.g., by session, time frame, or specific metrics). Drill-down capability to analyze individual sessions or processes in detail. Benefits: Enhanced Troubleshooting: Quickly pinpoint performance bottlenecks by identifying resource-intensive sessions and processes. Proactive Maintenance: Early detection of abnormal resource usage allows for timely intervention before issues escalate. Optimized Resource Management: Understand usage patterns to make informed decisions on scaling, workload balancing, and capacity planning. Improved User Experience: Reduce downtime and performance issues, leading to smoother end-user operations in the virtual desktop environment. Implementation Considerations: Data Collection: Leverage AVD session performance counters and existing telemetry from Azure Monitor. Dashboard Development: Use modern visualization tools (e.g., Power BI or Azure Dashboard) for an intuitive user interface. Security & Compliance: Ensure data privacy and compliance with government/federal cloud standards where applicable.
AVD Hibernate on Azure Local
We're working to deploy AVD on Azure Local to improve performance of our apps. We have a set of users that work infrequently, but have a need to keep their session persistent between "Shifts". In a personal host pool setup, we're finding our current options cost prohibitive with the avd management costs for azure local based deployments. A solution that would allow hibernating the VMs during periods of inactivity would be the best case for our needs.
Need insight to domain join failures for session host configuration
We are trying to use the session host configuration for a new AVD host pool. We have confirmed that it can join computer to the specified OU without difficulty when we do it manually, and that the key vault access is intact since the local admin is created without issue. But any new session hosts fail to join to the domain. They're created with all other specifications. If we try to add them manually it seems to create some kind of instability in the FSLogix where it will then permanently hang for users when trying to log off. It would be good if we had insight to the domain join failures so we don't have to manually join them. In the deployment I can see the network, the VM, and a DSC, but that DSC is only for joining to the AVD Host pool. I don't see anything in it to join using the key vault credentials.
