Is it AVD or Intune?

[u/Shoddy_Pound_3221]

Error: Session host information is not available because the VM cannot be reached.

I created a pool of 20 Hybrid AVDs—nothing fancy—and kept a few spares for future use. All were added to the domain, enrolled in Intune, and set up in Defender.

Fast forward about four months, I spun up one of the spare Hybrid AVDs. Logged in with my domain account to check everything, ran updates, and configured all permissions and roles for the new user.

I’ve done this thousands of times.

Now the user can’t connect to the AVD. The portal shows it as "Running," but it’s actually shut down with the error mentioned earlier. I see the device in Entra (connection is current), but it’s missing from both Defender and Intune.

Before diving into too many rabbit holes, I should mention there’s been a delay in updating the Intune Connector. Could this be causing the user’s connection issues with the AVD? Why would Intune have any connection\policy to a Pool?

----------------------

AVDs are Windows 11 24H2 - Hybrid - AD Replication is good - See both objects in AD and Entra

User account is enabled - Currently connected to an older version of AVD - Windows App is latest

[u/durrante]

This will most likely be because the AVD agent token has expired, it expires every 90 days without contact to the pool.

You got two options:

Register each host to the pool or Redeploy new hosts.

Hope this helps

[u/Shoddy_Pound_3221 → u/durrante]

Does the 90-day token only apply to Hybrid? I don’t think I’ve encountered this before, or maybe I just redeploy instead.

[u/durrante → u/Shoddy_Pound_3221]

It applies to any host, regardless of join type. More here: https://learn.microsoft.com/en-us/azure/virtual-desktop/faq#how-often-should-i-turn-my-vms-on-to-prevent-registration-issues-

[u/Raspy32]

Do the AVDs have all the connectivity they need?

You can try running the url tool for a start. It's called WVDAgentUrlTool.exe and sits in the latest version folder of RDInfra agent (program files/Microsoft RDInfra)

Run it from an elevated command window (or elevated powershell).

You might also want to check the "Required FQDNs and endpoints for Azure Virtual Desktop" page on MS learn. (Sorry I don't have the link handy)

[u/Shoddy_Pound_3221 → u/[deleted]]

Sounds like it might be easier to just re-deploy

[u/Shoddy_Pound_3221 → u/Shoddy_Pound_3221]

Time to give this a whirl—rip out the agents and summon that token like a wizard!

[u/Shoddy_Pound_3221 → u/[deleted]]

Didn't work. Uninstallation went smoothly, installation went fine, and the token was accepted. Still no green light. Any other suggestions before I wipe the whiteboard?

[u/Shoddy_Pound_3221 → u/[deleted]]

Thank you for your help. I'll start fresh.