Having issues with my new AVD environment: health state: Unavailable

Hello @Arya Vahanian AZ

Thank you for reaching out. We're looking into the Bastion login issue and would appreciate your help by answering these questions.

1. Is the AVD Agent (RDAgentBootLoader service) running on the Session Host VM?
2. Are you seeing EXPIRED_MACHINE_TOKEN or INVALID_REGISTRATION_TOKEN errors in the Windows Application logs?
3. DomainJoinedCheck: This makes sure your session host is actually joined to the right domain. If it’s not, none of your connections will work—so be sure it’s set up correctly.
4. DomainTrustCheck: This one looks for any domain trust problems. If it fails, authentication breaks, so it’s a pretty big deal.
5. FSLogixHealthCheck: Checks that FSLogix is running smoothly. If it’s not, user profiles won’t load and things can get messy.
6. SxSStackListenerCheck: Makes sure the side-by-side stack is up and ready. If it’s down, you might need to reboot the VM or dig into some troubleshooting.
7. UrlsAccessibleCheck: Verifies you can reach all the necessary Azure Virtual Desktop and Geneva URLs. Not always a showstopper, but if some URLs are blocked, updates and diagnostics could be affected.
8. DomainReachable: Checks if you can actually connect to the domain. If this fails, the service won’t be able to connect at all.

a Session Host may report "Unavailable" when it’s Stopped (deallocated). Ideally, it should show "Shutdown" instead, which usually occurs if "Hyper-V Integration Services" (specifically "Hyper-V Guest Shutdown Service") is disabled. For instance, the Hyper-V Guest Shutdown Service is responsible for gracefully shutting down the OS from the host when a Stop call is made from Azure.

Thanks,
Manish