Post added at the request of Microsoft support:
I understand that previously AVD/WVD deployments required that AVD vm's be domain-joined, but now there's an option to add vm's to host pools using Azure AD auth. However, even if the tenant ID for the host pool VM corresponds with the default Azure AD tenant ID, when the Azure AD option is selected on creating the host pool, hosts added to the pool are marked "unavailable", with the health check returning the following:
{
"healthCheckName": "DomainJoinedCheck",
"healthCheckResult": "HealthCheckFailed",
"additionalFailureDetails": {
"message": "SessionHost unhealthy: SessionHost is not joined to a domain",
"errorCode": -2147467259,
"lastHealthCheckDateTime": "2021-07-18T02:45:30.0910788Z"
}
}
This may just be a case where the configuration flow in the UI is allowing for new functionality (Azure AD-only configuration) but the vm verification as reflected in the portal hasn't been updated to allow the new configuration, but as I am new to AVD it's very possible that something less obvious is happening. Any pointers would be much-appreciated.