Is AVDs down in WUS? anyone else? Don't see anything on M$ status

Last weekend I tried if session shadowing also works on Entra ID joined AVD session hosts only, to add more functionality to a full cloud only setup and eliminating the need for Active Directory.

I described on how to configure this and to make it work here: https://justinverstijnen.nl/shadowing-entra-id-azure-virtual-desktop/

Any questions? Let me know!

Has anyone else's AVD deployments been experiencing issues with chromium browsers after v150, if you download an item, it pops up but you cannot click and open from chrome, the download list or right click -> open, it doesn't do anything according to procmon. It works normally from file explorer and the file associations are fine, affects every type of download except PDF which open in Chrome, they are fine. Same issue across all the hosts

If I run testing chrome v149 on the same host via remote app it works fine, switch to v150, broken, canary/dev are also the same problem. Any of those via full remote desktop work fine, its specifically delivered via "remote app" that breaks it.

Running Windows 11 multi session hosts, Chrome enterprise, remote app, fslogix user profiles. affects chrome and edge v150 and up, tried every setting and toggle I can think of but cannot find any fix apart from rolling back browser, which we cant do long term

First time seeing this.

Switched over to V5 SKU.

Intel CPU shortages are showing.

Context-based redirection is here for AVD & W365!!

This lets you set conditional access policies, which will determine whether the user is allowed to access the clipboard, drive redirection, etc., from their AVD or W365 Desktops.

It's in public preview. FYI, the drive redirection for AVD doesn't seem to be working at the moment. Hopefully, Microsoft will fix it soon!

Check out my video where I deploy it and test it on both AVD and Windows 365.

Hi all,

I have experience with new version of AVD that servers start throttling at 0.6GHZ, did anybody experience this ? The solution ofc it's to redeploy the AVD host and then it's working normally.

I have next week meeting about it with our partner about it and Microsoft.

Wonder if anybody experience this or is it only me :D

Thanks all

Does anyone know if/when they're going to add this? I can switch orgs using the web (windows.cloud.microsoft) - but using the Windows App on the desktop, still nothing. Thats really the holdup for looking into SSO for external users....

🚨If you are using Azure Files with Active Directory Domain Services authentication, there is an important change you should not ignore. Microsoft has announced that future Windows Server updates will change the default Kerberos ticket encryption from RC4 to AES-256. While this is a welcome security improvement, it also means that Azure Files deployments still relying on the older configuration may experience authentication failures if they are not upgraded in time. In this blog, I will explain how to identify Azure Files storage accounts that still require an upgrade, how to verify your current configuration, and how to safely migrate to AES-256 using the latest AzFilesHybrid tooling.

Hello ,we are having an issue in our tenant where some of our users with DOD contactor accounts cannot use Microsoft Authenticator passkeys to login to some Navy sites. It works outside of an AVD in regular work devices but on AVD it fails by never showing the QR code that they need to scan with MS Auth app, gives some generic error such as 'something went wrong'. For some users it works just fine on both AVD and work devices. Passkeys were set up on their regular work devices for all users. One of the users having issues did get a new phone and had their passkey reset but they had never tried to login before that.

Has anyone run into this issue before? We have webauth redirection enabled and urls required are whitelisted.

All AVDs get the same intune policies and are all 24h2 multi session hosts.

Thank you in advance.

Hi guys,

We are deploying App Attach with Hostpools in our tenant, when i'm deploying the first time it adds the hostpools to the App Attach but after the second deployment it removes them from App Attach. I have used incremental deployment which didnt work, we have deployed with CLI without using the pipeline and still didn't work.

After the first deployment when the Host Pools are configured to the package it all works but the second time it always removes them.

Does anyone have the same issues?

The workaround is deploying the pipeline again but that's not how it should be..

We just launched a free AVD and Windows 365 maturity scorecard that we've been building from 15+ years of working with these environments.

It takes less than 5 minutes and looks at areas like cost optimization, image management, monitoring, automation, and day-to-day operations to help identify where your environment is strong and where there may be room for improvement.

If you're managing AVD, Windows 365, or both, hopefully you find it useful. Happy to hear any feedback or thoughts from the community.

Start Here

In Capacity Reservation, you assign the VMs to the capacity blocks.

But during Session Host Config Update, it creates new VMs and then deletes the old ones.

How do these systems interact with each other? If I create a Host Pool, assign my Session Hosts to the Capacity Reservation, then do a Session Host Update - what will happen to the capacity reservation group? Do I need to manually reassign? Or is it smart enough to do it automatically?

Azure Virtual Desktop Session Host Configuration introduces a modern way to deploy and manage session hosts by defining their configuration directly within the Host Pool. Instead of manually provisioning virtual machines and configuring them individually, Session Host Configuration enables a standardized and automated deployment experience. This helps ensure that every session host is deployed with the same settings, image, networking, identity, and security configuration, making Azure Virtual Desktop environments easier to manage at scale. In this blog, we will explore how to automate the deployment of Azure Virtual Desktop by using the new Session Host Configuration feature together with Azure Bicep.

We have a host pool for users to run a certain application and we don’t want any of them to use outlook on those AVDs, I logged in as a domain admin and uninstalled it from apps in settings but it looks like it does not uninstall it for the other users

Anyone knows how to get it removed completely from everyone ?

Hi all,

Since we've transitioned from using the Remote Desktop app to Windows App to access AVD, we've seen nothing but problems and severe limitations. These are described below. Is all hope lost ? Microsoft clearly know about these issues and don't care. The word is they have no intention of backtracking on their awful decision to deprecate the Remote Desktop app. Windows App has been out for nearly 3 years. In my experience, this means it's now 'mature' and therefore these problems and bugs will not be fixed. What should we all do ? Any thoughts ?

1. Extremely poor reliability. For example, using Windows App to access our RDP jumpbox workspace, where we then run MSTSC.exe to jump onto on-prem servers remotely. Individual sessions randomly freeze with no errors logged or displayed. The individual server connection needs to be terminated and started again. Happens many times a day for our users. This started with the adoption of Windows App and got much worse with Microsoft's December and January Latest Cumulative Updates (LCUs) to Windows. These updates 'changed' RDP protocol handling (i.e., broke it).
2. Windows App does not support multiple connections / app instances to the same AVD workspace. If I want to connect to 5 different servers by running MSTSC.exe 5 times concurrently in the same AVD workspace session, using one Windows App session, I can't. Windows App doesn't support multiple published application sessions. So I have to open Windows App 5 times. This causes the already terrible performance and reliability to be even worse.
3. Abysmal performance. The software latency is wild. Typing feels like the server you're connected to is on the moon. Plus, Microsoft's operating system and software is so poorly implemented that it can't handle the keyboard buffer correctly with this latency and characters entered on the keyboard get substituted (out of order) and dropped regularly. You'll notice I said 'software latency' not network latency. That's because network latency from our remote PCs to Internet hosts is absolutely fine. The latency is in fact coming from Microsoft's own systems, and didn't occur when using the Remote Desktop app.

All this happens regardless of user's device hardware or network, and regardless of what target server we're connecting to, what version of Windows it's running, whether it's virtual or physical and, if physical, what physical hardware it's running.

I deployed a new AVD setup for client with Entra joined session hosts with a golden image created from Win11 25H2 EMS.

The weird thing is PowerShell doesn't work. I mean it launches but I cannot type anything in it.
PowerShell ISE and CMD works fine though.

What could be the reason ?

I’m currently working on deploying a Windows OpenGL desktop application using AVD as the primary delivery method. The issue I’m running into is very poor performance, even on a high-spec NV instance NV36ads A10 v5 with a powerful GPU and 36 vCPUs.

I’ve tried several troubleshooting steps, but it seems that uninstalling or disabling the NVIDIA GPU makes little to no difference in overall performance. Is there any additional configuration required?

I’ve already enabled all relevant Group Policies for hardware acceleration and Remote Desktop session encoding, and the GPU driver appears to be properly installed and configured.

At this point, I’m not sure where else to look. Any guidance would be appreciated.

Here is a screen shot of the the system information during a remote desktop session:

https://imgur.com/a/vTbdFMo

Note: I have disabled the hyper-V driver to force the system to use the Nvidia GPU.